support: single page (#23657)

## Description
- Moves support information to dedicated page
https://deploy-preview-23657--docsdocker.netlify.app/support/

Author: sarahsanders-docker

content/manuals/desktop/setup/vm-vdi.md

@@ -4,8 +4,8 @@ keywords: nested virtualization, Docker Desktop, windows, VM, VDI environment
 title: Run Docker Desktop for Windows in a VM or VDI environment
 linkTitle: VM or VDI environments
 aliases:
- - /desktop/nested-virtualization/
- - /desktop/vm-vdi/
+  - /desktop/nested-virtualization/
+  - /desktop/vm-vdi/
 weight: 30
 ---
 
@@ -44,11 +44,11 @@ quickstart](/offload/quickstart/).
 >
 > Support for running Docker Desktop on a virtual desktop is available to Docker Business customers, on VMware ESXi or Azure VMs only.
 
-Docker support includes installing and running Docker Desktop within the VM, provided that nested virtualization is correctly enabled. The only hypervisors successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](/manuals/desktop/troubleshoot-and-support/support.md).
+Docker support includes installing and running Docker Desktop within the VM, provided that nested virtualization is correctly enabled. The only hypervisors successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](/manuals/support/_index.md).
 
 For troubleshooting problems and intermittent failures that are outside of Docker's control, you should contact your hypervisor vendor. Each hypervisor vendor offers different levels of support. For example, Microsoft supports running nested Hyper-V both on-prem and on Azure, with some version constraints. This may not be the case for VMware ESXi.
 
-Docker does not support running multiple instances of Docker Desktop on the same machine in a VM or VDI environment. 
+Docker does not support running multiple instances of Docker Desktop on the same machine in a VM or VDI environment.
 
 > [!TIP]
 >
@@ -83,14 +83,14 @@ If using Windows container mode, confirm that the Nutanix environment supports H
 
 Docker Desktop follows the VDI support definitions outlined [previously](#virtual-desktop-support-when-using-nested-virtualization):
 
- - Persistent VDI environments (Supported): You receive the same virtual desktop instance across sessions, preserving installed software and configurations.
+- Persistent VDI environments (Supported): You receive the same virtual desktop instance across sessions, preserving installed software and configurations.
 
- - Non-persistent VDI environments (Not supported): Docker Desktop does not support environments where the OS resets between sessions, requiring re-installation or reconfiguration each time. 
+- Non-persistent VDI environments (Not supported): Docker Desktop does not support environments where the OS resets between sessions, requiring re-installation or reconfiguration each time.
 
 ### Support scope and responsibilities
 
 For WSL 2-related issues, contact Nutanix support. For Docker Desktop-specific issues, contact Docker support.
 
 ## Additional resources
 
-- [Docker Desktop on Microsoft Dev Box](/manuals/enterprise/enterprise-deployment/dev-box.md)
+- [Docker Desktop on Microsoft Dev Box](/manuals/enterprise/enterprise-deployment/dev-box.md)

content/manuals/desktop/troubleshoot-and-support/support.md

@@ -1,22 +1,23 @@
 ---
-description: Understand how to diagnose and troubleshoot Docker Desktop, and how to
+description:
+  Understand how to diagnose and troubleshoot Docker Desktop, and how to
   check the logs.
 keywords: Linux, Mac, Windows, troubleshooting, logs, issues, Docker Desktop
 toc_max: 2
 title: Troubleshoot Docker Desktop
 linkTitle: Troubleshoot and diagnose
 aliases:
- - /desktop/linux/troubleshoot/
- - /desktop/mac/troubleshoot/
- - /desktop/windows/troubleshoot/
- - /docker-for-mac/troubleshoot/
- - /mackit/troubleshoot/
- - /windows/troubleshoot/
- - /docker-for-win/troubleshoot/
- - /docker-for-windows/troubleshoot/
- - /desktop/troubleshoot/overview/
- - /desktop/troubleshoot/
-tags: [ Troubleshooting ]
+  - /desktop/linux/troubleshoot/
+  - /desktop/mac/troubleshoot/
+  - /desktop/windows/troubleshoot/
+  - /docker-for-mac/troubleshoot/
+  - /mackit/troubleshoot/
+  - /windows/troubleshoot/
+  - /docker-for-win/troubleshoot/
+  - /docker-for-windows/troubleshoot/
+  - /desktop/troubleshoot/overview/
+  - /desktop/troubleshoot/
+tags: [Troubleshooting]
 weight: 10
 ---
 
@@ -36,15 +37,15 @@ The **Troubleshooting** menu contains the following options:
 - **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](/manuals/desktop/settings-and-maintenance/settings.md#kubernetes).
 
 - **Clean / Purge data**. This option resets all Docker data without a
-reset to factory defaults. Selecting this option results in the loss of existing settings.
+  reset to factory defaults. Selecting this option results in the loss of existing settings.
 
 - **Reset to factory defaults**: Choose this option to reset all options on
-Docker Desktop to their initial state, the same as when Docker Desktop was first installed.
+  Docker Desktop to their initial state, the same as when Docker Desktop was first installed.
 
 If you are a Mac or Linux user, you also have the option to **Uninstall** Docker Desktop from your system.
 
 ## Diagnose
- 
+
 > [!TIP]
 >
 > If you do not find a solution in troubleshooting, browse the GitHub repositories or create a new issue:
@@ -59,22 +60,22 @@ If you are a Mac or Linux user, you also have the option to **Uninstall** Docker
 2. When the diagnostics collection process is complete, select **Upload to get a Diagnostic ID**.
 3. When the diagnostics are uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.
 4. Use your diagnostics ID to get help:
-    - If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
-        > [!NOTE]
-        >
-        > You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/desktop/troubleshoot-and-support/support.md).
-    - If you don't have a paid Docker subscription, select **Report a Bug** to open a new Docker Desktop issue on GitHub. Complete the information required and ensure you add the diagnostic ID you copied in step three.
+   - If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
+     > [!NOTE]
+     >
+     > You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/support/_index.md).
+   - If you don't have a paid Docker subscription, select **Report a Bug** to open a new Docker Desktop issue on GitHub. Complete the information required and ensure you add the diagnostic ID you copied in step three.
 
