Repo sync for protected CLA branch

docs/debugger/debug-using-the-just-in-time-debugger.md

@@ -52,15 +52,15 @@ Just-In-Time debugging may still be enabled even if Visual Studio is no longer i
 
 1. From the Windows **Start** menu, run the **Registry Editor** (*regedit.exe*).
 
-2. In the **Registry Editor** window for 64-bit computers, locate and delete the following registry entries:
+2. In the **Registry Editor** window, locate and delete the following registry entries if they exist:
 
     - **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\\.NETFramework\DbgManagedDebugger**
 
     - **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger**
 
     :::image type="content" source="../debugger/media/dbg-jit-registry.png" alt-text="JIT registry key" border="true":::
 
-3. If the following registry entries are present, or your computer is running a 32-bit operating system, delete the following entries:
+3. Also delete the following registry entries if they exist:
 
     - **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\\.NETFramework\DbgManagedDebugger**
 

docs/ide/csharp-developer-productivity.md

@@ -5,7 +5,7 @@ author: TerryGLee
 ms.author: tglee
 manager: jmartens
 ms.technology: vs-ide-general
-ms.date: 07/31/2022
+ms.date: 09/19/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - editor
@@ -60,7 +60,7 @@ The following are popular Visual Studio shortcuts:
 | **Ctrl**+**\\**,**Ctrl**+**E** (Default Profile) or **Ctrl**+**W**,**E** (C# Profile) | View Error List | See all errors in your document, project, or solution |
 | **Alt** + **PgUp/PgDn** | Go to Next/Previous Issue | Jump to the previous/next error, warning, suggestion in your document |
 | **Ctrl**+**K**,**/** | Toggle single line comment/uncomment | This command adds or removes a single line comment depending on whether your selection is already commented |
-| **Ctrl**+**Shift**+**/** | Toggle block comment/uncomment | This command adds or removes block comments depending on what you have selected |
+| **Ctrl**+**Shift**+**/** | Toggle block comment/uncomment | This command adds or removes block comments depending on what you've selected |
 
 > [!NOTE]
 > Some extensions unbind the default Visual Studio keybindings. You can restore your keybindings to their defaults by going to **Tools** > **Import and Export Settings** > **Reset all settings** or **Tools** > **Options** > **Keyboard** > **Reset**.
@@ -152,7 +152,7 @@ Check out the [.NET code-style rule options](/dotnet/fundamentals/code-analysis/
 
 ## Code Cleanup
 
-Visual Studio provides on-demand formatting of your code file, including code style preferences, through the **Code Cleanup** feature. To run Code Cleanup, click the broom icon at the bottom of the editor or press **Ctrl**+**K**, **Ctrl**+**E**.
+Visual Studio provides on-demand formatting of your code file, including code style preferences, through the **Code Cleanup** feature. To run Code Cleanup, select the broom icon at the bottom of the editor or press **Ctrl**+**K**, **Ctrl**+**E**.
 
 ::: moniker range="vs-2022"
 
@@ -166,7 +166,7 @@ Visual Studio provides on-demand formatting of your code file, including code st
 
 ::: moniker-end
 
-You can also run code cleanup across your entire project or solution. Right-click on the project or solution name in **Solution Explorer**, select **Analyze and Code Cleanup**, and then select **Run Code Cleanup**.
+You can also run code cleanup across your entire project or solution. Right-click the project or solution name in **Solution Explorer**, select **Analyze and Code Cleanup**, and then select **Run Code Cleanup**.
 
 ::: moniker range="vs-2022"
 
@@ -184,7 +184,7 @@ In addition to formatting your file for spaces, indents, et cetera, **Code Clean
 
 ## Refactorings and code fixes
 
-Visual Studio comes with numerous refactorings, code generation actions, and code fixes. Red squiggles represent errors, green squiggles represent warnings, and three gray dots represent code suggestions. You can access code fixes by clicking the light bulb or screwdriver icon, or by pressing **Ctrl**+**.** or **Alt**+**Enter**. Each fix comes with a preview window that shows a live code diff of how the fix works.
+Visual Studio comes with numerous refactorings, code generation actions, and code fixes. Red squiggles represent errors, green squiggles represent warnings, and three gray dots represent code suggestions. You can access code fixes by selecting the light bulb or screwdriver icon, or by pressing **Ctrl**+**.** or **Alt**+**Enter**. Each fix comes with a preview window that shows a live code diff of how the fix works.
 
 Popular quick fixes and refactorings include:
 
@@ -321,9 +321,10 @@ Here's a list of editor and productivity features to make writing code more effi
 | Add usings for types in reference assemblies and NuGet packages | Shows an error light bulb with a code fix to install a NuGet package for an unreferenced type | **Tools** > **Options** > **Text Editor** > **C#** > **Advanced** > **Suggest usings for types in reference assemblies** and **Suggest usings for types in NuGet packages** |
 | Enable full solution analysis | See all errors in your solution in the **Error List** | **Tools** > **Options** > **Text Editor** > **C#** > **Advanced** > **Enable full solution analysis** |
 | Enable navigation to decompiled sources | Allow Go To Definition on types/members from external sources and use the ILSpy decompiler to show method bodies | **Tools** > **Options** > **Text Editor** > **C#** > **Advanced** > **Enable navigation to decompiled sources** |
-| Completion/Suggestion Mode | Changes the completion behavior in [IntelliSense](using-intellisense.md). Developers with IntelliJ backgrounds tend to use a non-default setting here. | **Menu** > **Edit** > **IntelliSense** > **Toggle Completion Mode** |
+| Completion/Suggestion Mode | Changes the completion behavior in [IntelliSense](using-intellisense.md). Developers with IntelliJ backgrounds tend to use a non-default setting here. | **Edit** > **IntelliSense** > **Toggle Completion Mode** |
 | [CodeLens](../ide/find-code-changes-and-other-history-with-codelens.md) | Displays code reference information and change history in the editor. (Source control CodeLens indicators aren't available in Visual Studio Community edition.) | **Tools** > **Options** > **Text Editor** > **All Languages** > **CodeLens** |
 | [Code snippets](../ide/visual-csharp-code-snippets.md) | Help stub out common boilerplate code | Type a snippet name and press **Tab** twice. |
+| Paste JSON as classes | Copy any JSON fragment to the clipboard and paste it as strongly typed .NET classes into any C# code file. | **Edit** > **Paste Special** > **Paste JSON As Classes** |
 
 ## See also
 

docs/javascript/tutorial-asp-net-core-with-angular.md

@@ -70,7 +70,7 @@ Make sure to install the following:
 
    :::image type="content" source="media/vs-2022/asp-net-core-choose-web-api-template.png" alt-text="Choose the Web API template":::
 
-1. Give your project and solution a name. When you get to the **Additional information** window, select **.NET 6.0** as your target framework.
+1. Give your project a name. When you get to the **Additional information** window, select **.NET 6.0** as your target framework.
 
    Once the project is created, Solution Explorer should look like this:
 

pull_request_template.md

@@ -10,4 +10,6 @@ Before creating your pull request, please check your content against these quali
 - Should this page be linked to from other pages or Microsoft web sites?
 
 For more information about creating content for docs.microsoft.com, see the contributor guide at https://docs.microsoft.com/contribute/.
+
+When your PR is ready for review, add a comment with the text #sign-off to the Conversation tab.
 -->