more edits

Author: aevesdocker

_vale/Docker/Acronyms.yml

@@ -50,6 +50,7 @@ exceptions:
   - GDB
   - GET
   - GHSA
+  - GNOME
   - GNU
   - GPG
   - GPL
@@ -74,10 +75,12 @@ exceptions:
   - JIT
   - JSON
   - JSX
+  - KDE
   - LESS
   - LLDB
   - LTS
   - MAC
+  - MATE
   - MCP
   - mcp
   - MDM

content/manuals/desktop/_index.md

@@ -80,10 +80,4 @@ Docker Desktop integrates with your preferred development tools and languages, a
 {{< /tab >}}
 {{< /tabs >}}
 
-Docker Desktop works with your choice of development tools and languages and
-gives you access to a vast library of certified images and templates in
-[Docker Hub](https://hub.docker.com/). This allows development teams to extend
-their environment to rapidly auto-build, continuously integrate, and collaborate
-using a secure repository.
-
 {{< grid >}}

content/manuals/desktop/setup/install/enterprise-deployment/pkg-install-and-configure.md

@@ -26,7 +26,7 @@ The PKG package supports various MDM (Mobile Device Management) solutions, makin
 
 > [!NOTE]
 >
-> When installing Docker Desktop with the PKG, in-app updates are automatically disabled.  This ensures organizations can maintain version consistency and prevent unapproved updates. For Docker Desktop installed with the `.dmg` installer, in-app updates remain supported.
+> When installing Docker Desktop with the PKG, in-app updates are automatically disabled. This ensures organizations can maintain version consistency and prevent unapproved updates. For Docker Desktop installed with the `.dmg` installer, in-app updates remain supported.
 >
 > Docker Desktop notifies you when an update is available. To update Docker Desktop, download the latest installer from the Docker Admin Console. Navigate to the  **Deploy** page > under **Docker Desktop**.
 >

content/manuals/desktop/setup/install/linux/_index.md

@@ -137,7 +137,7 @@ To install Docker Desktop successfully, your Linux host must meet the following
 - KVM virtualization support. Follow the [KVM virtualization support instructions](#kvm-virtualization-support) to check if the KVM kernel modules are enabled and how to provide access to the KVM device.
 - QEMU must be version 5.2 or later. We recommend upgrading to the latest version.
 - systemd init system.
-- GNOW, KDE, or MATE desktop environment.
+- GNOME, KDE, or MATE desktop environment.
   - For many Linux distributions, the GNOME environment does not support tray icons. To add support for tray icons, you need to install a GNOME extension. For example, [AppIndicator](https://extensions.gnome.org/extension/615/appindicator-support/).
 - At least 4 GB of RAM.
 - Enable configuring ID mapping in user namespaces, see [File sharing](/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md#how-do-i-enable-file-sharing). Note that for Docker Desktop version 4.35 and later, this is not required anymore.

content/manuals/desktop/setup/install/linux/rhel.md

@@ -6,11 +6,6 @@ keywords: red hat, red hat enterprise linux, rhel, rpm,
 title: Install Docker Desktop on RHEL
 linkTitle: RHEL
 download-url-base: https://download.docker.com/linux/rhel
-params:
-  sidebar:
-    badge:
-      color: green
-      text: New
 aliases:
 - /desktop/install/linux/rhel/
 ---

content/manuals/desktop/setup/sign-in.md

@@ -30,7 +30,7 @@ aliases:
 - /desktop/get-started/
 ---
 
-Docker recommends that you authenticate using the **Sign in** option in the top-right corner of the Docker Dashboard. 
+Docker recommends signing in with the **Sign in** option in the top-right corner of the Docker Dashboard. 
 
 In large enterprises where admin access is restricted, administrators can [enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md). 
 
@@ -40,61 +40,53 @@ In large enterprises where admin access is restricted, administrators can [enfor
 
 ## Benefits of signing in
 
-- You can access your Docker Hub repositories directly from Docker Desktop.
+- Access your Docker Hub repositories directly from Docker Desktop.
 
-- Authenticated users also get a higher pull rate limit compared to anonymous users. For more information, see [Usage and limits](/manuals/docker-hub/usage/_index.md).
+- Increase your pull rate limit compared to anonymous users. See [Usage and limits](/manuals/docker-hub/usage/_index.md).
 
-- Improve your organization’s security posture for containerized development by taking advantage of [Hardened Desktop](/manuals/security/for-admins/hardened-desktop/_index.md).
+- Enhance your organization’s security posture for containerized development with [Hardened Desktop](/manuals/security/for-admins/hardened-desktop/_index.md).
 
 > [!NOTE]
 >
 > Docker Desktop automatically signs you out after 90 days, or after 30 days of inactivity. 
 
 ## Signing in with Docker Desktop for Linux
 
-Docker Desktop for Linux relies on [`pass`](https://www.passwordstore.org/) to store credentials in gpg2-encrypted files.
+Docker Desktop for Linux relies on [`pass`](https://www.passwordstore.org/) to store credentials in GPG-encrypted files.
 Before signing in to Docker Desktop with your [Docker ID](/accounts/create-account/), you must initialize `pass`.
-Docker Desktop displays a warning if you've not initialized `pass`.
+Docker Desktop displays a warning if `pass` is not configured.
 
+1. Generate a GPG key. Run: 
 You can initialize pass by using a gpg key. To generate a gpg key, run:
 
-``` console
-$ gpg --generate-key
-``` 
+   ``` console
+   $ gpg --generate-key
+   ``` 
+2. Enter your name and email once prompted. 
 
-The following is an example similar to what you see once you run the previous command:
+   Once confirmed, GPG creates a key pair. Look for the `pub` line that contains your GPG ID, for example:
 
-```console {hl_lines=12}
-...
-GnuPG needs to construct a user ID to identify your key.
+   ```text
+   ...
+   pubrsa3072 2022-03-31 [SC] [expires: 2024-03-30]
+    3ABCD1234EF56G78
+   uid          Molly <[email protected]>
+   ```
+3.Copy the GPG ID and use it to initialize `pass`
 
-Real name: Molly
-Email address: [email protected]
-You selected this USER-ID:
-   "Molly <[email protected]>"
+   ```console
+   $ pass init <your_generated_gpg-id_public_key>
+   ``` 
 
-Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
-...
-pubrsa3072 2022-03-31 [SC] [expires: 2024-03-30]
- <generated gpg-id public key>
-uid          Molly <[email protected]>
-subrsa3072  2022-03-31 [E] [expires: 2024-03-30]
-```
-
-To initialize `pass`, run the following command using the public key generated from the previous command:
-
-```console
-$ pass init <your_generated_gpg-id_public_key>
-``` 
-The following is an example similar to what you see once you run the previous command:
+   You should see output similar to: 
 
-```console
-mkdir: created directory '/home/molly/.password-store/'
-Password store initialized for <generated_gpg-id_public_key>
-```
+   ```text
+   mkdir: created directory '/home/molly/.password-store/'
+   Password store initialized for <generated_gpg-id_public_key>
+   ```
 
 Once you initialize `pass`, you can sign in and pull your private images.
-When Docker CLI or Docker Desktop use credentials, a user prompt may pop up for the password you set during the gpg key generation.
+When Docker CLI or Docker Desktop use credentials, a user prompt may pop up for the password you set during the GPG key generation.
 
 ```console
 $ docker pull molly/privateimage
@@ -109,5 +101,5 @@ docker.io/molly/privateimage:latest
 ## What's next?
 
 - [Explore Docker Desktop](/manuals/desktop/use-desktop/_index.md) and its features. 
-- Change your Docker Desktop settings
-- [Browse common FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md)
+- Change your [Docker Desktop settings](/manuals/desktop/settings-and-maintenance/settings.md).
+- [Browse common FAQs](/manuals/desktop/troubleshoot-and-support/faqs/general.md).

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

@@ -2,13 +2,14 @@
 description: Instructions on how to enable nested virtualization
 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/
 weight: 30
 ---
 
-In general, we recommend running Docker Desktop natively on either Mac, Linux, or Windows. However, Docker Desktop for Windows can run inside a virtual desktop provided the virtual desktop is properly configured. 
+Docker recommends running Docker Desktop natively on Mac, Linux, or Windows.  However, Docker Desktop for Windows can run inside a virtual desktop provided the virtual desktop is properly configured. 
 
 To run Docker Desktop in a virtual desktop environment, it is essential nested virtualization is enabled on the virtual machine that provides the virtual desktop. This is because, under the hood, Docker Desktop is using a Linux VM in which it runs Docker Engine and the containers.
 
@@ -18,28 +19,27 @@ To run Docker Desktop in a virtual desktop environment, it is essential nested v
 >
 > Support for running Docker Desktop on a virtual desktop is available to Docker Business customers, on VMware ESXi or Azure VMs only.
 
-The support available from Docker extends to installing and running Docker Desktop inside the VM, once the nested virtualization is set up correctly. The only hypervisors we have 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/desktop/troubleshoot-and-support/support.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.
+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 multiples 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. 
 
 ## Turn on nested virtualization
 
 You must turn on nested virtualization before you install Docker Desktop on a virtual machine.
 
 ### Turn on nested virtualization on VMware ESXi
 
-Nested virtualization of other hypervisors like Hyper-V inside a vSphere VM [is not a supported scenario](https://kb.vmware.com/s/article/2009916). However, running Hyper-V VM in a VMware ESXi VM is technically possible and, depending on the version, ESXi includes hardware-assisted virtualization as a supported feature. For internal testing, we used a VM that had 1 CPU with 4 cores and 12GB of memory.
+Nested virtualization of other hypervisors like Hyper-V inside a vSphere VM [is not a supported scenario](https://kb.vmware.com/s/article/2009916). However, running Hyper-V VM in a VMware ESXi VM is technically possible and, depending on the version, ESXi includes hardware-assisted virtualization as a supported feature. A VM that had 1 CPU with 4 cores and 12GB of memory was used for internal testing.
 
 For steps on how to expose hardware-assisted virtualization to the guest OS, [see VMware's documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-2A98801C-68E8-47AF-99ED-00C63E4857F6.html).
 
-
 ### Turn on nested virtualization on an Azure Virtual Machine
 
 Nested virtualization is supported by Microsoft for running Hyper-V inside an Azure VM.
 
-For Azure virtual machines, [check that the VM size chosen supports nested virtualization](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes). Microsoft provides [a helpful list on Azure VM sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/acu) and highlights the sizes that currently support nested virtualization. For internal testing, we used D4s_v5 machines. We recommend this specification or above for optimal performance of Docker Desktop.
+For Azure virtual machines, [check that the VM size chosen supports nested virtualization](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes). Microsoft provides [a helpful list on Azure VM sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/acu) and highlights the sizes that currently support nested virtualization. D4s_v5 machines were used for internal testing. Use this specification or above for optimal performance of Docker Desktop.
 
 ## Docker Desktop support on Nutanix-powered VDI
 
@@ -57,6 +57,4 @@ Docker Desktop follows the VDI support definitions outlined [previously](#virtua
 
 ### Support scope and responsibilities
 
-If WSL 2 encounters issues - for example, it crashes, fails to start, or experiences performance degradation - contact Nutanix support.
-
-If Docker Desktop itself encounters issues, contact Docker support.
+For WSL 2-related issues, contact Nutanix support. For Docker Desktop-specific issues, contact Docker support.