-### Diagnose from an error message 
+### Diagnose from an error message
 
 1. When an error message appears, select **Gather diagnostics**.
 2. When the diagnostics are uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.
 3. Use your diagnostics ID to get help:
-    - If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
-        > [!NOTE]
-        >
-        > You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/desktop/troubleshoot-and-support/support.md).
-    - If you don't have a paid Docker subscription, you can open a new Docker Desktop issue on GitHub for [Mac](https://github.com/docker/for-mac/issues), [Windows](https://github.com/docker/for-win/issues), or [Linux](https://github.com/docker/for-linux/issues). Complete the information required and ensure you add the diagnostic ID printed in step two. 
+   - If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
+     > [!NOTE]
+     >
+     > You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](/manuals/support/_index.md).
+   - If you don't have a paid Docker subscription, you can open a new Docker Desktop issue on GitHub for [Mac](https://github.com/docker/for-mac/issues), [Windows](https://github.com/docker/for-win/issues), or [Linux](https://github.com/docker/for-linux/issues). Complete the information required and ensure you add the diagnostic ID printed in step two.
 
 ### Diagnose from the terminal
 
@@ -96,7 +97,7 @@ Docker Desktop cannot start.
    $ & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
    ```
 
-After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`. 
+After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
 
 {{< /tab >}}
 {{< tab name="Mac" >}}
@@ -113,7 +114,7 @@ After the diagnostics have finished, the terminal displays your diagnostics ID a
    $ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload
    ```
 
-After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`. 
+After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
 
 {{< /tab >}}
 {{< tab name="Linux" >}}
@@ -130,7 +131,7 @@ After the diagnostics have finished, the terminal displays your diagnostics ID a
    $ /opt/docker-desktop/bin/com.docker.diagnose gather -upload
    ```
 
-After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`. 
+After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`.
 
 {{< /tab >}}
 {{< /tabs >}}
@@ -144,7 +145,7 @@ To view the contents of the diagnostic file:
 
    ```powershell
    $ Expand-Archive -LiteralPath "C:\Users\testUser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602.zip" -DestinationPath "C:\Users\testuser\AppData\Local\Temp\5DE9978A-3848-429E-8776-950FC869186F\20230607101602"
-   ```  
+   ```
 
 2. Open the file in your preferred text editor. Run:
 
@@ -176,7 +177,7 @@ $ unzip –l /tmp/<your-diagnostics-ID>.zip
 #### Use your diagnostics ID to get help
 
 If you have a paid Docker subscription, select **Contact support**. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID field**. Then, select **Submit ticket** to request Docker Desktop support.
-    
+
 If you don't have a paid Docker subscription, create an issue on GitHub:
 
 - [For Linux](https://github.com/docker/desktop-linux/issues)
@@ -262,3 +263,4 @@ to learn how to view the Docker Daemon logs.
 - View specific [troubleshoot topics](topics.md).
 - View information on [known issues](known-issues.md)
 - [Fix "Docker.app is damaged" on macOS](mac-damaged-dialog.md) - Resolve macOS installation issues
+- [Get support for Docker products](/manuals/support/_index.md)

content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

@@ -28,6 +28,7 @@ Follow these steps to resolve the issue:
 ### Step one: Quit third-party software
 
 Close any applications that might call Docker in the background:
+
 - Visual Studio Code and other IDEs
 - Terminal applications
 - Agent apps or development tools
@@ -47,10 +48,11 @@ Follow the instructions in the [macOS installation guide](/manuals/desktop/setup
 If you continue to see the "damaged" dialog after following the recovery steps:
 
 1. Gather diagnostics using the terminal. Follow the instructions in [Diagnose from the terminal](/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md#diagnose-from-the-terminal).
+
    - Note down the your diagnostics ID displayed in the terminal after running diagnostics.
 
 2. Get help:
-   - If you have a paid Docker subscription, [contact support](/manuals/desktop/troubleshoot-and-support/support.md) and include your diagnostics ID
+   - If you have a paid Docker subscription, [contact support](/manuals/support/_index.md) and include your diagnostics ID
    - For community users, [open an issue on GitHub](https://github.com/docker/for-mac/issues) and include your diagnostics ID
 
 ## Prevention