Minor lang trims to new output docs

- Avoid directional language
- Write parameters in monospace
- Prefer contractions to shorten text and make friendlier tone

Author: MattDodsonEnglish

src/data/markdown/translated-guides/en/03 Results output/200 Real-time/00 Dynatrace.md

@@ -3,19 +3,20 @@ title: 'Dynatrace'
 excerpt: Send k6 output to Dynatrace to visualize load test results and correlate performance testing metrics in Dynatrace.
 ---
 
-Using the [Dynatrace k6 extension](https://github.com/Dynatrace/xk6-output-dynatrace) you can send metrics to [Dynatrace](https://www.dynatrace.com/). That allows visualizing and correlating performance testing metrics with other monitored metrics in Dynatrace.
+With the [Dynatrace k6 extension](https://github.com/Dynatrace/xk6-output-dynatrace),
+you can send visualize and correlate performance testing metrics with the other metrics that you monitor in Dynatrace.
 
 ## Build the k6 version
 
 <InstallationInstructions extensionUrl="github.com/Dynatrace/xk6-output-dynatrace"/>
 
 ## Run the test
 
-Create a Dynatrace API token to send the data. 
+Create a Dynatrace API token to send the data.
 
 <Blockquote mod="attention">
-The Dynatrace API Token must have the scope name "metrics.ingest" (scope type "API v2").
-</Blockquote> 
+The Dynatrace API Token must have the scope name "metrics.ingest" (scope type `API v2`).
+</Blockquote>
 
 You can use the Dynatrace UI:
 
@@ -38,20 +39,20 @@ export K6_DYNATRACE_APITOKEN=<Dynatrace API token>
 ./k6 run script.js -o output-dynatrace
 ```
 
-You can now check the metrics in your Dynatrace environment, filtering for `k6`:
+Check the metrics in your Dynatrace environment, filtering for `k6`:
 
 ![Dynatrace Test result](./images/Dynatrace/dynatrace-k6-metrics.png)
 
 ![Dynatrace Test result](./images/Dynatrace/dynatrace-k6-test-result.png)
 
 ### Options
 
-When streaming the k6 results to Dynatrace, you can configure the Dynatrace options below:
+When streaming the k6 results to Dynatrace, you can configure the following Dynatrace options:
 
 | Name                                     | Value                                                                                                       |
 | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
 | `K6_DYNATRACE_APITOKEN`                  | Dynatrace API token to write the metrics. The token must have the scope `metrics.ingest API v2`.  |
 | `K6_DYNATRACE_FLUSH_PERIOD`              | Define how often metrics are sent to Dynatrace. The default value is 1 second.  |
 | `K6_DYNATRACE_URL`                       | Dynatrace URL. The default value is `https://dynatrace.live.com`.  |
 | `K6_DYNATRACE_INSECURE_SKIP_TLS_VERIFY`  | If `true`, the HTTP client kips TLS verification on the endpoint. The default value is `true`. |
-| `K6_DYNATRACE_HEADER`                    | Pair of key/value headers to add to Dynatrace requests. |
+| `K6_DYNATRACE_HEADER`                    | Pair of key/value headers to add to Dynatrace requests. |

src/data/markdown/translated-guides/en/03 Results output/200 Real-time/00 Elasticsearch.md

@@ -12,9 +12,9 @@ Using the [Elasticsearch k6 extension](https://github.com/elastic/xk6-output-ela
 
 ## Run the test
 
-Check that the Elasticsearch instance which will store the k6 metrics is running. 
+Check that the Elasticsearch instance to store the k6 metrics is running.
 
-If you are running on Elasticsearch cloud, use the previous k6 binary and run the test passing the cloud credentials as follows:
+If you're running on Elasticsearch cloud, use the previous k6 binary and run the test passing the cloud credentials as follows:
 
 ```bash
 # export cloud configuration
@@ -26,7 +26,7 @@ export K6_ELASTICSEARCH_PASSWORD=your-password-here
 ./k6 run script.js -o output-elasticsearch
 ```
 
-k6 runs the test script and sends the metrics in real-time to Elasticsearch. 
+k6 runs the test script and sends the metrics in real-time to Elasticsearch.
 
 You can also send the metrics to a local Elasticsearch cluster:
 
@@ -39,10 +39,11 @@ export K6_ELASTICSEARCH_URL=http://localhost:9200
 ```
 
 <Blockquote mod="attention">
-Security and self-signed certificates for non-cloud clusters are not yet supported
+Security and self-signed certificates for non-cloud clusters are not yet supported.
 </Blockquote>
 
-You can now connect to Elasticsearch and query the [k6 metrics](/using-k6/metrics/) stored in the `k6-metrics` index. The example below uses an unsecured local Elasticsearch version `7.17.9`:
+You can now connect to Elasticsearch and query the [k6 metrics](/using-k6/metrics/) stored in the `k6-metrics` index.
+The following example uses an unsecured local Elasticsearch, version `7.17.9`:
 
 ```bash
 curl -XGET 'http://localhost:9200/k6-metrics/_search?pretty' -H 'Content-Type: application/json' -d'
@@ -73,4 +74,3 @@ Here is the full list of options that can be configured and passed to the extens
 | `K6_ELASTICSEARCH_URL`                     | Elasticsearch URL.  |
 | `K6_ELASTICSEARCH_USER`                     | Elasticsearch username.  |
 | `K6_ELASTICSEARCH_PASSWORD`                     | Elasticsearch password.  |
-