From 810e553ccd1daee20a855080efa02c22b98ffe71 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Wed, 27 May 2026 14:59:41 +0100 Subject: [PATCH] 25174 25165 (#25179) ## Description Closes https://github.com/docker/docs/issues/25165 Addresses https://github.com/docker/docs/issues/25174 ## Related issues or tickets ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- content/manuals/desktop/features/wsl/_index.md | 2 +- .../manuals/extensions/extensions-sdk/architecture/_index.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/manuals/desktop/features/wsl/_index.md b/content/manuals/desktop/features/wsl/_index.md index 7dd7df427a..bf6c7c8215 100644 --- a/content/manuals/desktop/features/wsl/_index.md +++ b/content/manuals/desktop/features/wsl/_index.md @@ -41,7 +41,7 @@ that was installed directly inside a WSL Linux distribution. Running both can ca 4. Navigate to **Settings**. 5. From the **General** tab, select **Use WSL 2 based engine**. - If you have installed Docker Desktop on a system that supports WSL 2, this option is turned on by default. + If you have installed Docker Desktop on a system that supports WSL 2, this option is turned on by default and the setting is not visible. 6. Select **Apply**. `docker` commands are now available from any Windows terminal using the WSL 2 engine. diff --git a/content/manuals/extensions/extensions-sdk/architecture/_index.md b/content/manuals/extensions/extensions-sdk/architecture/_index.md index 15e2ff1a02..1153323bd2 100644 --- a/content/manuals/extensions/extensions-sdk/architecture/_index.md +++ b/content/manuals/extensions/extensions-sdk/architecture/_index.md @@ -62,7 +62,7 @@ file Usually, the backend is made of one container that runs within the Docker Desktop VM. Internally, Docker Desktop creates a Docker Compose project, creates the container from the `image` option of the `vm` section of the `metadata.json`, and -attaches it to the Compose project. See the [ui metadata section](metadata.md#vm-section) for more details. +attaches it to the Compose project. See the [`vm` metadata section](metadata.md#vm-section) for more details. In some cases, a `compose.yaml` file can be used instead of an `image`. This is useful when the backend container needs more specific options, such as mounting volumes or requesting [capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) @@ -97,7 +97,7 @@ Shipping those executables with the extension ensure that the CLI tool is always the users' machine. When Docker Desktop installs the extension, it copies the executables on the host as defined by the `host` section in -the `metadata.json`. See the [ui metadata section](metadata.md#host-section) for more details. +the `metadata.json`. See the [`host` metadata section](metadata.md#host-section) for more details. ![Executable and frontend communication](images/extensions-arch-3.png?w=250h=300)