From e546e18c341a0e0b5a83a2b9e542c98ff4f5d7bb Mon Sep 17 00:00:00 2001 From: no-yan <63000297+no-yan@users.noreply.github.com> Date: Sat, 18 Mar 2023 12:06:19 +0900 Subject: [PATCH] docs: fix typo --- sections/docker/clean-cache.french.md | 2 +- sections/docker/clean-cache.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sections/docker/clean-cache.french.md b/sections/docker/clean-cache.french.md index 4fcecc0f..1c4bad56 100644 --- a/sections/docker/clean-cache.french.md +++ b/sections/docker/clean-cache.french.md @@ -6,7 +6,7 @@ Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag. -*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage* +*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*

diff --git a/sections/docker/clean-cache.md b/sections/docker/clean-cache.md index 481f35e1..c5ab40ec 100644 --- a/sections/docker/clean-cache.md +++ b/sections/docker/clean-cache.md @@ -6,7 +6,7 @@ Node package managers, npm & Yarn, cache the installed packages locally so that future projects which need the same libraries won't need to fetch from a remote repository. Although this duplicates the packages and consumes more storage - it pays off in a local development environment that typically keeps installing the same packages. In a Docker container this storage increase is worthless since it installs the dependency only once. By removing this cache, using a single line of code, tens of MB are shaved from the image. While doing so, ensure that it doesn't exit with non-zero code and fail the CI build because of caching issues - This can be avoided by including the --force flag. -*Please not that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage* +*Please note that this is not relevant if you are using a multi-stage build as long as you don't install new packages in the last stage*