docs: fix typos (#8447)

* fix typo in bundling-extension.md

* fix typo in config-mingw.md

* fix typo in customize-cpp-settings.md

* docs:  fix typo in TemplateProject.md

* docs: fix typo in nodejs-debugging.md

* docs: fix typo in settings-reference.md

Author: noritaka1166

api/working-with-extensions/bundling-extension.md

@@ -99,7 +99,7 @@ The build script does the following:
 esbuild can work directly with TypeScript files. However, esbuild simply strips off all type declarations without doing any type checks.
 Only syntax errors are reported and can cause esbuild to fail.
 
-For that reason, we separatly run the TypeScript compiler (`tsc`) to check the types, but without emmiting any code (flag `--noEmit`).
+For that reason, we separately run the TypeScript compiler (`tsc`) to check the types, but without emitting any code (flag `--noEmit`).
 
 The `scripts` section in `package.json` now looks like that
 

docs/cpp/config-mingw.md

@@ -414,7 +414,7 @@ The extension uses the `compilerPath` setting to infer the path to the C++ stand
 
 The C/C++ extension attempts to populate `compilerPath` with a default compiler based on what it finds on your system. The extension looks in several common compiler locations but will only automatically select one that is in either one of the "Program Files" folders or whose path is listed in the PATH environment variable. If the Microsoft Visual C++ compiler can be found it will be selected, otherwise it will select a version of gcc, g++, or clang.
 
-If you have more than one compiler installed, you might need to change `compilerPath` to match the preferred compiler for your project. You may also use the **C/C++: Select InteliSense Configuration...** command in the Command Palette to select one of the compilers that the extension detected.
+If you have more than one compiler installed, you might need to change `compilerPath` to match the preferred compiler for your project. You may also use the **C/C++: Select IntelliSense Configuration...** command in the Command Palette to select one of the compilers that the extension detected.
 
 ## Troubleshooting
 

docs/cpp/customize-cpp-settings.md

@@ -133,7 +133,7 @@ The following JSON snippet is an example configuration for `c_cpp_properties.jso
   Custom variables that can be queried through the command `${cpptools:activeConfigCustomVariable}` to use for the input variables in `launch.json` or `tasks.json`.
 
 - `browse`:
-  The set of properties used in conjunction with IntelliSense to identify all symbols in your code base. These properties are used by features such as **Go to Definition/Declaration**, gloabl symbol search, or when the "default" IntelliSense engine is unable to resolve the `#includes` in your source files.
+  The set of properties used in conjunction with IntelliSense to identify all symbols in your code base. These properties are used by features such as **Go to Definition/Declaration**, global symbol search, or when the "default" IntelliSense engine is unable to resolve the `#includes` in your source files.
 
 - `recursiveIncludes`:
   A set of properties used to configure how the extension processes an `includePath` entry that specifies a recursive search.

docs/intelligentapps/reference/TemplateProject.md

@@ -27,7 +27,7 @@ You could also adjust other parameters to suit your need:
 - `max_length: 128` / `batch_size: 1`: For static quantization, the input size should be fixed. Adjust these to match `FIXED_VALUES`
 - `max_samples: 100`: The number of samples used.
 
-## Update model_project.comfig (optional)
+## Update model_project.config (optional)
 Update workflows's `name` to reflect what you want to do. So it is more easy to pick from the workflow list.
 
 Update modelInfo's `displayName` and `modelLink` to the one you used. So it is more easy to pick from the model list.

docs/nodejs/nodejs-debugging.md

@@ -573,7 +573,7 @@ Some examples:
 
 ### Triggered breakpoints
 
-A trigged breakpoint is a breakpoint that is automatically enabled once another breakpoint is hit. They can be very useful when diagnosing failure cases in code that happen only after a certain precondition.
+A triggered breakpoint is a breakpoint that is automatically enabled once another breakpoint is hit. They can be very useful when diagnosing failure cases in code that happen only after a certain precondition.
 
 Triggered breakpoints can be set by right-clicking on the glyph margin, selecting **Add Triggered Breakpoint**, and then choosing which other breakpoint enables the breakpoint.
 

docs/python/settings-reference.md

@@ -103,7 +103,7 @@ The language server settings apply when `python.languageServer` is `Pylance` or
 | inlayHints.functionReturnTypes | false |  Whether to display inlay hints for function return types.  Accepted values are `true` or `false`. |
 | inlayHints.pytestParameters | false | Whether to display inlay hints for pytest fixture argument types. Accepted values are `true` or `false`. |
 | inlayHints.variableTypes | false | Whether to display inlay hints for variable types. Accepted values are `true` or `false`. |
-| languageServerMode | default |  Offers predefined configurations to optimize Pylance's performance based on the development needs. <br> Available values are `default` and `light`. <br> When set to `default`, the language server delivers sufficient functionality for most machines without overloading the system. <br> When set to `light`, it enables a lightweight, memory-efficient setup. This mode disables various features to make Pylance function more like a streamlined text editor, and it's ideal for those who do not require the full breadth of IntelliSense capabilities and prefer Pylance to be as resource-friendly as possible. <br> Default setting values are overriden to the following by each mode:  <table> <tr> <th>Setting</th> <th>`light` mode</th> <th> `default` mode </th> </tr> <tr> <td>python.analysis.exclude</td> <td> ["**"]    </td> <td> [] </td>  <tr> <td>python.analysis.useLibraryCodeForTypes</td> <td>false</td> <td>true</td> <tr> <td> python.analysis.enablePytestSupport  </td> <td>false</td> <td>true </td>  <tr> <td> python.analysis.indexing </td> <td>false</td> <td>true </td></tr> </table> |
+| languageServerMode | default |  Offers predefined configurations to optimize Pylance's performance based on the development needs. <br> Available values are `default` and `light`. <br> When set to `default`, the language server delivers sufficient functionality for most machines without overloading the system. <br> When set to `light`, it enables a lightweight, memory-efficient setup. This mode disables various features to make Pylance function more like a streamlined text editor, and it's ideal for those who do not require the full breadth of IntelliSense capabilities and prefer Pylance to be as resource-friendly as possible. <br> Default setting values are overridden to the following by each mode:  <table> <tr> <th>Setting</th> <th>`light` mode</th> <th> `default` mode </th> </tr> <tr> <td>python.analysis.exclude</td> <td> ["**"]    </td> <td> [] </td>  <tr> <td>python.analysis.useLibraryCodeForTypes</td> <td>false</td> <td>true</td> <tr> <td> python.analysis.enablePytestSupport  </td> <td>false</td> <td>true </td>  <tr> <td> python.analysis.indexing </td> <td>false</td> <td>true </td></tr> </table> |
 | logLevel | `Error` | Specifies the level of logging to be performed by the language server.<br> The possible levels of logging, in increasing level of information provided, are `Error`, `Warning`, `Information`, and `Trace`.|
 | nodeArguments | `"--max-old-space-size=8192"` | Specifies custom arguments directly the custom Node.js executable defined by `python.analysis.nodeExecutable`. This can be used to allocate more memory or configure Node.js behavior. <br> Accepts a list of arguments supported by Node.js. Each `"arg=value"` should be separated by commas in the list. <br> Usage Example: ```"python.analysis.nodeArguments": ["--max-old-space-size=8192"]``` |
 | nodeExecutable | `""` | Specifies the Node.js executable to use, which allows Pylance to allocate more memory.  <br> Accepted values are strings with executable paths, an empty string or `"auto"`. <br> When set to an empty string, Pylance will use VS Code's node executable. When set to `"auto"`, it will automatically download [Node.js](https://nodejs.org/dist/).|