Merge pull request #10200 from Blake-Madden/main

Fix a few typos

Author: ghogen

docs/azure/vs-azure-tools-migrate-publish-web-app-to-cloud-service.md

@@ -83,7 +83,7 @@ The following table provides details about starting the application in Azure:
 
 ## Update a Connection String for ASP.NET Dynamic Entities
 
-1. Create a SQL Azure database for a ASP.NET Dynamic Entities web application as described earlier in (#use-an-azuresql-database-for-your-application).
+1. Create a SQL Azure database for an ASP.NET Dynamic Entities web application as described earlier in (#use-an-azuresql-database-for-your-application).
 1. Add the tables and fields that you need for this database from the Azure portal.
 1. Specify a connection string in the `web.config` file with the following format and save the file:
 

docs/data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md

@@ -111,7 +111,7 @@ You can use the WCF Visual Studio templates as a foundation to quickly create yo
 
 #### WCF Templates
 
-WCF Visual Studio templates provide a basic class structure for service development. Several WCF templates are available in the **Add New Project** dialog box. These include WCF service lLibrary projects, WCF service websites, and WCF Service item templates.
+WCF Visual Studio templates provide a basic class structure for service development. Several WCF templates are available in the **Add New Project** dialog box. These include WCF service library projects, WCF service websites, and WCF Service item templates.
 
 When you select a template, files are added for a service contract, a service implementation, and a service configuration. All necessary attributes are already added, creating a simple "Hello World" type of service, and you did not have to write any code. You will, of course, want to add code to provide functions and methods for your real world service, but the templates provide the basic foundation.
 

docs/debugger/create-custom-views-of-native-objects.md

@@ -161,7 +161,7 @@ Natvis visualizations use C++ expressions to specify the data items to display.
 
 - Natvis expressions don't allow function evaluation or side effects. Function calls and assignment operators are ignored. Because [debugger intrinsic functions](../debugger/expressions-in-the-debugger.md#BKMK_Using_debugger_intrinisic_functions_to_maintain_state) are side-effect free, they might be freely called from any Natvis expression, even though other function calls are disallowed.
 
-- To control how an expression displays, you can use any of the format specifiers described in [Format specifiers in C++](format-specifiers-in-cpp.md#BKMK_Visual_Studio_2012_format_specifiers). Format specifiers are ignored when the entry is used internally by Natvis, such as the `Size` expression in a [ArrayItems expansion](../debugger/create-custom-views-of-native-objects.md#BKMK_ArrayItems_expansion).
+- To control how an expression displays, you can use any of the format specifiers described in [Format specifiers in C++](format-specifiers-in-cpp.md#BKMK_Visual_Studio_2012_format_specifiers). Format specifiers are ignored when the entry is used internally by Natvis, such as the `Size` expression in an [ArrayItems expansion](../debugger/create-custom-views-of-native-objects.md#BKMK_ArrayItems_expansion).
 
 >[!NOTE]
 > Because the Natvis document is XML, your expressions cannot directly use the ampersand, greater than, less than, or shift operators. You must escape these characters in both the item body and the condition statements. For example:<br>

docs/debugger/using-the-tasks-window.md

@@ -46,7 +46,7 @@ The columns in the **Tasks** window show the following information.
 |**Flags**|Shows which tasks are flagged and lets you flag or unflag a task.|
 |**Icons**|A yellow arrow indicates the current task. The current task is the top-most task on the current thread.<br /><br /> A white arrow indicates the breaking task, that is, the one that was current when the debugger was invoked.<br /><br /> The pause icon indicates a task that has been frozen by the user. You can freeze and unfreeze a task by right-clicking it in the list.|
 |**ID**|A system-provided number for the task. In native code, this is the address of the task.|
-|**Status**|The current state (scheduled, active, blocked, deadlocked, awaiting, or completed) of the task. A scheduled task is one that has not yet been run and, therefore, does not yet have a call stack, assigned thread, or related information.<br /><br /> A active task is one that was executing code before breaking in the debugger.<br /><br /> An awaiting or blocked task is one that is blocked because it is waiting on an event to be signaled, a lock to be released, or another task to finish.<br /><br /> A deadlocked task is a waiting task whose thread is deadlocked with another thread.<br /><br /> Hover over the **Status** cell for a deadlocked or awaiting task to see more information about the block. **Warning:**  The **Tasks** window reports deadlock only for a blocked task that uses a synchronization primitive that is supported by Wait Chain Traversal (WCT). For example, for a deadlocked <xref:System.Threading.Tasks.Task> object, which uses WCT, the debugger reports **Awaiting-deadlocked**. For a deadlocked task that is managed by the Concurrency Runtime, which does not use WCT, the debugger reports **Waiting**. For more information about WCT, see [Wait Chain Traversal](/windows/desktop/Debug/wait-chain-traversal).|
+|**Status**|The current state (scheduled, active, blocked, deadlocked, awaiting, or completed) of the task. A scheduled task is one that has not yet been run and, therefore, does not yet have a call stack, assigned thread, or related information.<br /><br /> An active task is one that was executing code before breaking in the debugger.<br /><br /> An awaiting or blocked task is one that is blocked because it is waiting on an event to be signaled, a lock to be released, or another task to finish.<br /><br /> A deadlocked task is a waiting task whose thread is deadlocked with another thread.<br /><br /> Hover over the **Status** cell for a deadlocked or awaiting task to see more information about the block. **Warning:**  The **Tasks** window reports deadlock only for a blocked task that uses a synchronization primitive that is supported by Wait Chain Traversal (WCT). For example, for a deadlocked <xref:System.Threading.Tasks.Task> object, which uses WCT, the debugger reports **Awaiting-deadlocked**. For a deadlocked task that is managed by the Concurrency Runtime, which does not use WCT, the debugger reports **Waiting**. For more information about WCT, see [Wait Chain Traversal](/windows/desktop/Debug/wait-chain-traversal).|
 |**Start Time**|The time at which the task became active.|
 |**Duration**|The number of seconds that the task has been active.|
 |**Completion Time**|The time at which the task completed.|

docs/debugger/view-data-in-tabular-visualizer.md

@@ -30,7 +30,7 @@ To open the visualizer, you must be paused during debugging.
 You can access the visualizer by clicking on the magnifying glass icon that appears next to the Value for one of those objects ![VisualizerIcon](../debugger/media/dbg-tips-visualizer-icon.png "Visualizer icon")
 in a debugger variables window or in a DataTip.
 
-:::image type="content" source="../debugger/media/vs-2022/dbg-ienumerable-debugger-visualizer.png" alt-text="Diagram of Open a IEnumerable visualizer.":::
+:::image type="content" source="../debugger/media/vs-2022/dbg-ienumerable-debugger-visualizer.png" alt-text="Diagram of Open an IEnumerable visualizer.":::
 
 ## DataSet visualizer 
 

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

@@ -95,7 +95,7 @@ HRESULT CEnvBlock::ParseText(
     if (pszAnsiCode) {
         // Map the wide-character pszCode string to the new pszAnsiCode character string.
         WideCharToMultiByte(CP_ACP, 0, pszCode, -1, pszAnsiCode, iAnsiLen, NULL, NULL);
-        // Check to see if the app can succesfully get the environment variable.
+        // Check to see if the app can successfully get the environment variable.
         if (GetEnv(pszAnsiCode)) {
 
             // Create and initialize a CExpression object.
@@ -108,7 +108,7 @@ HRESULT CEnvBlock::ParseText(
             *ppExpr = pExpr;
             (*ppExpr)->AddRef();
             hr = S_OK;
-        // If the program cannot succesfully get the environment variable.
+        // If the program cannot successfully get the environment variable.
         } else {
             // Set the errror message and return E_FAIL.
             *pbstrError = SysAllocString(L"No such environment variable.");

docs/extensibility/debugger/reference/idebugexpressionevaluator2-preloadmodules.md

@@ -45,7 +45,7 @@ If successful, returns `S_OK`; otherwise, returns an error code.
 This optional method is used when you do a hosting-process attach. It gives the EE a chance to 'warm up' as part of the attach.
 
 ## Example
-The following example shows how to implement this method for a **ExpressionEvaluatorPackage** object that exposes the [IDebugExpressionEvaluator2](../../../extensibility/debugger/reference/idebugexpressionevaluator2.md) interface.
+The following example shows how to implement this method for an **ExpressionEvaluatorPackage** object that exposes the [IDebugExpressionEvaluator2](../../../extensibility/debugger/reference/idebugexpressionevaluator2.md) interface.
 
 ```cpp
 STDMETHODIMP ExpressionEvaluatorPackage::PreloadModules

docs/extensibility/debugger/reference/idebugexpressionevaluator2-setcorpath.md

@@ -42,7 +42,7 @@ HRESULT SetCorPath(
  If successful, returns `S_OK`; otherwise, returns an error code.
 
 ## Example
- The following example shows how to implement this method for a **ExpressionEvaluatorPackage** object that exposes the [IDebugExpressionEvaluator2](../../../extensibility/debugger/reference/idebugexpressionevaluator2.md) interface.
+ The following example shows how to implement this method for an **ExpressionEvaluatorPackage** object that exposes the [IDebugExpressionEvaluator2](../../../extensibility/debugger/reference/idebugexpressionevaluator2.md) interface.
 
 ```cpp
 STDMETHODIMP ExpressionEvaluatorPackage::SetCorPath(LPCOLESTR pcstrCorPath)

docs/extensibility/debugger/reference/idebugportnotify2-removeprogramnode.md

@@ -37,7 +37,7 @@ HRESULT RemoveProgramNode( 
 
 ## Parameters
 `pProgramNode`\
-[in] An [IDebugProgramNode2](../../../extensibility/debugger/reference/idebugprogramnode2.md) objecy that represents the program to be unregistered.
+[in] An [IDebugProgramNode2](../../../extensibility/debugger/reference/idebugprogramnode2.md) object that represents the program to be unregistered.
 
 ## Return Value
  If successful, returns `S_OK`; otherwise, returns an error code.

docs/extensibility/debugger/reference/idebugsettingscallback2.md

@@ -29,10 +29,10 @@ The following table shows the methods of `IDebugSettingsCallback2`.
 |Method|Description|
 |------------|-----------------|
 |[EnumEEs](../../../extensibility/debugger/reference/idebugsettingscallback2-enumees.md)|Enumerates the available expression evaluators given the language and vendor identifiers.|
-|[GetEELocalObject](../../../extensibility/debugger/reference/idebugsettingscallback2-geteelocalobject.md)|Retrieves a expression evaluator local object given the metric.|
+|[GetEELocalObject](../../../extensibility/debugger/reference/idebugsettingscallback2-geteelocalobject.md)|Retrieves an expression evaluator local object given the metric.|
 |[GetEEMetricDword](../../../extensibility/debugger/reference/idebugsettingscallback2-geteemetricdword.md)|Retrieves a value that corresponds to the specified metric of the expression evaluator.|
 |[GetEEMetricFile](../../../extensibility/debugger/reference/idebugsettingscallback2-geteemetricfile.md)|Retrieves the expression evaluator metric file given the name or the metric.|
-|[GetEEMetricGuid](../../../extensibility/debugger/reference/idebugsettingscallback2-geteemetricguid.md)|Retrieves the unique identifier for a expression evaluator metric given its name.|
+|[GetEEMetricGuid](../../../extensibility/debugger/reference/idebugsettingscallback2-geteemetricguid.md)|Retrieves the unique identifier for an expression evaluator metric given its name.|
 |[GetEEMetricString](../../../extensibility/debugger/reference/idebugsettingscallback2-geteemetricstring.md)|Retrieves the value string of an expression evaluator metric given its name.|
 |[GetMetricDword](../../../extensibility/debugger/reference/idebugsettingscallback2-getmetricdword.md)|Retrieves the value of a metric given its name.|
 |[GetMetricGuid](../../../extensibility/debugger/reference/idebugsettingscallback2-getmetricguid.md)|Retrieves the unique identifier of a metric given its name.|

docs/extensibility/debugger/reference/idebugstopcompleteevent2.md

@@ -26,7 +26,7 @@ This interface was introduced with Visual Studio 2005. Prior releases did not su
 
 - [Stop](../../../extensibility/debugger/reference/idebugengineprogram2-stop.md) is called by the SDM in multi-process or multi-program scenarios. When one program sends a stopping event to the SDM, the SDM requests other programs to stop, too.
 
-Stop is used to asynchronously inform the SDM that a program has stopped. Informing the SDM is useful for an interpreter debug engine, where sometimes no code is running inside the debugged program, so [Stop](../../../extensibility/debugger/reference/idebugengineprogram2-stop.md) can not be completed synchronously. If a debug engine wants to employ this asynchronous notification, it must return `S_ASYNC_STOP` from [Stop](../../../extensibility/debugger/reference/idebugengineprogram2-stop.md).
+Stop is used to asynchronously inform the SDM that a program has stopped. Informing the SDM is useful for an interpreter debug engine, where sometimes no code is running inside the debugged program, so [Stop](../../../extensibility/debugger/reference/idebugengineprogram2-stop.md) can't be completed synchronously. If a debug engine wants to employ this asynchronous notification, it must return `S_ASYNC_STOP` from [Stop](../../../extensibility/debugger/reference/idebugengineprogram2-stop.md).
 
 ## Requirements
 

docs/extensibility/internals/rdt-readlock-usage.md

@@ -25,7 +25,7 @@ Generally, you use [_VSRDTFLAGS.RDT_ReadLock](<xref:Microsoft.VisualStudio.Shell
 
 ## How to Manage Visible and Invisible Documents
 
-When a user opens a document in the UI, an <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> owner for the document must be established and an [_VSRDTFLAGS.RDT_EditLock](<xref:Microsoft.VisualStudio.Shell.Interop._VSRDTFLAGS.RDT_EditLock>) flag must be set. If no <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> owner can be established, then the document will not be saved when the user clicks **Save All** or closes the IDE. This means if a document is open invisibly where it is modified in memory, and the user is prompted to save the document on shutdown or saved if **Save All** is chosen, then an `RDT_ReadLock` cannot be used. Instead, you must use an `RDT_EditLock` and register a <xref:Microsoft.VisualStudio.Shell.Interop.IVsDocumentLockHolder> when an [__VSREGDOCLOCKHOLDER.RDLH_WeakLockHolder](<xref:Microsoft.VisualStudio.Shell.Interop.__VSREGDOCLOCKHOLDER.RDLH_WeakLockHolder>) flag.
+When a user opens a document in the UI, an <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> owner for the document must be established and a [_VSRDTFLAGS.RDT_EditLock](<xref:Microsoft.VisualStudio.Shell.Interop._VSRDTFLAGS.RDT_EditLock>) flag must be set. If no <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy> owner can be established, then the document will not be saved when the user clicks **Save All** or closes the IDE. This means if a document is open invisibly where it is modified in memory, and the user is prompted to save the document on shutdown or saved if **Save All** is chosen, then an `RDT_ReadLock` cannot be used. Instead, you must use an `RDT_EditLock` and register a <xref:Microsoft.VisualStudio.Shell.Interop.IVsDocumentLockHolder> when a [__VSREGDOCLOCKHOLDER.RDLH_WeakLockHolder](<xref:Microsoft.VisualStudio.Shell.Interop.__VSREGDOCLOCKHOLDER.RDLH_WeakLockHolder>) flag.
 
 ## RDT_EditLock and Document Modification
 

docs/extensibility/internals/upgrading-projects.md

@@ -91,7 +91,7 @@ The following scenarios arise with project upgrades:
 
 ### IVsProjectUpgrade Implementation
 
-If your project system implements <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> only, it can not participate in the **Visual Studio Conversion Wizard**. However, even if you implement the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory> interface, you can still delegate the file upgrade to <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> implementation.
+If your project system implements <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> only, it can't participate in the **Visual Studio Conversion Wizard**. However, even if you implement the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgradeViaFactory> interface, you can still delegate the file upgrade to <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectUpgrade> implementation.
 
 #### To implement IVsProjectUpgrade
 

docs/extensibility/strings-used-as-keys-for-finding-a-source-control-plug-in.md

@@ -34,7 +34,7 @@ The following strings are the keys for accessing the registry to find informatio
 |`SCC_KEY`|SCC|
 |`SCC_FILE_SIGNATURE`|A source code control file|
 |`SCC_NSE`|Namespace extension|
-|`SCC_NSE_PREFIX`|Protocal Prefix|
+|`SCC_NSE_PREFIX`|Protocol Prefix|
 |`SCC_NSE_DisableOpenSCC`|DisableOpenFromSourceControl|
 |`STR_SCCHELPCOLLECTION`|HelpCollection|
 |`STR_UI_LANGUAGE`|UILanguage|

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

@@ -108,7 +108,7 @@ Starting with our 17.9 release, we're ready to label the vast majority of our AP
 
 There are a few of our APIs that don't yet meet this bar for stability, for one of several reasons:
 * The feature area is new and additional features and changes are expected in future versions.
-* The API is new and we want to incorporate user feedback into the deisgn before marking it stable.
+* The API is new and we want to incorporate user feedback into the design 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 SDK.

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

@@ -106,7 +106,7 @@ namespace ColumnGuides
         {
             if (!IsValidColumn(column))
                 throw new ArgumentOutOfRangeException(
-                    "column", "The paramenter must be between 1 and 10,000");
+                    "column", "The parameter must be between 1 and 10,000");
             var columns = GuidesSettingsManager.GetColumnOffsets();
             if (! columns.Remove(column))
             {
@@ -1096,7 +1096,7 @@ namespace ColumnGuides
         }
 
         /// <summary>
-        /// This function is the callback used to execute a command when the a menu item
+        /// This function is the callback used to execute a command when a menu item
         /// is clicked. See the Initialize method to see how the menu item is associated
         /// to this function using the OleMenuCommandService service and the MenuCommand
         /// class.

docs/ide/copilot-chat-context.md

@@ -74,7 +74,7 @@ Here are some examples of using references for context control:
 
 ## <a name="find-context"></a>Review the sources used by Copilot Chat
 
-Copilot Chat displays the context it used after every result, so that you can tell what was taken into account when answering your question. When you ask a Copilot Chat a question and get a response in the chat window, an **References** dropdown appears below the response. The entries in the **References** dropdown list show you the context referenced by Copilot Chat to generate that response. This information can help you modify your question to get better and more relevant answers.
+Copilot Chat displays the context it used after every result, so that you can tell what was taken into account when answering your question. When you ask a Copilot Chat a question and get a response in the chat window, a **References** dropdown appears below the response. The entries in the **References** dropdown list show you the context referenced by Copilot Chat to generate that response. This information can help you modify your question to get better and more relevant answers.
 
 :::image type="content" source="media/vs-2022/copilot-chat-context/copilot-chat-references-used-dropdown.png" alt-text="Screenshot of References used dropdown in Copilot Chat." lightbox="media/vs-2022/copilot-chat-context/copilot-chat-references-used-dropdown.png":::