[fix] Correct grammatical number

and other language trims

Author: MattDodsonEnglish

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/01 shared-iterations.md

@@ -31,12 +31,12 @@ this executor has the following options:
 
 ## When to use
 
-This executor is suitable when you want a specific amount of VUs to complete a fixed
-number of total iterations, and the amount of iterations per VU is not important. This will be 
-the most _"efficient"_ use of VUs, therefore if **time to complete** a number of test iterations
-is your concern, this executor should perform best. 
+This executor is suitable when you want a specific number of VUs to complete a fixed
+number of total iterations, and the amount of iterations per VU is unimportant.
+If the **time to complete** a number of test iterations is your concern, this executor should perform best.
 
-> An example use case could be to incorporate a quick performance test as part of the build cycle during development. As developers compile their changes, the test could be executed against the local code to help insure against performance regressions. This would be considered as part of _"shifting left"_; placing more emphasis on performance early in the development cycle when the _cost_ of the fix is lowest. 
+An example use case is for quick performance tests in the developement build cycle.
+As developers make changes, they might run the test against the local code to test for performance regressions. Thus the executor works well with a _shift-left_ policy, where emphasizes testing performance early in the development cycle when the cost of a fix is lowest. 
 
 ## Example
 

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/02 per-vu-iterations.md

@@ -19,7 +19,7 @@ this executor has the following options:
 
 ## When to use
 
-Use this executor if you need a specific amount of VUs to complete the same amount of
+Use this executor if you need a specific number of VUs to complete the same number of
 iterations. This can be useful when you have fixed sets of test data that you want to
 partition between VUs.
 

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/03 constant-vus.md

@@ -19,7 +19,7 @@ this executor has the following options:
 
 ## When to use
 
-Use this executor if you need a specific amount of VUs to run for a certain amount of time.
+Use this executor if you need a specific number of VUs to run for a certain amount of time.
 
 ## Example
 

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/05 constant-arrival-rate.md

@@ -36,8 +36,7 @@ this executor has the following options:
 
 ## When to use
 
-When you want to maintain a constant number of iterations without being affected by the
-performance of the system under test.
+When you want iterations to remain constant, independent of the performance of the system under test.
 This approach is useful for a more accurate representation of RPS, for example.
 
 

src/data/markdown/translated-guides/en/02 Using k6/14 Scenarios/01 Executors/06 ramping-arrival-rate.md

@@ -36,7 +36,7 @@ this executor has the following options:
 
 ## When to use
 
-If you need your tests to not be affected by the system-under-test's performance, and
+If you need start iterations independent of system-under-test performance, and
 want to ramp the number of iterations up or down during specific periods of time.
 
 <Blockquote mod="note" title="">