Merge pull request #21119 from docker/published-update

publish updates from main

Author: aevesdocker

content/manuals/desktop/troubleshoot/_index.md

@@ -21,9 +21,12 @@ weight: 160
 
 This page contains information on how to diagnose and troubleshoot Docker Desktop, and how to check the logs.
 
-## Troubleshooting menu
+## Troubleshoot menu
 
-Select the **Question mark** icon near the top-right corner of Docker Dashboard, then **Troubleshooting**.
+To navigate to **Troubleshoot** either:
+
+- Select the Docker menu Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Troubleshoot**.
+- Select the **Troubleshoot** icon near the top-right corner of Docker Dashboard.
 
 The **Troubleshooting** menu contains the following options:
 
@@ -39,8 +42,6 @@ Docker Desktop to their initial state, the same as when Docker Desktop was first
 
 If you are a Mac or Linux user, you also have the option to **Uninstall** Docker Desktop from your system.
 
-You can also access these troubleshoot options from the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}}.
-
 > [!TIP]
 >
 > If you need to contact support, select the **Question mark** icon near the top-right corner of Docker Dashboard, and then select **Contact support**. Users with a paid Docker subscription can use this option to send a support request.
@@ -57,22 +58,22 @@ You can also access these troubleshoot options from the Docker menu {{< inline-i
 
 ### Diagnose from the app
 
-1. Select the **Question mark** icon near the top-right corner of Docker Dashboard, then **Report a bug**
-This opens a new in-app page and starts collecting the diagnostics.
-2. When the diagnostics collection process is complete 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** from the **Troubleshooting** menu. This opens the Docker Desktop support form. Fill in the information required. Your diagnostics ID is gathered automatically. Then, select **Submit ticket** to request Docker Desktop support.
+1. From **Troubleshoot**, select **Get support**. This opens the in-app Support page and starts collecting the diagnostics.
+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](../../support/_index.md).
-    - If you don't have a paid Docker subscription, follow the GitHub repository link to open a new Docker Desktop issue on GitHub. Complete the information required on the GitHub issue and ensure you add the diagnostic ID printed in step two. 
+    - 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 
 
 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:
-    - Select **Contact support** from the **Troubleshooting** menu. This opens the Docker Desktop support form. Fill in the information required. Your diagnostics ID is gathered automatically. Then, select **Submit ticket** to request Docker Desktop support.
+    - 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](../../support/_index.md).
@@ -177,7 +178,7 @@ $ unzip –l /tmp/<your-diagnostics-ID>.zip
 
 #### Use your diagnostics ID to get help
 
-Select **Contact support** from the **Troubleshooting** menu. This opens the Docker Desktop support form. Fill in the information required. Your diagnostics ID is gathered automatically. Then, select **Submit ticket** to request Docker Desktop support.
+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:
 

content/manuals/harmonia/_index.md

@@ -49,13 +49,21 @@ To verify creation, check the context switcher in the top-left corner of the Doc
 Run the following command: 
 
 ```console
-$ docker harmonia engine create cloudengine --arch "amd64"  --use
+$ docker harmonia engine create cloudengine --type "standard-amd64"  --use
 ```
 
 This creates an engine called `cloudengine` and:
 - Immediately switches you to the new cloud engine with the `--use` flag.
-- Sets the engine's CPU architecture to amd64 using the `--arch "amd64"` flag. You can choose between amd64 and arm64.
-- Configures the engine size with the `--size "standard"` flag. Options are standard (2 CPU cores, 4GB RAM, default) or large (4 CPU cores, 8GB RAM).
+- Sets the engine size to standard and the engine's CPU architecture to amd64 with the `--type` flag. 
+
+Project Harmonia supports the following values for `--type`:
+- `standard-arm64`
+- `standard-amd64` (default)
+- `large-arm64`
+- `large-amd64`
+- `aiml-amd64`
+
+Standard size engines have 2 CPU cores and 4GB RAM, large and AI/ML engines have 4 CPU cores and 8GB RAM.
 
 To verify you're using the newly created cloud engine, run: