fix typo (venodor -> vendor)

quantk · quantk · commit 6eef23ad8f76 · 2022-08-01T18:47:02.000+03:00
diff --git a/_posts/2022-07-02-codeception-5.markdown b/_posts/2022-07-02-codeception-5.markdown
@@ -111,13 +111,13 @@ In this case, you specify the batch of tests that should be executed independent
 
 ```
 # first job
-./venodor/bin/codecept run --shard 1/3
+./vendor/bin/codecept run --shard 1/3
 
 # second job
-./venodor/bin/codecept run --shard 2/3
+./vendor/bin/codecept run --shard 2/3
 
 # third job
-./venodor/bin/codecept run --shard 3/3
+./vendor/bin/codecept run --shard 3/3
 ```
 
 This feature reduces the need for complex configuration and usage of `robo` task runner to split tests.
@@ -129,7 +129,7 @@ It is recommended to use sharding to parallelize tests between multiple jobs as
 New options `--grep` and `--filter` were introduced to select tests by part of their name. Actually, it is the same option and an alias. `--grep` is a common way to select tests to execute in NodeJS test runners, so we ported it to Codeception. But as usual, specific tests can also be executed by group or specifying a test signature.
 
 ```
-php venodor/bin/codecept run --grep "user"
+php vendor/bin/codecept run --grep "user"
 ```
 
 ## Other Changes
diff --git a/docs/12-ParallelExecution.md b/docs/12-ParallelExecution.md
@@ -24,19 +24,19 @@ Each job should have Codeception running a subset of tests set by `--shard` opti
 First job
 
 ```
-php venodor/bin/codecept run --shard 1/3
+php vendor/bin/codecept run --shard 1/3
 ```
 
 Second job
 
 ```
-php venodor/bin/codecept run --shard 2/3
+php vendor/bin/codecept run --shard 2/3
 ```
 
 Third job
 
 ```
-php venodor/bin/codecept run --shard 3/3
+php vendor/bin/codecept run --shard 3/3
 ```
 
 For each job you specify on how many groups tests should be split and the group that should be executed on this agent.
diff --git a/docs/ParallelExecution.md b/docs/ParallelExecution.md
@@ -24,19 +24,19 @@ Each job should have Codeception running a subset of tests set by `--shard` opti
 First job
 
 ```
-php venodor/bin/codecept run --shard 1/3
+php vendor/bin/codecept run --shard 1/3
 ```
 
 Second job
 
 ```
-php venodor/bin/codecept run --shard 2/3
+php vendor/bin/codecept run --shard 2/3
 ```
 
 Third job
 
 ```
-php venodor/bin/codecept run --shard 3/3
+php vendor/bin/codecept run --shard 3/3
 ```
 
 For each job you specify on how many groups tests should be split and the group that should be executed on this agent.
diff --git a/guides/12-ParallelExecution.md b/guides/12-ParallelExecution.md
@@ -18,19 +18,19 @@ Each job should have Codeception running a subset of tests set by `--shard` opti
 First job
 
 ```
-php venodor/bin/codecept run --shard 1/3
+php vendor/bin/codecept run --shard 1/3
 ```
 
 Second job
 
 ```
-php venodor/bin/codecept run --shard 2/3
+php vendor/bin/codecept run --shard 2/3
 ```
 
 Third job
 
 ```
-php venodor/bin/codecept run --shard 3/3
+php vendor/bin/codecept run --shard 3/3
 ```
 
 For each job you specify on how many groups tests should be split and the group that should be executed on this agent.
