small updates for consistency/clarity

Author: heitortsergent

src/data/markdown/docs/05 Examples/02 Tutorials/01 Get started with k6/100 Test-for-functional-behavior.md

@@ -66,13 +66,23 @@ After the test finishes, k6 reports the [default result summary](/results-output
   ...
 ```
 
-To make sure you're getting the right response, you could log the response body to the console as follows:
+As an optional step, you can log the response body to the console to make sure you're getting the right response.
+
+<CodeGroup labels={["api-test.js"]} lineNumbers={[]} showCopyButton={[true]}>
 
 ```javascript
-const res = http.post(url, payload, params);
-console.log(res.body);
+export default function () {
+  ...
+
+  const res = http.post(url, payload, params);
+
+  // Log the request body
+  console.log(res.body);
+}
 ```
 
+</CodeGroup>
+
 ## Add response checks
 
 Once you're sure the request is well-formed, add a [check](/using-k6/checks) that validates whether the system responds with the expected status code.
@@ -111,6 +121,12 @@ Once you're sure the request is well-formed, add a [check](/using-k6/checks) tha
   
   </CodeGroup>
 
+1. Run the script again.
+
+  ```bash
+  k6 run api-test.js
+  ```
+
 1. Inspect the result output for your check.
    It should look something like this.
 

src/data/markdown/docs/05 Examples/02 Tutorials/01 Get started with k6/200 Test for performance.md

@@ -11,7 +11,7 @@ In this tutorial, learn how to:
 - Use [thresholds](/using-k6/thresholds) to assert for performance criteria
 - Configure load increases through [scenarios](/using-k6/scenarios)
 
-These examples build on the script from the previous section.
+These examples build on the script from the [previous section](/examples/tutorials/get-started-with-k6/test-for-functional-behavior/).
 
 ## Context: meet service-level objectives
 
@@ -24,7 +24,8 @@ The service must meet these SLOs under different types of usual traffic.
 ## Assert for performance with thresholds
 
 To codify the SLOs, add [_thresholds_](/using-k6/thresholds) to test that your system performs to its goal criteria.
-Thresholds are set in options.
+
+Thresholds are set in the [`options`](/using-k6/k6-options/) object.
 
 
 ```javascript
@@ -37,7 +38,7 @@ export const options = {
 };
 ```
 
-Add this [`options`](/using-k6/k6-options/) object with thresholds to your script `api-test.js`. 
+Add this `options` object with thresholds to your script `api-test.js`. 
 
 
 <CodeGroup labels={["api-test.js"]} lineNumbers={[true]} showCopyButton={[true]}
@@ -83,13 +84,12 @@ export default function () {
 
 </CodeGroup>
 
-Run the test as usual: 
+Run the test. 
 
 ```bash
 k6 run api-test.js
 ```
 
-
 Inspect the console output to determine whether performance crossed a threshold.
 
 ```
@@ -98,7 +98,7 @@ Inspect the console output to determine whether performance crossed a threshold.
 ✗ http_req_failed................: 0.00% ✓ 0        ✗ 1
 ```
 
-
+The ✓ and ✗ symbols indicate whether the performance thresholds passed or failed.
 
 ## Test performance under increasing load
 
@@ -110,7 +110,7 @@ Scenarios schedule load according to the number of VUs, number of iterations, VU
 
 ### Run a smoke test
 
-Start small. Run a [smoke test](/test-types/smoke-testing "a small test to confirm the script works properly") to see your script can handle minimal load.
+Start small. Run a [smoke test](/test-types/smoke-testing "a small test to confirm the script works properly") to check that your script can handle a minimal load.
 
 To do so, use the [`--iterations`](/using-k6/k6-options/reference/#iterations) flag with an argument of 10 or fewer.
 
@@ -123,15 +123,11 @@ Good thing you ran the test early!
 
 ### Run a test against an average load
 
-Now increase the load.
-
 Generally, traffic doesn't arrive all at once.
 Rather, it gradually increases to a peak load.
 To simulate this, testers increase the load in _stages_.
 
-Since this is a learning environment, the stages are still quite short.
-Add the following _scenario_ to your options `object` and rerun the test.
-Where the smoke test defined the load in terms of iterations, this configuration uses the [`ramping-vus` executor](/using-k6/scenarios/executors/ramping-vus/) to express load through virtual users and duration.
+Add the following `scenario` property to your `options` object and rerun the test.
 
 ```javascript
 export const options = {
@@ -158,6 +154,9 @@ export const options = {
 };
 ```
 
+Since this is a learning environment, the stages are still quite short.
+Where the smoke test defined the load in terms of iterations, this configuration uses the [`ramping-vus` executor](/using-k6/scenarios/executors/ramping-vus/) to express load through virtual users and duration.
+
 Run the test with no command-line flags: 
 
 ```bash
@@ -167,7 +166,6 @@ k6 run api-test.js
 The load is small, so the server should perform within thresholds.
 However, this test server may be under load by many k6 learners, so the results are unpredictable.
 
-
 <Blockquote mod="note" title="To visualize results...">
 
 At this point, it'd be nice to have a graphical interface to visualize metrics as they occur.
@@ -184,13 +182,13 @@ In this case, run the test until the availability (error rate) threshold is cros
 
 To do this:
 
-1. Configure the threshold to abort when it fails.
+1. Add the `abortOnFail` property to `http_req_failed`.
 
   ```javascript
   http_req_failed: [{ threshold: "rate<0.01", abortOnFail: true }], // http errors should be less than 1%, otherwise abort the test
   ```
 
-1. Configure the load to ramp the test up until it fails.
+1. Update the `scenarios` property to ramp the test up until it fails.
 
   ```javascript
   export const options = {
@@ -219,7 +217,6 @@ To do this:
   ```
 
 Here is the full script.
-Copy and run it with `k6 run api-test.js`.
 
 <CodeGroup labels={["api-test.js"]} lineNumbers={[true]} showCopyButton={[true]}
 heightTogglers={[true]}>
@@ -281,13 +278,18 @@ export default function () {
 
 </CodeGroup>
 
+Run the test. 
+
+```bash
+k6 run api-test.js
+```
+
 Did the threshold fail? If not, add another stage with a higher target and try again. Repeat until the threshold aborts the test:
 
 ```bash
 ERRO[0010] thresholds on metrics 'http_req_duration, http_req_failed' were breached; at least one has abortOnFail enabled, stopping test prematurely 
 ```
 
-
 ## Next steps
 
 In this tutorial, you used [thresholds](/using-k6/thresholds/) to assert performance and [Scenarios](/using-k6/scenarios) to schedule different load patterns. To learn more about the usual load patterns and their goals, read [Load Test Types](/test-types/load-test-types/)

src/data/markdown/docs/05 Examples/02 Tutorials/01 Get started with k6/300 Analyze results.md

@@ -45,16 +45,14 @@ vus_max........................: 20     min=20     max=20
 
 For simplicity to learn about [k6 metric results](/using-k6/metrics/reference/), this tutorial uses the [JSON output](/results-output/real-time/json) and [jq](https://jqlang.github.io/jq/) to filter results.
 
+For other options to analyze test results such as storage and time-series visualizations in real-time, check out:
 
-For other options to analyze test results such as storage and time-series visualizations in real-time, review:
 - [Results output](/results-output/overview/)
 - [Ways to visualize k6 results](https://k6.io/blog/ways-to-visualize-k6-results/)
 
-
-
 ## Write time-series results to a JSON file
 
-To output results as JSON lines, use the `--out` flag.
+To output results to a JSON file, use the `--out` flag.
 
 ```bash
 k6 run --out json=results.json api-test.js
@@ -66,14 +64,13 @@ Then run this `jq` command to filter the latency results; `http_req_duration` me
 jq '. | select(.type == "Point" and .metric == "http_req_duration")' results.json
 ```
 
-k6 results have a number of [built-in tags](/using-k6/tags-and-groups/#system-tags).
-For example, filter results to only results where the status is 200:
+k6 results have a number of [built-in tags](/using-k6/tags-and-groups/#system-tags). For example, filter results to only results where the status is 200.
 
 ```bash
 jq '. | select(.type == "Point" and .data.tags.status == "200")' results.json
 ```
 
-And calculate the aggregated value of any metric with any particular tags. For example, 
+Or calculate the aggregated value of any metric with any particular tags.
 
 <CodeGroup labels={["Average", "Min", "Max"]} lineNumbers={[false]} showCopyButton={[true]} heightTogglers={[true]}>
 
@@ -93,12 +90,9 @@ jq '. | select(.type == "Point" and .metric == "http_req_duration") | .data.valu
 
 ## Apply custom tags
 
-You can also apply [_Tags_](/using-k6/tags-and-groups/#tags) to requests or code blocks.
-To do so:
+You can also apply [_Tags_](/using-k6/tags-and-groups/#tags) to requests or code blocks. For example, this is how you can add a [`tags`](/using-k6/tags-and-groups/#tags) to the [request params](/javascript-api/k6-http/params/).
 
-Add a [`tags`](/using-k6/tags-and-groups/#tags) object in the [request params](/javascript-api/k6-http/params/). Give the tag a key and value.
-
-  ```javascript
+```javascript
   const params = {
     headers: {
       "Content-Type": "application/json",
@@ -107,9 +101,9 @@ Add a [`tags`](/using-k6/tags-and-groups/#tags) object in the [request params](/
       "my-custom-tag": "auth-api",
     },
   };
-  ```
+```
 
-Pass `params` to the `http` request. Create the file `tagged-login.js`:
+Create a new script named "tagged-login.js", and add a custom tag to it.
 
   <CodeGroup labels={["tagged-login.js"]} showCopyButton={[true]} heightTogglers={[true]}>
 
@@ -153,9 +147,8 @@ jq '. | select(.type == "Point" and .metric == "http_req_duration" and .data.tag
 
 ## Organize requests in groups
 
-You can also organize your test logic into [Groups](/using-k6/tags-and-groups#groups), test logic inside a `group` tags to all requests and metrics within its block.
-Groups can help you to organize the test as a series of logical transactions or blocks.
-
+You can also organize your test logic into [Groups](/using-k6/tags-and-groups#groups). Test logic inside a `group` tags to all requests and metrics within its block.
+Groups can help you organize the test as a series of logical transactions or blocks.
 
 ### Context: a new test to group test logic
 
@@ -275,8 +268,7 @@ As an example, create a metric that collects latency results for each group:
 1. Create two duration trend metric functions.
 1. In each group, add the `duration` time to the trend for requests to `contacts` and the `coin_flip` endpoints.
 
-
-<CodeGroup labels={["Adding custom metrics"]} lineNumbers={["false"]} showCopyButton={[true]} heightTogglers={[true]}>
+<CodeGroup labels={["multiple-flows.js"]} lineNumbers={["false"]} showCopyButton={[true]} heightTogglers={[true]}>
 
 ```javascript
 //import necessary modules
@@ -326,20 +318,20 @@ export default function () {
 
 </CodeGroup>
 
-Run the test with small number of iterations and output the results to `results.json`:
+Run the test with small number of iterations and output the results to `results.json`.
 
 ```bash
 k6 run multiple-flows.js --out json=results.json --iterations 10
 ```
 
-Look for the custom trend metrics in the end-of-test console summary:
+Look for the custom trend metrics in the end-of-test console summary.
 
 ```bash
 coinflip_duration..............: avg=119.6438  min=116.481  med=118.4755 max=135.498  p(90)=121.8459 p(95)=123.89565
 contacts_duration..............: avg=125.76985 min=116.973  med=120.6735 max=200.507  p(90)=127.9271 p(95)=153.87245
 ```
 
-You can also query custom metric results from the JSON results. For example, to get the aggregated results as:
+You can also query custom metric results from the JSON results. For example, to get the aggregated results as.
 
 
 <CodeGroup labels={["Average", "Min", "Max"]} lineNumbers={[false]} showCopyButton={[true]} heightTogglers={[true]}>

src/data/markdown/docs/05 Examples/02 Tutorials/01 Get started with k6/400 Reuse and re-run tests.md

@@ -175,7 +175,7 @@ To do so, follow these steps:
     // Put visits to contact page in one group
     contacts(baseUrl);
     // Coinflip players in another group
-    contacts(baseUrl);
+    coinflip(baseUrl);
   }
 
   //define configuration