From 5cb23b34e157df9a24d85637a4a4efbe85024237 Mon Sep 17 00:00:00 2001 From: Arie Heinrich Date: Fri, 1 Nov 2024 00:41:19 +0100 Subject: [PATCH] Spelling fixes (#7734) --- api/extension-guides/testing.md | 2 +- api/extension-guides/web-extensions.md | 2 +- docs/azure/mongodb.md | 2 +- docs/copilot/getting-started.md | 2 +- docs/csharp/debugging.md | 2 +- docs/csharp/package-management.md | 12 ++++++------ docs/getstarted/tips-and-tricks.md | 2 +- docs/java/java-project.md | 2 +- docs/supporting/oss-extensions.md | 2 +- 9 files changed, 14 insertions(+), 14 deletions(-) diff --git a/api/extension-guides/testing.md b/api/extension-guides/testing.md index eb8223c4ab..2fddd3767a 100644 --- a/api/extension-guides/testing.md +++ b/api/extension-guides/testing.md @@ -261,7 +261,7 @@ async function runHandler(shouldDebug: boolean, request: vscode.TestRunRequest, The `FileCoverage` contains the overall covered and uncovered count of statements, branches, and declarations in each file. Depending on your runtime and coverage format, you might see statement coverage referred to as line coverage, or declaration coverage referred to as function or method coverage. You can add file coverage for a single URI multiple times, in which case the new information will replace the old. -Once a user opens a file with coverage or expands a file in the **Test Coverage** view, VS Code requests more information for that file. It does so by calling an extension-defined `loadDetailedCoverage` method on the `TestRunProfile` with the `TestRun`, `FileCoverage`, and a `CancellationToken`. Note that the test run and file coverage instances are the same as the ones used in `run.addCoverage`, which is useful for assocating data. For example, you can create a map of `FileCoverage` objects to your own data: +Once a user opens a file with coverage or expands a file in the **Test Coverage** view, VS Code requests more information for that file. It does so by calling an extension-defined `loadDetailedCoverage` method on the `TestRunProfile` with the `TestRun`, `FileCoverage`, and a `CancellationToken`. Note that the test run and file coverage instances are the same as the ones used in `run.addCoverage`, which is useful for associating data. For example, you can create a map of `FileCoverage` objects to your own data: ```ts const coverageData = new WeakMap(); diff --git a/api/extension-guides/web-extensions.md b/api/extension-guides/web-extensions.md index 67ecc08cf1..4a12aac1ac 100644 --- a/api/extension-guides/web-extensions.md +++ b/api/extension-guides/web-extensions.md @@ -625,7 +625,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 error 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 ```json diff --git a/docs/azure/mongodb.md b/docs/azure/mongodb.md index 8f40b8ab2a..e382ef473c 100644 --- a/docs/azure/mongodb.md +++ b/docs/azure/mongodb.md @@ -31,7 +31,7 @@ To connect to a MongoDB database: * Select **Connect with Connection String**, and then enter the connection string in the connection string Quick Pick. - The default connetion string for a local MongoDB is `mongodb://127.0.0.1:27017`. + The default connection string for a local MongoDB is `mongodb://127.0.0.1:27017`. ![Database Connection setup](images/mongodb/attach-database-account-connection-string.png) diff --git a/docs/copilot/getting-started.md b/docs/copilot/getting-started.md index fa07ed97ee..820bef6591 100644 --- a/docs/copilot/getting-started.md +++ b/docs/copilot/getting-started.md @@ -145,7 +145,7 @@ One such place is the Copilot coding actions in the editor, whenever there you h 1. Select the sparkle to view the Copilot code actions, and then select **Fix using Copilot**. - ![Screenshot of VS Code editor, showing the Copilot code actions, hihglighting `Fix using Copilot`.](./images/getting-started/copilot-code-action-fix.png) + ![Screenshot of VS Code editor, showing the Copilot code actions, highlighting `Fix using Copilot`.](./images/getting-started/copilot-code-action-fix.png) 1. Notice that the Copilot Inline Chat comes up, prepopulated with the error message, and a solution to fix the problem. diff --git a/docs/csharp/debugging.md b/docs/csharp/debugging.md index c7185bc54f..64ab127db2 100644 --- a/docs/csharp/debugging.md +++ b/docs/csharp/debugging.md @@ -173,7 +173,7 @@ The following tokens are also supported in the log message: ### Breakpoint - 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. diff --git a/docs/csharp/package-management.md b/docs/csharp/package-management.md index c8313e5866..039c6a890a 100644 --- a/docs/csharp/package-management.md +++ b/docs/csharp/package-management.md @@ -10,23 +10,23 @@ MetaDescription: C# package management with NuGet in Visual Studio Code # NuGet in Visual Studio Code -NuGet is the package manager for .NET. It defines how packages for .NET are created, hosted, and consumed, while providing the tools for each of those functions. NuGet also manages the dependency tree on behalf of a project, so you only need to focus on the packages that you're directly using in a project. +NuGet is the package manager for .NET. It defines how packages for .NET are created, hosted, and consumed, while providing the tools for each of those functions. NuGet also manages the dependency tree on behalf of a project, so you only need to focus on the packages that you're directly using in a project. -In Visual Studio Code, you can manage your NuGet packages either directly from the C# Dev Kit Solution explorer, or by using the Command Palette. +In Visual Studio Code, you can manage your NuGet packages either directly from the C# Dev Kit Solution explorer, or by using the Command Palette. * [NuGet Commands in C# Dev Kit](#nuget-commands-in-c-dev-kit) * [Dependency Management](#dependency-management) -To learn more about NuGet, go to the [NuGet documentation](https://learn.microsoft.com/nuget/what-is-nuget). +To learn more about NuGet, go to the [NuGet documentation](https://learn.microsoft.com/nuget/what-is-nuget). ## NuGet commands in C# Dev Kit -In C# Dev Kit, you can perform NuGet package operations in one of two ways: +In C# Dev Kit, you can perform NuGet package operations in one of two ways: * Using the Command Palette (`kb(workbench.action.showCommands)`) * Right-clicking in the C# Dev Kit Solution explorer - + The following sections describe how to use each NuGet command, using both of these two methods. ### Add a package @@ -81,7 +81,7 @@ The following sections describe how to use each NuGet command, using both of the ### Automatic NuGet restore -For a .NET project, a package restore happens automatically when you create a project from a template, build, load, or make changes to an SDK-style project. You can view in the progress and logs in the Ouput panel. +For a .NET project, a package restore happens automatically when you create a project from a template, build, load, or make changes to an SDK-style project. You can view in the progress and logs in the Output panel. ![Automatic NuGet package restore](images/package-management/automatic-nuget-package-restore.png) diff --git a/docs/getstarted/tips-and-tricks.md b/docs/getstarted/tips-and-tricks.md index a3348eeaa7..cdbd2a51e1 100644 --- a/docs/getstarted/tips-and-tricks.md +++ b/docs/getstarted/tips-and-tricks.md @@ -968,7 +968,7 @@ Add a logpoint with the **Add Logpoint** command in the left editor gutter and i ### 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. diff --git a/docs/java/java-project.md b/docs/java/java-project.md index b193cbe9bb..1ebfae776c 100644 --- a/docs/java/java-project.md +++ b/docs/java/java-project.md @@ -126,7 +126,7 @@ For Maven project, you can add a dependency by clicking the **+** icon next to * If your project is an unmanaged folder without any build tools. You can manage the dependencies by clicking the **+** icon or the **-** icon on the **Referenced Libraries** node or the items under it, or you can just directly drag your jar libraries to the node `Referenced Libraries` -![manage referenced librares](images/java-project/manage-referenced-libraries.png) +![manage referenced libraries](images/java-project/manage-referenced-libraries.png) > You can also manage the dependencies in the classpath configuration page. See: [Configure classpath for unmanaged folder](#configure-classpath-for-unmanaged-folders) diff --git a/docs/supporting/oss-extensions.md b/docs/supporting/oss-extensions.md index d061d70584..48a98d2773 100644 --- a/docs/supporting/oss-extensions.md +++ b/docs/supporting/oss-extensions.md @@ -66,7 +66,7 @@ As more and more teams in Microsoft contribute extensions, we realize that it ca | [Maven for Java](https://marketplace.visualstudio.com/items/vscjava.vscode-maven) | ✔ | [MIT](https://marketplace.visualstudio.com/items/vscjava.vscode-maven/license) | | [Mezzurite](https://marketplace.visualstudio.com/items/mezzurite-devs.mezzurite) | ✔ | [MIT](https://marketplace.visualstudio.com/items/mezzurite-devs.mezzurite/license) | | [Mono Debug](https://marketplace.visualstudio.com/items/ms-vscode.mono-debug) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-vscode.mono-debug/license) | -| [Nodepad++ Keymap](https://marketplace.visualstudio.com/items/ms-vscode.notepadplusplus-keybindings) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-vscode.notepadplusplus-keybindings/license) | +| [Notepad++ Keymap](https://marketplace.visualstudio.com/items/ms-vscode.notepadplusplus-keybindings) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-vscode.notepadplusplus-keybindings/license) | | [OpenPAI VS Code Client](https://marketplace.visualstudio.com/items/OpenPAIVSCodeClient.pai-vscode) | ✔ | [MIT](https://marketplace.visualstudio.com/items/OpenPAIVSCodeClient.pai-vscode/license) | | [PostgreSQL](https://marketplace.visualstudio.com/items/ms-ossdata.vscode-postgresql) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-ossdata.vscode-postgresql/license) | | [PowerShell](https://marketplace.visualstudio.com/items/ms-vscode.PowerShell) | ✔ | [MIT](https://marketplace.visualstudio.com/items/ms-vscode.PowerShell/license) |