Fix links etc

Author: ghogen

.openpublishing.redirection.json

@@ -5,35 +5,30 @@
       "redirect_url": "/visualstudio/ide/command-window",
       "redirect_document_id": true
     },
-        {
+    {
       "source_path": "docs/ide/reference/error-list-window.md",
       "redirect_url": "/visualstudio/ide/error-list-window",
       "redirect_document_id": true
     },
-        {
+    {
       "source_path": "docs/ide/reference/output-window.md",
       "redirect_url": "/visualstudio/ide/output-window",
       "redirect_document_id": true
     },
-        {
+    {
       "source_path": "docs/ide/reference/user-notifications-window.md",
       "redirect_url": "/visualstudio/ide/user-notifications-window",
       "redirect_document_id": true
     },
-        {
+    {
       "source_path": "docs/ide/reference/trust-settings.md",
       "redirect_url": "/visualstudio/ide/trust-settings",
       "redirect_document_id": true
     },
-        {
+    {
       "source_path": "docs/ide/reference/team-explorer-reference.md",
       "redirect_url": "/visualstudio/ide/team-explorer-reference",
       "redirect_document_id": true
-    },
-        {
-      "source_path": "docs/ide/reference/command-window.md",
-      "redirect_url": "/visualstudio/ide/command-window",
-      "redirect_document_id": true
     },
     {
       "source_path": "docs/ide/reference/options-text-editor-all-languages-tabs.md",

docs/ide/command-window.md

@@ -106,5 +106,5 @@ If, for example, you want to open a file that has a path containing spaces, you
 
 ## See also
 
-- [Visual Studio Command Aliases](../../ide/reference/visual-studio-command-aliases.md)
-- [Visual Studio Commands](../../ide/reference/visual-studio-commands.md)
+- [Visual Studio Command Aliases](reference/visual-studio-command-aliases.md)
+- [Visual Studio Commands](reference/visual-studio-commands.md)

docs/ide/output-window.md

@@ -56,9 +56,9 @@ The **Output** pane selected in the **Show output from** list displays output fr
 
 To display the **Output** window whenever you build a project, in the **Options** dialog box, on the **Projects and Solutions** > **General** page, select **Show Output window when build starts**. Then, with a code file open for editing, choose **Go to Next Message** and **Go To Previous Message** on the **Output** window toolbar to select entries in the **Output** pane. As you do this, the insertion point in the code editor jumps to the line of code where the selected problem occurs.
 
-Certain IDE features and commands invoked in the [Command window](../../ide/reference/command-window.md) deliver their output to the **Output** window. Output from external tools such as *.bat* and *.com* files, which is typically displayed in the command window, is routed to an **Output** pane when you select the **Use Output Window** option in [Manage external tools](../../ide/managing-external-tools.md). Many other kinds of messages can be displayed in **Output** panes as well. For example, when Transact-SQL syntax in a stored procedure is checked against a target database, the results are displayed in the **Output** window.
+Certain IDE features and commands invoked in the [Command window](command-window.md) deliver their output to the **Output** window. Output from external tools such as *.bat* and *.com* files, which is typically displayed in the command window, is routed to an **Output** pane when you select the **Use Output Window** option in [Manage external tools](managing-external-tools.md). Many other kinds of messages can be displayed in **Output** panes as well. For example, when Transact-SQL syntax in a stored procedure is checked against a target database, the results are displayed in the **Output** window.
 
-You can also program your own applications to write diagnostic messages at run time to an **Output** pane. To do this, use members of the <xref:System.Diagnostics.Debug> class or <xref:System.Diagnostics.Trace> class in the <xref:System.Diagnostics> namespace of the .NET API. Members of the <xref:System.Diagnostics.Debug> class display output when you build Debug configurations of your solution or project; members of the <xref:System.Diagnostics.Trace> class display output when you build either Debug or Release configurations. For more information, see [Diagnostic messages in the Output window](../../debugger/diagnostic-messages-in-the-output-window.md).
+You can also program your own applications to write diagnostic messages at run time to an **Output** pane. To do this, use members of the <xref:System.Diagnostics.Debug> class or <xref:System.Diagnostics.Trace> class in the <xref:System.Diagnostics> namespace of the .NET API. Members of the <xref:System.Diagnostics.Debug> class display output when you build Debug configurations of your solution or project; members of the <xref:System.Diagnostics.Trace> class display output when you build either Debug or Release configurations. For more information, see [Diagnostic messages in the Output window](../debugger/diagnostic-messages-in-the-output-window.md).
 
 In C++, you can create custom build steps and build events whose warnings and errors are displayed and counted in the **Output** pane. By pressing **F1** on a line of output, you can display an appropriate help topic. For more information, see [Format the output of a custom build step](/cpp/build/formatting-the-output-of-a-custom-build-step-or-build-event).
 
@@ -68,12 +68,12 @@ If you use autoscrolling in the **Output** window and then navigate by using the
 
 ## Structured Diagnostics
 
-C++ MSBuild projects might emit structured diagnostics. The level of indentation of a diagnostic in the **Output** window represents the nested structure of the information. Enable or disable indentation with the **Project** > **Properties** > **Advanced** > **Enable MSVC Structured Output** option. You can affect several projects by creating a [Directory.Build.props](/visualstudio/msbuild/customize-by-directory) file with the **UseStructuredOutput** property defined to true or false.
+C++ MSBuild projects might emit structured diagnostics. The level of indentation of a diagnostic in the **Output** window represents the nested structure of the information. Enable or disable indentation with the **Project** > **Properties** > **Advanced** > **Enable MSVC Structured Output** option. You can affect several projects by creating a [Directory.Build.props](../msbuild/customize-by-directory) file with the **UseStructuredOutput** property defined to true or false.
 
 ## See also
 
-- [Diagnostic messages in the Output window](../../debugger/diagnostic-messages-in-the-output-window.md)
+- [Diagnostic messages in the Output window](../debugger/diagnostic-messages-in-the-output-window.md)
 - [How to: Control the Output window](/previous-versions/ht6z4e28(v=vs.140))
-- [Compile and build](../../ide/compiling-and-building-in-visual-studio.md)
-- [Understand build configurations](../../ide/understanding-build-configurations.md)
+- [Compile and build](compiling-and-building-in-visual-studio.md)
+- [Understand build configurations](understanding-build-configurations.md)
 - [Class library overview](/dotnet/standard/class-library-overview)

docs/ide/team-explorer-reference.md

@@ -16,11 +16,11 @@ This article provides links to Azure DevOps articles about the various functions
 Use the **Team Explorer** tool window to coordinate your code efforts with other team members to develop a project, and to manage work that's assigned to you, your team, or your projects. **Team Explorer** connects Visual Studio to Git and GitHub repositories, Team Foundation version control (TFVC) repositories, and projects hosted on [Azure DevOps Services](/azure/devops/user-guide/what-is-azure-devops-services) or an on-premises [Azure DevOps Server](/azure/devops/index-all) (formerly known as Team Foundation Server, or TFS). You can manage source code, work items, and builds.
 
 > [!IMPORTANT]
-> Starting with the release of Visual Studio 2019 [**version 16.8**](/visualstudio/releases/2019/release-notes-history), the Git version control experience is the default. If you'd like to learn more about how it compares with Team Explorer, see the [**Side-by-side comparison of Git and Team Explorer**](../../version-control/git-team-explorer-feature-comparison.md) page.
+> Starting with the release of Visual Studio 2019 [**version 16.8**](/visualstudio/releases/2019/release-notes-history), the Git version control experience is the default. If you'd like to learn more about how it compares with Team Explorer, see the [**Side-by-side comparison of Git and Team Explorer**](../version-control/git-team-explorer-feature-comparison.md) page.
 
 ## Home page
 
-After you [connect to a project](../connect-team-project.md) in **Team Explorer**, the following links become available in the **Project** section:
+After you [connect to a project](connect-team-project.md) in **Team Explorer**, the following links become available in the **Project** section:
 
 - [Clone repository](/azure/devops/repos/git/clone)
 - [Web Portal](/azure/devops/project/navigation/index)
@@ -109,4 +109,4 @@ The **Settings** page lets you configure administrative features for either a pr
 
 ## See also
 
-- [Connect to projects in Team Explorer](../../ide/connect-team-project.md)
+- [Connect to projects in Team Explorer](connect-team-project.md)

docs/ide/trust-settings.md

@@ -167,4 +167,4 @@ To remove trusted paths, follow these steps:
 
 ## See also
 
-[Build an application in Visual Studio](../walkthrough-building-an-application.md)
+[Build an application in Visual Studio](walkthrough-building-an-application.md)