Fix typo

VSCode -> VS Code

Author: changeworld

reference/docs-conceptual/community/contributing/product-terminology.md

@@ -111,7 +111,7 @@ Guidelines
 
 - First mention - use the full name
 - Subsequent mentions - you can use "VS Code"
-- Never use "VSCode"
+- Never use "VS Code"
 
 ### PowerShell Extension for Visual Studio Code
 

reference/docs-conceptual/dev-cross-plat/vscode/Using-VSCode-for-Remote-Editing-and-Debugging.md

@@ -8,7 +8,7 @@ title: Using Visual Studio Code for remote editing and debugging
 For those of you that are familiar with the ISE, you may recall that you could run `psedit file.ps1`
 from the integrated console to open files - local or remote - right in the ISE.
 
-This feature is also available in the PowerShell extension for VSCode. This guide shows you how to
+This feature is also available in the PowerShell extension for VS Code. This guide shows you how to
 do it.
 
 ## Prerequisites
@@ -17,7 +17,7 @@ This guide assumes that you have:
 
 - A remote resource (ex: a VM, a container) that you have access to
 - PowerShell running on it and the host machine
-- VSCode and the PowerShell extension for VSCode
+- VS Code and the PowerShell extension for VS Code
 
 This feature works on PowerShell and Windows PowerShell.
 
@@ -26,7 +26,7 @@ you want to use SSH, but are using Windows, check out the [Win32 version of SSH]
 
 > [!IMPORTANT]
 > The `Open-EditorFile` and `psedit` commands only work in the **PowerShell Integrated Console**
-> created by the PowerShell extension for VSCode.
+> created by the PowerShell extension for VS Code.
 
 ## Usage examples
 
@@ -35,7 +35,7 @@ Azure. The process is identical on Windows.
 
 ### Local file editing with Open-EditorFile
 
-With the PowerShell extension for VSCode started and the PowerShell Integrated Console opened, we
+With the PowerShell extension for VS Code started and the PowerShell Integrated Console opened, we
 can type `Open-EditorFile foo.ps1` or `psedit foo.ps1` to open the local foo.ps1 file right in the
 editor.
 

reference/docs-conceptual/learn/deep-dives/everything-about-null.md

@@ -189,7 +189,7 @@ Not only can we create a value that makes both of them evaluate to `$false`, it'
 create a value where they both evaluate to `$true`. Mathias Jessen (@IISResetMe) has a
 [good post][good post] that dives into that scenario.
 
-### PSScriptAnalyzer and VSCode
+### PSScriptAnalyzer and VS Code
 
 The [PSScriptAnalyzer][PSScriptAnalyzer] module has a rule that checks for this issue called
 `PSPossibleIncorrectComparisonWithNull`.

reference/docs-conceptual/whats-new/Migrating-from-Windows-PowerShell-51-to-PowerShell-7.md

@@ -286,7 +286,7 @@ For more information, see [about_Logging_Windows][14].
 
 ## Improved editing experience with Visual Studio Code
 
-[Visual Studio Code (VSCode)][22] with the [PowerShell Extension][23] is the supported scripting
+[Visual Studio Code (VS Code)][22] with the [PowerShell Extension][23] is the supported scripting
 environment for PowerShell 7. The Windows PowerShell Integrated Scripting Environment (ISE) only
 supports Windows PowerShell.
 
@@ -300,7 +300,7 @@ The updated PowerShell extension includes:
 - Improved path autocompletion
 
 To make the transition to Visual Studio Code easier, use the **Enable ISE Mode** function available
-in the **Command Palette**. This function switches VSCode into an ISE-style layout. The ISE-style
+in the **Command Palette**. This function switches VS Code into an ISE-style layout. The ISE-style
 layout gives you all the new features and capabilities of PowerShell in a familiar user experience.
 
 To switch to the new ISE layout, press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> to open the
@@ -309,7 +309,7 @@ To switch to the new ISE layout, press <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</
 To set the layout to the original layout, open the **Command Palette**, select
 **PowerShell: Disable ISE Mode (restore to defaults)**.
 
-For details about customizing the VSCode layout to ISE, see
+For details about customizing the VS Code layout to ISE, see
 [How to Replicate the ISE Experience in Visual Studio Code][01]
 
 > [!NOTE]

reference/index.yml

@@ -106,7 +106,7 @@ productDirectory:
         - url: https://code.visualstudio.com/docs/languages/powershell
           text: Visual Studio Code PowerShell Extension
         - url: /powershell/scripting/components/vscode/using-vscode-for-remote-editing-and-debugging
-          text: Using VSCode for remote editing and debugging
+          text: Using VS Code for remote editing and debugging
         - url: /powershell/scripting/developer/windows-powershell
           text: Windows PowerShell SDK documentation
         - url: /dotnet/api/?view=powershellsdk-7.4.0