Update Getting started topics for style, syntax, layout, spacing (#5909)

* Fix spelling mistake

* Fix some text that was removed

* Update variable syntax in setp topics

* Update variable syntax semantic breaks spelling

* Refactoring cleanup spelling syntax

* Refactor Otel topic cleanup spelling syntax

* Refactoring layout spelling syntax spacing

* Fix some bad links

* Correct link syntax

* Cleanup variable references

* Cleanup language and spelling

* Minor corrections spelling and layout

* Fix bad syntax in caution

* Apply suggestions from code review

Co-authored-by: Paulin Todev <paulin.todev@gmail.com>

* Small tweaks from code review

---------

Co-authored-by: Paulin Todev <paulin.todev@gmail.com>

docs/sources/flow/config-language/expressions/types_and_values.md

@@ -91,7 +91,7 @@ The supported escape sequences are as follows:
 
 ## Raw strings
 
-Raw strings are represented by sequences of Unicode characters surrounded by backticks ``` `` ```. 
+Raw strings are represented by sequences of Unicode characters surrounded by backticks ``` `` ```.
 Raw strings do not support any escape sequences:
 
 ```river
@@ -102,7 +102,7 @@ Within the backticks, any character may appear except a backtick. A backtick
 can be included by concatenating a double quoted string that contains a
 backtick using `+`.
 
-A multiline raw string will be interpretted exactly as written:
+A multiline raw string is interpreted exactly as written:
 
 ```river
 `Hello,

docs/sources/flow/getting-started/configure-agent-clustering.md

@@ -13,32 +13,26 @@ weight: 400
 
 # Configure {{< param "PRODUCT_NAME" >}} clustering in an existing installation
 
-You can configure {{< param "PRODUCT_NAME" >}} to run with [clustering][] so that
-individual {{< param "PRODUCT_ROOT_NAME" >}}s can work together for workload distribution and high
-availability.
+You can configure {{< param "PRODUCT_NAME" >}} to run with [clustering][] so that individual {{< param "PRODUCT_ROOT_NAME" >}}s can work together for workload distribution and high availability.
 
-
-> **Note:** Clustering is a [beta][] feature. Beta features are subject to breaking changes and may be
-> replaced with equivalent functionality that covers the same use case.
+> **Note:** Clustering is a [beta][] feature. Beta features are subject to breaking
+> changes and may be replaced with equivalent functionality that covers the same use case.
 
 This topic describes how to add clustering to an existing installation.
 
 ## Configure {{< param "PRODUCT_NAME" >}} clustering with Helm Chart
 
-This section guides you through enabling clustering when {{< param "PRODUCT_NAME" >}} is
-installed on Kubernetes using the {{< param "PRODUCT_ROOT_NAME" >}} [Helm chart][install-helm].
+This section guides you through enabling clustering when {{< param "PRODUCT_NAME" >}} is installed on Kubernetes using the {{< param "PRODUCT_ROOT_NAME" >}} [Helm chart][install-helm].
 
 ### Before you begin
 
-- Ensure that your `values.yaml` file has `controller.type` set to
-  `statefulset`.
+- Ensure that your `values.yaml` file has `controller.type` set to `statefulset`.
 
 ### Steps
 
 To configure clustering:
 
-1. Amend your existing values.yaml file to add `clustering.enabled=true` inside
-   of the `agent` block:
+1. Amend your existing `values.yaml` file to add `clustering.enabled=true` inside the `agent` block.
 
    ```yaml
    agent:
@@ -49,17 +43,18 @@ To configure clustering:
 1. Upgrade your installation to use the new `values.yaml` file:
 
    ```bash
-   helm upgrade RELEASE_NAME -f values.yaml
+   helm upgrade <RELEASE_NAME> -f values.yaml
    ```
 
-   Replace `RELEASE_NAME` with the name of the installation you chose when you
-   installed the Helm chart.
+   Replace the following:
+
+   - _`<RELEASE_NAME>`_: The name of the installation you chose when you installed the Helm chart.
 
 1. Use the {{< param "PRODUCT_NAME" >}} [UI][] to verify the cluster status:
 
    1. Click **Clustering** in the navigation bar.
 
-   2. Ensure that all expected nodes appear in the resulting table.
+   1. Ensure that all expected nodes appear in the resulting table.
 
 {{% docs/reference %}}
 [clustering]: "/docs/agent/ -> /docs/agent/<AGENT_VERSION>/flow/concepts/clustering.md"

docs/sources/flow/getting-started/distribute-prometheus-scrape-load.md

@@ -13,10 +13,8 @@ weight: 500
 
 # Distribute Prometheus metrics scrape load
 
-A good predictor for the size of an {{< param "PRODUCT_NAME" >}} deployment is the number of
-Prometheus targets each {{< param "PRODUCT_ROOT_NAME" >}} scrapes. [Clustering][] with target
-auto-distribution allows a fleet of {{< param "PRODUCT_ROOT_NAME" >}}s to work together to dynamically
-distribute their scrape load, providing high-availability.
+A good predictor for the size of an {{< param "PRODUCT_NAME" >}} deployment is the number of Prometheus targets each {{< param "PRODUCT_ROOT_NAME" >}} scrapes.
+[Clustering][] with target auto-distribution allows a fleet of {{< param "PRODUCT_ROOT_NAME" >}}s to work together to dynamically distribute their scrape load, providing high-availability.
 
 > **Note:** Clustering is a [beta][] feature. Beta features are subject to breaking
 > changes and may be replaced with equivalent functionality that covers the same use case.
@@ -32,8 +30,7 @@ distribute their scrape load, providing high-availability.
 
 To distribute Prometheus metrics scrape load with clustering:
 
-1. Add the following block to all `prometheus.scrape` components which
-   should use auto-distribution:
+1. Add the following block to all `prometheus.scrape` components, which should use auto-distribution:
 
    ```river
    clustering {
@@ -45,8 +42,7 @@ To distribute Prometheus metrics scrape load with clustering:
 
 1. Validate that auto-distribution is functioning:
 
-   1. Using the {{< param "PRODUCT_ROOT_NAME" >}} [UI][] on each {{< param "PRODUCT_ROOT_NAME" >}}, navigate to the details page for one of
-      the `prometheus.scrape` components you modified.
+   1. Using the {{< param "PRODUCT_ROOT_NAME" >}} [UI][] on each {{< param "PRODUCT_ROOT_NAME" >}}, navigate to the details page for one of the `prometheus.scrape` components you modified.
 
    1. Compare the Debug Info sections between two different {{< param "PRODUCT_ROOT_NAME" >}} to ensure that they're not scraping the same sets of targets.