Merge branch 'main' into repo_sync_working_branch

Author: Court72

docs/extensibility/internals/ide-defined-commands-for-extending-project-systems.md

@@ -26,7 +26,7 @@ When you want to extend project systems, you can use commands and command groups
 |IDM_VS_TOOL_PROJWIN|The **Solution Explorer** toolbar.|
 
 ## Shortcut Menus
- The following table shows the shortcut menus that apply when a single node is selected in the **Solution Explorer**, or when there are multiple homogenous selections in the **Solution Explorer**, which is when all selected nodes are of the same type.
+ The following table shows the shortcut menus that apply when a single node is selected in the **Solution Explorer**, or when there are multiple homogeneous selections in the **Solution Explorer**, which is when all selected nodes are of the same type.
 
 |Shortcut menu|Description|
 |-------------------|-----------------|

docs/extensibility/internals/properties-display-grid.md

@@ -22,7 +22,7 @@ The two-column list shows configuration-independent properties that can be chang
 
 2. Set the `pfHide` parameter in <xref:Microsoft.VisualStudio.Shell.Interop.IVsPerPropertyBrowsing.HideProperty%2A> to `TRUE`.
 
-To push information to the **Properties** window, the IDE uses <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer>. <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer> is called by VSPackages for each window that contains selectable objects with related properties to be displayed in the **Properties** window. **Solution Explorer**'s implementation of <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer> calls `GetProperty` using [__VSHPROPID.VSHPROPID_BrowseObject](<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID.VSHPROPID_BrowseObject>) in your project hierarchy to acquire the browseable objects in the hierarchy.
+To push information to the **Properties** window, the IDE uses <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer>. <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer> is called by VSPackages for each window that contains selectable objects with related properties to be displayed in the **Properties** window. **Solution Explorer**'s implementation of <xref:Microsoft.VisualStudio.Shell.Interop.ISelectionContainer> calls `GetProperty` using [__VSHPROPID.VSHPROPID_BrowseObject](<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID.VSHPROPID_BrowseObject>) in your project hierarchy to acquire the browsable objects in the hierarchy.
 
 If your VSPackage does not support [__VSHPROPID.VSHPROPID_BrowseObject](<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID.VSHPROPID_BrowseObject>), the IDE attempts to use <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy.GetProperty%2A> using the value for [__VSHPROPID.VSHPROPID_SelContainer](<xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID.VSHPROPID_SelContainer>) that the hierarchy item or items supply.
 

docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md

@@ -75,7 +75,7 @@ namespace ColumnGuides
 {
     internal static class GuidesSettingsManager
     {
-        // Because my code is always called from the UI thred, this succeeds.
+        // Because my code is always called from the UI thread, this succeeds.
         internal static SettingsManager VsManagedSettingsManager =
             new ShellSettingsManager(ServiceProvider.GlobalProvider);
 

docs/extensibility/walkthrough-publishing-a-visual-studio-extension.md

@@ -227,7 +227,7 @@ You can remove the extension from Visual Studio Marketplace and from your comput
 
 2. In the upper-right hand corner, click **Publish** extensions. Pick the publisher that you used to publish (eg: **TestPublish**). The listing for extensions will appear.
 
-3. Click on extenion menu button → click **Remove**. You are asked to confirm if you want to remove the extension.
+3. Click on extension menu button → click **Remove**. You are asked to confirm if you want to remove the extension.
 
 ![Screenshot that shows Remove menu item.](media/remove-extension.png)
 

docs/get-started/csharp/tutorial-windows-forms-match-game-icons.md

@@ -163,7 +163,7 @@ To get your game to work this way, add a <xref:System.Windows.Forms.Control.Clic
 1. Then, hold the **Ctrl** key while you select each of the other labels.
    Be sure that every label is selected.
 
-1. In the **Properties** window, select the **Events** button, which is a lightening bolt.
+1. In the **Properties** window, select the **Events** button, which is a lightning bolt.
    For the **Click** event, select **label1_Click** in the box.
 
      ![Screenshot shows the Properties window showing Click event.](../media/tutorial-windows-forms-match-game-icons/click-event.png)