Merge pull request #12494 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch main)

Author: Albertyang0

bridge/articles/bridge-to-kubernetes-vs-code.md

@@ -119,7 +119,7 @@ If you're using an AKS cluster that uses managed identity, a security feature pr
 
 Logging output is written to the **Bridge to Kubernetes** window after your development computer is connected to your Kubernetes cluster.
 
-Click on the **Kubernetes** Status bar and choose **Show connection diagnostics information**. This command prints the current environment variables and DNS entires in the logging output.
+Click on the **Kubernetes** Status bar and choose **Show connection diagnostics information**. This command prints the current environment variables and DNS entries in the logging output.
 
 Additionally, you can find the diagnostic logs in the `Bridge to Kubernetes` directory in your development computer's TEMP directory. On Windows 10, that's in `%TEMP%\Bridge to Kubernetes`. On a Mac, the TEMP directory can be found by running `echo $TMPDIR` from a terminal window. On Linux, it is `/tmp/Bridge to Kubernetes`.
 

docs/azure/vs-azure-tools-cloud-service-project-managing-roles.md

@@ -45,7 +45,7 @@ The following steps guide you through removing a web or worker role from an Azur
 
    ![Menu options to add a role to an Azure cloud service](./media/vs-azure-tools-cloud-service-project-managing-roles/remove-role.png)
 
-## Readding a role to an Azure cloud service project
+## Reading a role to an Azure cloud service project
 
 If you remove a role from your cloud service project but later decide to add the role back to the project, only the role declaration and basic attributes, such as endpoints and diagnostics information, are added. No additional resources or references are added to the `ServiceDefinition.csdef` file or to the `ServiceConfiguration.cscfg` file. If you want to add this information, you need to manually add it back into these files.
 

docs/debugger/exception-helper.md

@@ -67,7 +67,7 @@ Starting in Visual Studio 2022 version 17.3, you can view exception stack frames
 ![Exception helper with call stack](media/vs-2022/debugger-exception-helper-call-stack.png)
 ::: moniker-end
 ::: moniker range=">= vs-2022"
-## Get AI asistance
+## Get AI assistance
 
 If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're debugging exceptions. Just look for the **Ask Copilot** ![Screenshot of Ask Copilot button.](../debugger/media/vs-2022/debug-with-copilot-ask-copilot-button.png) button. In these scenarios, Copilot already knows the context for your questions, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
 ::: moniker-end

docs/debugger/not-in-toc/snapshot-debugger-start-page.md

@@ -17,7 +17,7 @@ To use the Snapshot Debugger, set some snappoints in your code, click the button
 
 ## Collect and view snapshots
 
-The Snapshot Debugger collects snapshots from your application. Snapshots are like pictures of your appication at a point in time. You tell Visual Studio when and where to collect a snapshot by setting a snappoint in code. In the snappoint, you set any conditions you need to make sure you get a snapshot of the problem you're investigating.
+The Snapshot Debugger collects snapshots from your application. Snapshots are like pictures of your application at a point in time. You tell Visual Studio when and where to collect a snapshot by setting a snappoint in code. In the snappoint, you set any conditions you need to make sure you get a snapshot of the problem you're investigating.
 
 ### Set a Snappoint
 

docs/deployment/dependency-element-clickonce-application.md

@@ -118,9 +118,9 @@ Identifies a platform or assembly dependency that is required for the applicatio
 
 | Attribute | Description |
 |-----------------------| - |
-| `dependencyType` | Required. Specifies the dependency type. Valid values are `preprequisite` and `install`. An `install` assembly is installed as part of the ClickOnce application. A `prerequisite` assembly must be present in the global assembly cache (GAC) before the ClickOnce application can install. |
+| `dependencyType` | Required. Specifies the dependency type. Valid values are `prerequisite` and `install`. An `install` assembly is installed as part of the ClickOnce application. A `prerequisite` assembly must be present in the global assembly cache (GAC) before the ClickOnce application can install. |
 | `allowDelayedBinding` | Required. Specifies whether the assembly can be loaded programmatically at run time. |
-| `group` | Optional. If the `dependencyType` attribute is set to `install`, designates a named group of assemblies that only install on demand. For more information, see [Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer](../deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api-using-the-designer.md).<br /><br /> If set to `framework` and the `dependencyType` attribute is set to `prerequisite`, designates the assembly as part of the .NET Framework. The global assemby cache (GAC) is not checked for this assembly when installing on .NET Framework 4 and later versions. |
+| `group` | Optional. If the `dependencyType` attribute is set to `install`, designates a named group of assemblies that only install on demand. For more information, see [Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer](../deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api-using-the-designer.md).<br /><br /> If set to `framework` and the `dependencyType` attribute is set to `prerequisite`, designates the assembly as part of the .NET Framework. The global assembly cache (GAC) is not checked for this assembly when installing on .NET Framework 4 and later versions. |
 | `codeBase` | Required when the `dependencyType` attribute is set to `install`. The path to the dependent assembly. May be either an absolute path, or a path relative to the manifest's code base. This path must be a valid URI in order for the assembly manifest to be valid. |
 | `size` | Required when the `dependencyType` attribute is set to `install`. The size of the dependent assembly, in bytes. |
 

