From 0e469c1d1d85a134ce2c3233231cad2379af83c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20K=C3=A4ufl?= Date: Thu, 7 Feb 2019 13:23:13 +0100 Subject: [PATCH] Fix typos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Michael Käufl --- docs/reference/commandline/build.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/commandline/build.md b/docs/reference/commandline/build.md index a2f4763f84..21220c631d 100644 --- a/docs/reference/commandline/build.md +++ b/docs/reference/commandline/build.md @@ -504,13 +504,13 @@ stable. Squashing layers can be beneficial if your Dockerfile produces multiple layers -modifying the same files, for example, file that are created in one step, and +modifying the same files, for example, files that are created in one step, and removed in another step. For other use-cases, squashing images may actually have a negative impact on performance; when pulling an image consisting of multiple layers, layers can be pulled in parallel, and allows sharing layers between images (saving space). -For most use cases, multi-stage are a better alternative, as they give more +For most use cases, multi-stage builds are a better alternative, as they give more fine-grained control over your build, and can take advantage of future optimizations in the builder. Refer to the [use multi-stage builds](https://docs.docker.com/develop/develop-images/multistage-build/) section in the userguide for more information. @@ -531,7 +531,7 @@ The `--squash` option has a number of known limitations: downloading a single layer cannot be parallelized. - When attempting to squash an image that does not make changes to the filesystem (for example, the Dockerfile only contains `ENV` instructions), - the squash step will fail (see [issue #33823](https://github.com/moby/moby/issues/33823) + the squash step will fail (see [issue #33823](https://github.com/moby/moby/issues/33823)). #### Prerequisites