[feat] clarify and standardize executor intros

Hopefully simpler language makes it more understandable, and
standardized structure makes it easier to scan from page to page.

- Standardize structure
- Less words
- Use "shortcut" instead of "global option".

Author: MattDodsonEnglish

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

@@ -3,16 +3,21 @@ title: 'Shared iterations'
 excerpt: 'A fixed number of iterations are "shared" between a number of VUs, and the test ends once all iterations are executed.'
 ---
 
-## Description
+The `shared-iterations` executor shares iterations between the number of VUs.
+The test ends once k6 executes all iterations.
 
-In this executor, the iterations are shared between the number of VUs.
-The test ends once all iterations are executed. This executor is equivalent to the global [vus](/using-k6/k6-options/reference#vus) and [iterations](/using-k6/k6-options/reference#iterations) shortcut options.
+For a shortcut to this executor, use the [vus](/using-k6/k6-options/reference#vus) and [iterations](/using-k6/k6-options/reference#iterations) options.
+
+<Blockquote mod="note" title="">
 
 Iterations **are not guaranteed to be evenly distributed** with this executor.
 VU that executes faster will complete more iterations than slower VUs.
 
 To guarantee that every VU completes a specific, fixed number of iterations, [use the per-VU iterations executor](/using-k6/scenarios/executors/per-vu-iterations).
 
+</Blockquote>
+
+
 ## Options
 
 Besides the [common configuration options](/using-k6/scenarios#options),

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

@@ -3,10 +3,8 @@ title: 'Per VU iterations'
 excerpt: 'Each VU executes an exact number of iterations.'
 ---
 
-## Description
-
-Each VU executes an exact number of iterations. The total number of completed
-iterations will be `vus * iterations`.
+With the `per-vu-iterations` executor, each VU executes an exact number of iterations.
+The total number of completed iterations equals `vus * iterations`.
 
 ## Options
 

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

@@ -3,10 +3,9 @@ title: 'Constant VUs'
 excerpt: 'A fixed number of VUs execute as many iterations as possible for a specified amount of time.'
 ---
 
-## Description
+With the `constant-vus` executor, a fixed number of VUs execute as many iterations as possible for a specified amount of time.
 
-A fixed number of VUs execute as many iterations as possible for a specified amount
-of time. This executor is equivalent to the global [vus](/using-k6/options#vus) and [duration](/using-k6/options#duration) options.
+For a shortcut to this executor, use the [vus](/using-k6/options#vus) and [duration](/using-k6/options#duration) options.
 
 ## Options
 

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

@@ -3,10 +3,9 @@ title: 'Ramping VUs'
 excerpt: 'A variable number of VUs execute as many iterations as possible for a specified amount of time.'
 ---
 
-## Description
+With the `ramping-vus` executor, a variable number of VUs executes as many iterations as possible for a specified amount of time.
 
-A variable number of VUs execute as many iterations as possible for a specified
-amount of time. This executor is equivalent to the global [stages](/using-k6/options#stages) option.
+For a shortcut to this executor, use the [stages](/using-k6/options#stages) option.
 
 ## Options
 

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

@@ -3,18 +3,14 @@ title: 'Constant arrival rate'
 excerpt: 'A fixed number of iterations are started in a specified period of time.'
 ---
 
-## Description
+With the `constant-arrival-rate` executor, k6 starts a fixed number of iterations over a specified period of time.
+It is an open-model executor, meaning iterations start independently of system response (for details, read
+[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed).
 
-A fixed number of iterations are started in a specified period of time.
-This executor will continue to start iterations at the given rate as long as there are VUs
-available to run them. Since iteration execution time can vary because of test logic or the
-system-under-test responding more slowly, this executor will try to compensate
-by running a variable number of VUs—including potentially initializing more in the middle
-of the test—to meet the configured iteration rate. This approach is
-useful for a more accurate representation of RPS, for example.
-
-For explanations about how this executor works, refer to [Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed)
-and [Arrival-rate VU allocation](/using-k6/scenarios/concepts/arrival-rate-vu-allocation).
+This executor continues to start iterations at the given rate as long as VUs are available.
+The time to execute an iteration can vary with test logic or the system-under-test response time.
+To compensate for this, the executor starts a varied number of VUs to meet the configured iteration rate.
+For explanations of how allocation works, read [Arrival-rate VU allocation](/using-k6/scenarios/concepts/arrival-rate-vu-allocation).
 
 <Blockquote mod="Note" title="">
 
@@ -42,6 +38,8 @@ this executor has the following options:
 
 When you want to maintain a constant number of iterations without being affected by the
 performance of the system under test.
+This approach is useful for a more accurate representation of RPS, for example.
+
 
 <Blockquote mod="note" title="">
 
@@ -54,7 +52,7 @@ So it's unnecessary to use a `sleep()` function at the end of the VU code.
 
 ## Example
 
-In this example, we'll start a constant rate of 30 iterations per second for 30 seconds, allowing k6 to dynamically schedule up to 50 VUs.
+This example starts a constant rate of 30 iterations per second for 30 seconds, allowing k6 to dynamically schedule up to 50 VUs.
 
 <CodeGroup labels={[ "constant-arr-rate.js" ]} lineNumbers={[true]}>
 

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

@@ -3,14 +3,14 @@ title: 'Ramping arrival rate'
 excerpt: 'A variable number of iterations are started in a specified period of time.'
 ---
 
-## Description
+With the `ramping-arrival-rate` executor, k6 starts iterations at a variable rate.
+It is an open-model executor, meaning iterations start independently of system response (for details, read
+[Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed).
 
-A variable number of iterations are started in specified periods of time. This is
-similar to the [ramping VUs executor](/using-k6/scenarios/executors/ramping-vus/), but for iterations instead.
-k6 will attempt to dynamically change the number of VUs to achieve the configured iteration rate.
-
-For explanations about how this executor works, refer to [Open and Closed models](/using-k6/scenarios/concepts/open-vs-closed)
-and [Arrival-rate VU allocation](/using-k6/scenarios/concepts/arrival-rate-vu-allocation).
+This executor has _stages_ that configure target number of iterations and the time k6 takes to reach or stay at this target.
+Unlike the [ramping VUs executor](/using-k6/scenarios/executors/ramping-vus/), which configures VUs,
+this executor dynamically changes the number of iterations to start, and starts these iterations as long as the test has enough allocated VUs.
+To learn how allocation works, read [Arrival-rate VU allocation](/using-k6/scenarios/concepts/arrival-rate-vu-allocation).
 
 <Blockquote mod="Note" title="">
 
@@ -37,7 +37,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
-would like to ramp the number of iterations up or down during specific periods of time.
+want to ramp the number of iterations up or down during specific periods of time.
 
 <Blockquote mod="note" title="">