Merge pull request #13990 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

docs/containers/container-launch-settings.md

@@ -83,7 +83,7 @@ The following table shows the properties that can be set in this section:
 
 Not all settings are available in the UI, for example, `useSSL`. To change those settings, edit `launchSettings.json` directly.
 
-The setting `DockerfileRunArguments` is superceded in Visual Studio 2022 17.12 and later by `containerRunArguments`, which can be set in the Launch Profiles UI as `Container run arguments`.
+The setting `DockerfileRunArguments` is superseded in Visual Studio 2022 17.12 and later by `containerRunArguments`, which can be set in the Launch Profiles UI as `Container run arguments`.
 
 > [!NOTE]
 > If the same setting is found in both the project file and in the launch settings file, the value in the launch settings file takes precedence.

docs/extensibility/debugger/reference/idebugbreakpointchecksumrequest2-getchecksum.md

@@ -85,7 +85,7 @@ bool CDebugProgram::DoChecksumsMatch(CDebugPendingBreakpoint *pPending, CDebugCo
                 CoTaskMemFree(data.pBytes);
             }
             else
-                fRet = true; // checksums not available - user disabed checksums
+                fRet = true; // checksums not available - user disabled checksums
         }
         else
             fRet = true; // we couldn't get checksum from UI - default to past behavior

docs/extensibility/debugger/reference/idebugexpressioncontext2-parsetext.md

@@ -110,7 +110,7 @@ HRESULT CEnvBlock::ParseText(
             hr = S_OK;
         // If the program cannot successfully get the environment variable.
         } else {
-            // Set the errror message and return E_FAIL.
+            // Set the error message and return E_FAIL.
             *pbstrError = SysAllocString(L"No such environment variable.");
             hr = E_FAIL;
         }

docs/extensibility/visualstudio.extensibility/inside-the-sdk/advanced-remote-ui.md

@@ -365,7 +365,7 @@ With the code above, the `Color` property value is converted to a `LinearGradien
 
 ## Remote UI and threads
 
-*Async command* callbacks (and `INotifyPropertyChanged` callbacks for values updated by the UI through data biding) are raised on random thread pool threads. Callbacks are raised one at a time and won't overlap until the code yields control (using an `await` expression).
+*Async command* callbacks (and `INotifyPropertyChanged` callbacks for values updated by the UI through data binding) are raised on random thread pool threads. Callbacks are raised one at a time and won't overlap until the code yields control (using an `await` expression).
 
 This behavior can be changed by passing a [NonConcurrentSynchronizationContext](/dotnet/api/microsoft.visualstudio.threading.nonconcurrentsynchronizationcontext) to the [`RemoteUserControl`](/dotnet/api/microsoft.visualstudio.extensibility.ui.remoteusercontrol) constructor. In that case, you can use the provided synchronization context for all *async command* and `INotifyPropertyChanged` callbacks related to that control.
 

docs/extensibility/visualstudio.extensibility/tool-window/tool-window.md

@@ -46,7 +46,7 @@ The [`ToolWindow`](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.
 | --------- |----- | -------- | ----------- | ------------- |
 | [Placement](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowconfiguration.placement#microsoft-visualstudio-extensibility-toolwindows-toolwindowconfiguration-placement) | ToolWindowPlacement | No | The location in Visual Studio where the tool window should be opened the first time. [`ToolWindowPlacement.DockedTo`](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowplacement.dockedto) allows docking the tool window to a GUID matching an old VSIX-style tool window ID. See more about [ToolWindowPlacement](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowplacement). | ToolWindowPlacement.Floating |
 | [DockDirection](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowconfiguration.dockdirection#microsoft-visualstudio-extensibility-toolwindows-toolwindowconfiguration-dockdirection) | Dock | No | The direction relative to the placement where the tool window should be docked when opened the first time. See [Dock](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.dock). | Dock.None |
-| [AllowAutoCreation](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowconfiguration.allowautocreation#microsoft-visualstudio-extensibility-toolwindows-toolwindowconfiguration-allowautocreation) | Bool | No | Specifies whether or not the tool window can be created automatically. Setting this paramater to false means that tool windows that are open when Visual Studio closes don't automatically restore when Visual Studio is opened again. | `true` |
+| [AllowAutoCreation](/dotnet/api/microsoft.visualstudio.extensibility.toolwindows.toolwindowconfiguration.allowautocreation#microsoft-visualstudio-extensibility-toolwindows-toolwindowconfiguration-allowautocreation) | Bool | No | Specifies whether or not the tool window can be created automatically. Setting this parameter to false means that tool windows that are open when Visual Studio closes don't automatically restore when Visual Studio is opened again. | `true` |
 
 ### Example