Fix minor typos and grammar (bamarni#133)

summercms · Aug 3, 2022 · cba1fcd · cba1fcd
1 parent 2476470
commit cba1fcd
Show file tree

Hide file tree

Showing 12 changed files with 15 additions and 15 deletions.
diff --git a/README.md b/README.md
@@ -144,7 +144,7 @@ in `.vendor/bin/`:
   └── ...
 
 But what happens if another bin-namespace has a dependency using [Nikic PHP-Parser][6]? In that situation symlinks would
-collides and are not created (only the colliding ones).
+collide and are not created (only the colliding ones).
 
 
 ## Tips
@@ -213,17 +213,17 @@ There is a `forward mode` which is disabled by default. This can be activated by
 ```
 
 If this mode is activated, all your `composer install` and `composer update` commands are forwarded to all bin directories.
-This is an replacement for the tasks shown in section [Auto-installation](#auto-installation).
+This is a replacement for the tasks shown in section [Auto-installation](#auto-installation).
 
 ### Reduce clutter
 
-You can add following line to your `.gitignore` file in order to avoid committing dependencies of your tools.
+You can add the following line to your `.gitignore` file in order to avoid committing dependencies of your tools.
 
 ```.gitignore
 /vendor-bin/**/vendor
 ```
 
-Updating each tool can create many not legible changes in `composer.lock` files. You can use `.gitattributes` file in order 
+Updating each tool can create many not legible changes in `composer.lock` files. You can use a `.gitattributes` file in order 
 to inform git that it shouldn't show diffs of `composer.lock` files.
 
 ```.gitattributes

diff --git a/e2e/scenario0/script.sh b/e2e/scenario0/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario1/script.sh b/e2e/scenario1/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario10/script.sh b/e2e/scenario10/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario11/script.sh b/e2e/scenario11/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario2/script.sh b/e2e/scenario2/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario3/script.sh b/e2e/scenario3/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario5/script.sh b/e2e/scenario5/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario6/script.sh b/e2e/scenario6/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario7/script.sh b/e2e/scenario7/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario8/script.sh b/e2e/scenario8/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1

diff --git a/e2e/scenario9/script.sh b/e2e/scenario9/script.sh
@@ -2,7 +2,7 @@
 
 set -Eeuo pipefail
 
-# Set env envariables in order to experience a behaviour closer to what happens
+# Set env variables in order to experience a behaviour closer to what happens
 # in the CI locally. It should not hurt to set those in the CI as the CI should
 # contain those values.
 export CI=1