Update UI reference articles

Author: Mikejo5000

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/ide/reference/immediate-window.md",
+      "redirect_url": "/visualstudio/ide/immediate-window",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/ide/reference/miscellaneous-files.md",
       "redirect_url": "/visualstudio/ide/miscellaneous-files",

docs/debugger/debugger-windows.md

@@ -22,7 +22,7 @@ You can open most debugger windows while you're debugging your program. To see a
 |Autos|CTRL+ALT+V, A|[Autos and Locals Windows](../debugger/autos-and-locals-windows.md)|
 |Locals|CTRL+ALT+V, L|[Autos and Locals Windows](../debugger/autos-and-locals-windows.md)|
 |Call Stacks|CTRL+ALT+C|[How to: Use the Call Stack Window](../debugger/how-to-use-the-call-stack-window.md)|
-|Immediate|CTRL+ALT+I|[Immediate Window](../ide/reference/immediate-window.md)|
+|Immediate|CTRL+ALT+I|[Immediate Window](../ide/immediate-window.md)|
 |Parallel Stacks|CTR:+SHIFT+D, S|[Using the Parallel Stacks Window](../debugger/using-the-parallel-stacks-window.md)|
 |Parallel Watch|CTR:+SHIFT+D, (1, 2, 3, 4)|[Get started Debugging Multithreaded Applications](../debugger/get-started-debugging-multithreaded-apps.md)|
 |Threads|CTRL+ALT+H|[View threads in the Visual Studio debugger](../debugger/walkthrough-debugging-a-multithreaded-application.md)|

docs/debugger/toc.yml

@@ -362,8 +362,8 @@
       href: /visualstudio/bridge/bridge-to-kubernetes-vs
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md
-  - name: Immediate window
-    href: ../ide/reference/immediate-window.md
+  - name: Use the Immediate window
+    href: ../ide/immediate-window.md
   - name: Work with...
     items:
     - name: .NET

docs/debugger/walkthrough-debugging-at-design-time.md

@@ -23,7 +23,7 @@ To debug XAML code behind an app from the XAML designer, such as declarative dat
 
 ## Use the Immediate window
 
-You can use the Visual Studio **Immediate** window to execute a function or subroutine without running your app. If the function or subroutine contains a breakpoint, Visual Studio will break at the breakpoint. You can then use the debugger windows to examine your program state. This feature is called *debugging at design time*. For detailed information, see [Use the Immediate window](../ide/reference/immediate-window.md)
+You can use the Visual Studio **Immediate** window to execute a function or subroutine without running your app. If the function or subroutine contains a breakpoint, Visual Studio will break at the breakpoint. You can then use the debugger windows to examine your program state. This feature is called *debugging at design time*. For detailed information, see [Use the Immediate window](../ide/immediate-window.md)
 
 The following example is in Visual Basic. You can also use the **Immediate** window at design time in C#, F#, and C++/CLI apps. For C++/CLI, compile without the /clr option to use the Immediate window.
 

docs/ide/productivity-features.md

@@ -158,7 +158,7 @@ Debugging can take time, but the following tips can help you speed up the proces
 
      To add a DataTip, the debugger must be in break mode. Place the cursor on the variable, and then choose the pin button on the DataTip that appears. When debugging is stopped, a blue pin icon appears in the source file next to the line of code that contains the variable. If you point to the blue pin, the value of the variable from the most recent debugging session appears.
 
-- **Clear the Immediate window**. You can erase the contents of the [Immediate window](../ide/reference/immediate-window.md) at design time by entering `>cls` or `>Edit.ClearAll`
+- **Clear the Immediate window**. You can erase the contents of the [Immediate window](../ide/immediate-window.md) at design time by entering `>cls` or `>Edit.ClearAll`
 
      For more information about other commands, see [Visual Studio command aliases](../ide/reference/visual-studio-command-aliases.md).
 

docs/ide/reference/new-file-command.md

@@ -64,6 +64,6 @@ This example creates a new web page "test1.htm" and opens it in the source code
 
 - [Visual Studio Commands](../../ide/reference/visual-studio-commands.md)
 - [Command Window](../../ide/reference/command-window.md)
-- [Immediate Window](../../ide/reference/immediate-window.md)
+- [Immediate Window](../../ide/immediate-window.md)
 - [Find/Command Box](../../ide/find-command-box.md)
 - [Visual Studio Command Aliases](../../ide/reference/visual-studio-command-aliases.md)

docs/ide/reference/open-file-command.md

@@ -60,6 +60,6 @@ File.OpenFile "C:\My Projects\project1\Test1.css" /e:"Source Code (text) Editor"
 
 - [Visual Studio commands](../../ide/reference/visual-studio-commands.md)
 - [Command window](../../ide/reference/command-window.md)
-- [Immediate window](../../ide/reference/immediate-window.md)
+- [Immediate window](../../ide/immediate-window.md)
 - [Find/Command box](../../ide/find-command-box.md)
 - [Visual Studio command aliases](../../ide/reference/visual-studio-command-aliases.md)

docs/ide/reference/visual-studio-commands.md

@@ -14,7 +14,7 @@ ms.subservice: general-ide
 ---
 # Visual Studio commands
 
-You can enter Visual Studio commands in the [**Command** window](../../ide/reference/command-window.md), [**Immediate** window](../../ide/reference/immediate-window.md), or **Find/Command** box. In each case, the greater than sign (`>`) indicates that a command, rather than a search or debug operation, follows.
+You can enter Visual Studio commands in the [**Command** window](../../ide/reference/command-window.md), [**Immediate** window](../../ide/immediate-window.md), or **Find/Command** box. In each case, the greater than sign (`>`) indicates that a command, rather than a search or debug operation, follows.
 
 You can find a complete list of commands and their syntax on the **Keyboard** page in **Tools** > **Options** > **Environment**.
 

docs/ide/visual-csharp-intellisense.md

@@ -13,7 +13,7 @@ ms.date: 03/28/2024
 ---
 # C# IntelliSense
 
-C# IntelliSense is a language-specific code-completion aid. It's available to you when you write C# code in the code editor and debug it in the [Immediate mode](../ide/reference/immediate-window.md) command window.
+C# IntelliSense is a language-specific code-completion aid. It's available to you when you write C# code in the code editor and debug it in the [Immediate mode](../ide/immediate-window.md) command window.
 
 ## Completion lists
 

docs/ide/whats-new-visual-studio-docs.md

@@ -366,7 +366,7 @@ The following people contributed to the Visual Studio docs during this period. T
 - [Visual Studio performance tips and tricks](../ide/visual-studio-performance-tips-and-tricks.md) - Update Visual Studio performance tips
 - [What's new in Visual Studio 2022](../ide/whats-new-visual-studio-2022.md) - Update What's New for 17.14
 - [Add or remove imported namespaces (Visual Basic)](../ide/how-to-add-or-remove-imported-namespaces-visual-basic.md) - Update procedure for Visual Basic Import namespaces
-- [Use the Immediate window](../ide/reference/immediate-window.md) - Update article on the Immediate window
+- [Use the Immediate window](../ide/immediate-window.md) - Update article on the Immediate window
 - [JavaScript IntelliSense](../ide/javascript-intellisense.md) - Refactor JavaScript/TypeScript editor content
 - [Add Visual Studio editor support for other languages](../ide/adding-visual-studio-editor-support-for-other-languages.md) - Updates for user feedback
 - [Customize the scroll bar](../ide/how-to-track-your-code-by-customizing-the-scrollbar.md) - Updates for user feedback on track changes