From 92cdc25f8897d5bea6e15fdad901850f07a1890a Mon Sep 17 00:00:00 2001 From: Nedunchezhiyan-M Date: Fri, 17 Apr 2026 20:19:14 +0530 Subject: [PATCH] docs: fix spurious 'to' and double slash URL in two files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - engine/containers/start-containers-automatically.md: remove spurious 'to' from 'lets you to keep' → 'lets you keep'. After 'lets you', the verb should be in the bare infinitive (no 'to'). - build/buildkit/configure.md: fix double slash in GitHub URL 'blob/master//hack' → 'blob/master/hack' --- content/manuals/build/buildkit/configure.md | 2 +- .../manuals/engine/containers/start-containers-automatically.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/manuals/build/buildkit/configure.md b/content/manuals/build/buildkit/configure.md index c05b2b2dbd..021f9cd48c 100644 --- a/content/manuals/build/buildkit/configure.md +++ b/content/manuals/build/buildkit/configure.md @@ -141,7 +141,7 @@ available in the default BuildKit image. But you can create your own image that includes CNI support. The following Dockerfile example shows a custom BuildKit image with CNI support. -It uses the [CNI config for integration tests](https://github.com/moby/buildkit/blob/master//hack/fixtures/cni.json) +It uses the [CNI config for integration tests](https://github.com/moby/buildkit/blob/master/hack/fixtures/cni.json) in BuildKit as an example. Feel free to include your own CNI configuration. ```dockerfile diff --git a/content/manuals/engine/containers/start-containers-automatically.md b/content/manuals/engine/containers/start-containers-automatically.md index c513208bf8..f323e2d832 100644 --- a/content/manuals/engine/containers/start-containers-automatically.md +++ b/content/manuals/engine/containers/start-containers-automatically.md @@ -17,7 +17,7 @@ Docker recommends that you use restart policies, and avoid using process managers to start containers. Restart policies are different from the `--live-restore` flag of the `dockerd` -command. Using `--live-restore` lets you to keep your containers running during +command. Using `--live-restore` lets you keep your containers running during a Docker upgrade, though networking and user input are interrupted. ## Use a restart policy