docs/extensibility/adding-a-toolbar-to-a-tool-window.md

@@ -17,7 +17,7 @@ This walkthrough shows how to add a toolbar to a tool window.
 
  A toolbar is a horizontal or vertical strip that contains buttons bound to commands. The length of a toolbar in a tool window is always the same as the width or height of the tool window, depending on where the toolbar is docked.
 
- Unlike toolbars in the IDE, a toolbar in a tool window must be docked and cannot be moved or customized. If the VSPackage is written in umanaged code, the toolbar can be docked on any edge.
+ Unlike toolbars in the IDE, a toolbar in a tool window must be docked and cannot be moved or customized. If the VSPackage is written in unmanaged code, the toolbar can be docked on any edge.
 
  For more information about how to add a toolbar, see [Adding a toolbar](../extensibility/adding-a-toolbar.md).
 

docs/extensibility/adding-and-removing-property-pages.md

@@ -119,7 +119,7 @@ A project subtype frequently needs to display additional property pages in the P
     class DeployPropertyPage : Form, Microsoft.VisualStudio.OLE.Interop.IPropertyPage
     {
         . . . .
-        //Summary: Return a stucture describing your property page.
+        //Summary: Return a structure describing your property page.
         public void GetPageInfo(Microsoft.VisualStudio.OLE.Interop.PROPPAGEINFO[] pPageInfo)
         {
             PROPPAGEINFO info = new PROPPAGEINFO();
@@ -141,7 +141,7 @@ A project subtype frequently needs to display additional property pages in the P
     Class DeployPropertyPage
             Inherits Form
             Implements Microsoft.VisualStudio.OLE.Interop.IPropertyPage
-        'Summary: Return a stucture describing your property page.
+        'Summary: Return a structure describing your property page.
         ....
         Public Sub GetPageInfo(ByVal pPageInfo As Microsoft.VisualStudio.OLE.Interop.PROPPAGEINFO())
             Dim info As PROPPAGEINFO = New PROPPAGEINFO()

docs/extensibility/creating-a-software-development-kit.md

@@ -49,7 +49,7 @@ Platform SDKs have the following layout:
 | *DesignTime* folder | Contains files that are needed only at pre-run/debugging time. These could include XML docs, libraries, headers, Toolbox design-time binaries, MSBuild artifacts, and so forth<br /><br /> XML docs would, ideally, be placed in the *\DesignTime* folder, but XML docs for references will continue to be placed alongside the reference file in Visual Studio. For example, the XML doc for a reference<em>\References\\[config]\\[arch]\sample.dll</em> will be *\References\\[config]\\[arch]\sample.xml*, and the localized version of that doc will be *\References\\[config]\\[arch]\\[locale]\sample.xml*. |
 | *Configuration* folder | There can be only three folders: *Debug*, *Retail* and *CommonConfiguration*. SDK authors can place their files under *CommonConfiguration* if the same set of SDK files should be consumed, regardless of the configuration that the SDK consumer will target. |
 | *Architecture* folder | Any supported *architecture* folder can exist. Visual Studio supports the following architectures: x86, x64, ARM, and neutral. Note: Win32 maps to x86, and AnyCPU maps to neutral.<br /><br /> MSBuild looks only under *\CommonConfiguration\neutral* for Platform SDKs. |
-| *SDKManifest.xml* | This file describes how Visual Studio should consume the SDK. Look at the SDK Manifest for Windows 8.1:<br /><br /> `<FileList             DisplayName = "Windows"             PlatformIdentity = "Windows, version=8.1"             TargetFramework = ".NET for Windows Store apps, version=v4.5.1; .NET Framework, version=v4.5.1"             MinVSVersion = "14.0">              <File Reference = "Windows.winmd">                <ToolboxItems VSCategory = "Toolbox.Default" />             </File> </FileList>`<br /><br /> **DisplayName:** The value that the Object Browser displays in the Browse list.<br /><br /> **PlatformIdentity:** The existence of this attribute tells Visual Studio and MSBuild that the SDK is a platform SDK and that the references added from it shouldn't be copied locally.<br /><br /> **TargetFramework:** This attribute is used by Visual Studio to ensure that only projects that target the same Frameworks as specified in the value of this attribute can consume the SDK.<br /><br /> **MinVSVersion:** This attribute is used by Visual Studio to consume only the SDKs that apply to it.<br /><br /> **Reference:** This attribute must to be specified for only those references that contain controls. For information about how to specify whether a reference contains controls, see below. |
+| *SDKManifest.xml* | This file describes how Visual Studio should consume the SDK. Look at the SDK Manifest for Windows 8.1:<br /><br /> `<FileList             DisplayName = "Windows"             PlatformIdentity = "Windows, version=8.1"             TargetFramework = ".NET for Windows Store apps, version=v4.5.1; .NET Framework, version=v4.5.1"             MinVSVersion = "14.0">              <File Reference = "Windows.winmd">                <ToolboxItems VSCategory = "Toolbox.Default" />             </File> </FileList>`<br /><br /> **DisplayName:** The value that the Object Browser displays in the Browse list.<br /><br /> **PlatformIdentity:** The existence of this attribute tells Visual Studio and MSBuild that the SDK is a platform SDK and that the references added from it shouldn't be copied locally.<br /><br /> **TargetFramework:** This attribute is used by Visual Studio to ensure that only projects that target the same Frameworks as specified in the value of this attribute can consume the SDK.<br /><br /> **MinVSVersion:** This attribute is used by Visual Studio to consume only the SDKs that apply to it.<br /><br /> **Reference:** This attribute must be specified for only those references that contain controls. For information about how to specify whether a reference contains controls, see below. |
 
 ## Extension SDKs
 

docs/extensibility/debugger/reference/idebugcomplussymbolprovider-getattributedclassesforlanguage.md

@@ -140,7 +140,7 @@ HRESULT CDebugSymbolProvider::GetAttributedClassesForLanguage(
                     &pUnused,
                     &cbUnused ) == S_OK)
             {
-                // Only return classes implemeted in the correct language
+                // Only return classes implemented in the correct language
 
                 if (pModule->ClassImplementedInLanguage( rgTypeDefs[iTypeDef],
                         guidLanguage) )

docs/extensibility/debugger/reference/idebugsettingscallback2-geteelocalobject.md

@@ -15,7 +15,7 @@ dev_langs:
 ---
 # IDebugSettingsCallback2::GetEELocalObject
 
-Retrieves a expression evaluator local object given the metric name.
+Retrieves an expression evaluator local object given the metric name.
 
 ## Syntax
 

docs/extensibility/debugger/reference/idebugsettingscallback2-geteemetricguid.md

@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the unique identifier for a expression evaluator metric given its name."
+description: "Retrieves the unique identifier for an expression evaluator metric given its name."
 title: IDebugSettingsCallback2::GetEEMetricGuid
 ms.date: 11/04/2016
 ms.topic: reference
@@ -15,7 +15,7 @@ dev_langs:
 ---
 # IDebugSettingsCallback2::GetEEMetricGuid
 
-Retrieves the unique identifier for a expression evaluator metric given its name.
+Retrieves the unique identifier for an expression evaluator metric given its name.
 
 ## Syntax
 

docs/extensibility/debugger/reference/idebugsymbolsearchevent2-getsymbolsearchinfo.md

@@ -56,7 +56,7 @@ HRESULT GetSymbolSearchInfo(
  If successful, returns `S_OK`; otherwise returns an error code.
 
 ## Remarks
- When a handler receives the [IDebugSymbolSearchEvent2](../../../extensibility/debugger/reference/idebugsymbolsearchevent2.md) event after an attempt is made to load debugging symbols for a module, the handler can call thismethod to determine the results of that load.
+ When a handler receives the [IDebugSymbolSearchEvent2](../../../extensibility/debugger/reference/idebugsymbolsearchevent2.md) event after an attempt is made to load debugging symbols for a module, the handler can call this method to determine the results of that load.
 
 ## See also
 - [IDebugModule3](../../../extensibility/debugger/reference/idebugmodule3.md)

docs/extensibility/how-to-use-rule-based-ui-context-for-visual-studio-extensions.md

@@ -133,7 +133,7 @@ Here are the various types of term that are supported:
 |ActiveProjectCapability:\<Expression>|The term is true when active project capabilities match the provided expression. An expression can be something like VB &#124; CSharp.|
 |SolutionHasProjectCapability:\<Expression>|Similar to above but term is true when solution has any loaded project that matches to the expression.|
 |SolutionHasProjectFlavor:\<projectTypeGuid>|The term will be true whenever a solution has project that is flavored (aggregated) and has a flavor matching the given project type GUID.|
-|ProjectAddedItem:\<pattern>| The term is true when a file matching the "pattern" is added to a project in the soluion that is opened.|
+|ProjectAddedItem:\<pattern>| The term is true when a file matching the "pattern" is added to a project in the solution that is opened.|
 |ActiveProjectOutputType:\<outputType>|The term is true when output type for active project matches exactly.  The outputType could be an integer or a <xref:Microsoft.VisualStudio.Shell.Interop.__VSPROJOUTPUTTYPE> type.|
 |ActiveProjectBuildProperty:\<buildProperty>=\<regex>|The term is true when active project has the specified build property and property value matches to regex filter provided. Refer to [Persisting Data in MSBuild Project Files](internals/persisting-data-in-the-msbuild-project-file.md) for more details on build properties.|
 |SolutionHasProjectBuildProperty:\<buildProperty>=\<regex>|The term is true when solution has a loaded project with the specified build property and property value matches to regex filter provided.|

docs/extensibility/internals/microsoft-help-viewer-sdk.md

@@ -545,7 +545,7 @@ The branding.js file contains JavaScript used by the Visual Studio Help Viewer b
 
 **HTM FILES**
 
-The branding package contains a set of HTM files that support scenarios for communicating key information to Help content users, for example a homepage that contains a section describing which content sets are installed and pages telling the user when topics cannot be found in the local set of topics. These HTM files can be modified per product.  ISO Shell vendors are able to take the default branding package and change the behavior and content of these pages to suite their need.  These files refer to their respective branding package in order for the branding tags to get the corresponding content from the branding.xml file.
+The branding package contains a set of HTM files that support scenarios for communicating key information to Help content users, for example a homepage that contains a section describing which content sets are installed and pages telling the user when topics cannot be found in the local set of topics. These HTM files can be modified per product.  ISO Shell vendors are able to take the default branding package and change the behavior and content of these pages to suit their need.  These files refer to their respective branding package in order for the branding tags to get the corresponding content from the branding.xml file.
 
 |**File**|**Use**|**Displayed Content Source**|
 |-|-|-|

docs/extensibility/internals/test-area-7-share.md

@@ -15,7 +15,7 @@ ms.subservice: extensibility-integration
 
 This test area covers sharing items between locations via the **Share** command.
 
- A hhare operation is the apparent duplication of files and folder items between two or more locations within a source control file hierarchy. Duplication does not really occur on the server, but the user does see the same file in two or more specified locations. Whenever changes are made to any of the shared items, those changes appear in all other shared locations.
+ A share operation is the apparent duplication of files and folder items between two or more locations within a source control file hierarchy. Duplication does not really occur on the server, but the user does see the same file in two or more specified locations. Whenever changes are made to any of the shared items, those changes appear in all other shared locations.
 
  Sharing into folders works if you select a folder with at least one file under source control in it. The share command is disabled under the following conditions:
 

docs/extensibility/persisting-the-property-of-a-project-item.md

@@ -68,7 +68,7 @@ You may want to persist a property you add to a project item, such as the author
     try
     {
         // Get the current project hierarchy, project item, and selection container for the current selection
-        // If the selection spans multiple hierachies, hierarchyPtr is Zero
+        // If the selection spans multiple hierarchies, hierarchyPtr is Zero
         IVsMultiItemSelect multiItemSelect = null;
         ErrorHandler.ThrowOnFailure(
             monitorSelection.GetCurrentSelection(

docs/extensibility/ux-guidelines/ui-text-and-help-for-visual-studio.md

@@ -192,7 +192,7 @@ ms.subservice: extensibility-integration
 
   - Does the user use the same vocabulary as this error?
 
-  - Is this error ambigious or shared in multiple situations? If so, how do you guide users to the solution they need?
+  - Is this error ambiguous or shared in multiple situations? If so, how do you guide users to the solution they need?
 
 #### Build errors
  Since Visual Studio is a software development tool, many of its components have a compilation, converting, or encoding step to convert the developer's work to binary form. These conversions can cause errors when the compiler cannot process improperly authored files or when compiler options weren't set correctly.

docs/extensibility/visualstudio.extensibility/visualstudio-extensibility.md

@@ -111,7 +111,7 @@ There are a few of our APIs that don't yet meet this bar for stability, for one
 * The API is new and we want to incorporate user feedback into the deisgn before marking it stable.
 * We've received feedback that a particular API is difficult to use, so we're planning on updating it in future versions.
 
-For these APIs, we've explicitly labeled them using the `[Experimental]` attribute to help extension authors create their extensions with confidence in the the SDK.
+For these APIs, we've explicitly labeled them using the `[Experimental]` attribute to help extension authors create their extensions with confidence in the SDK.
 
 For more information, including how to use experimental APIs, please see our [Experimental APIs](https://github.com/microsoft/VSExtensibility/blob/main/docs/experimental_apis.md) page.
 

docs/ide/file-nesting-solution-explorer.md

@@ -17,7 +17,7 @@ ms.subservice: general-ide
 
 > [!NOTE]
 > In Visual Studio 2022 version 17.2 and earlier, this feature was only supported for ASP.NET Core projects.
-> In version 17.3 and later the projects targetting .NET support file nesting. 
+> In version 17.3 and later the projects targeting .NET support file nesting. 
 
 ## File nesting options