vale corrections

Author: sarahsanders-docker

_vale/config/vocabularies/Docker/accept.txt

@@ -9,6 +9,7 @@ Artifactory
 auditable
 autolock
 Azure
+Azure AD
 bootup
 Btrfs
 Bugsnag
@@ -142,6 +143,7 @@ osxfs
 OTel
 Paketo
 pgAdmin
+plist
 PKG
 Postgres
 PowerShell
@@ -172,6 +174,7 @@ Syft
 syntaxes
 Sysbox
 sysctls
+sysctl
 Sysdig
 systemd
 Testcontainers

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

@@ -491,8 +491,8 @@ To use Docker Desktop with Windows Containers, ensure that FDVDenyWriteAccess is
 **Computer Configuration** > **Administrative Templates** > **Windows Components** > **BitLocker Drive Encryption** > **Fixed Data Drives** > **Deny write access to fixed drives not protected by BitLocker**
 
 > [!NOTE]
-> 
-> Modifying Group Policy settings may require administrator privileges and should comply with your organization's IT policies. If the setting gets reset after some time this usually means that it was overriden by the centralized configuration of your IT department. Talk to them before making any changes.
+>
+> Modifying Group Policy settings may require administrator privileges and should comply with your organization's IT policies. If the setting gets reset after some time this usually means that it was overridden by the centralized configuration of your IT department. Talk to them before making any changes.
 
 ### `Docker Desktop Access Denied` error message when starting Docker Desktop
 

content/manuals/enterprise/security/hardened-desktop/air-gapped-containers.md

@@ -174,7 +174,7 @@ function FindProxyForURL(url, host) {
     }
   }
 
-  // Block access to developer's localhost to prevent data exfiltration
+  // Block access to developer's localhost
   if (host === "host.docker.internal" || host === "localhost") {
     return "PROXY reject.docker.internal:1234";
   }

content/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/config.md

@@ -115,7 +115,7 @@ Docker Desktop validates allowed images by:
 1. Comparing container image digests against the allowlist when containers start
 1. Blocking containers whose digests don't match allowed images
 
-This prevents bypassing restrictions by retagging unauthorized images:
+This prevents bypassing restrictions by re-tagging unauthorized images:
 
 ```console
 $ docker tag malicious-image docker:cli

content/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/faq.md

@@ -71,7 +71,7 @@ ECI protection varies by container type and Docker Desktop version:
 
 - Docker Extensions
 - Docker Debug containers
-- Kubernetes with kubeadm provisioner
+- Kubernetes with Kubeadm provisioner
 
 For complete details, see [ECI limitations](/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/limitations.md).
 

content/manuals/enterprise/security/hardened-desktop/enhanced-container-isolation/limitations.md

@@ -47,7 +47,7 @@ containers mode isn't supported.
 
 ## Docker Build protection varies
 
-Docker Build proection depends on the driver and Docker Desktop version:
+Docker Build protection depends on the driver and Docker Desktop version:
 
 | Build drive | Protection | Version requirements |
 |:------------|:-----------|:---------------------|

content/manuals/enterprise/security/hardened-desktop/settings-management/_index.md

@@ -54,7 +54,7 @@ When multiple policies exist, Docker Desktop applies them in this order:
 
 1. User-specific policies: Highest priority
 1. Organization default policy: Applied when no user-specific policy exists
-1. Local `admin-settings.json` file: Lowest priority, overriden by Admin Console policies
+1. Local `admin-settings.json` file: Lowest priority, overridden by Admin Console policies
 
 ## Set up Settings Management
 

content/manuals/enterprise/security/hardened-desktop/settings-management/settings-reference.md

@@ -23,7 +23,7 @@ methods are indicated with these labels:
 
 - Desktop GUI: Configurable through Docker Desktop settings interface
 - Admin Console: Configurable through the Docker Admin Console using Settings Management
-- JSON file: Configurable htrough `admin-settings.json` using Settings Managemet
+- JSON file: Configurable through `admin-settings.json` using Settings Management
 - CLI: Configurable through command-line tools
 
 ## General settings
@@ -344,7 +344,7 @@ if needed.
 
 - **Description:** Automatic SBOM indexing for images without requiring user interaction.
 - **OS:** {{< badge color=blue text="All" >}}
-- **Use case:** KKeep image metadata current by indexing during idle time or after image operations.
+- **Use case:** Keep image metadata current by indexing during idle time or after image operations.
 - **Configure this setting with:**
     - **General settings** in [Docker Desktop GUI](/manuals/desktop/settings-and-maintenance/settings.md)
 

content/manuals/enterprise/security/provisioning/just-in-time.md

@@ -16,7 +16,7 @@ This page explains how JIT provisioning works, SSO authentication flows, and how
 
 ## Prerequisites
 
-Before you beging, you must have:
+Before you begin, you must have:
 
 - SSO configured for your organization
 - Administrator access to Docker Home and your identity provider

content/manuals/enterprise/security/provisioning/scim.md

@@ -83,7 +83,7 @@ To enable SCIM:
 
 1. Sign in to [Docker Home](https://app.docker.com).
 1. Select **Admin Console**, then **SSO and SCIM**.
-1. In the **SSO connections** table, select the **Actions** icon for your conection, then select **Setup SCIM**.
+1. In the **SSO connections** table, select the **Actions** icon for your connection, then select **Setup SCIM**.
 1. Copy the **SCIM Base URL** and **API Token** and paste the values into your IdP.
 
 ## Enable SCIM in your IdP