Merge pull request #1224 from no-yan/chore/fix-typo

goldbergyoni · Mar 19, 2023 · 24b6e69 · 24b6e69
2 parents 4b1cd95 + e546e18
commit 24b6e69
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git 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*
 
 <br/><br/>
 

diff --git 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*
 
 <br/><br/>