diff --git a/docs/sources/concepts/configuration-syntax/components.md b/docs/sources/concepts/configuration-syntax/components.md
index d33a4a071f..5114e4c570 100644
--- a/docs/sources/concepts/configuration-syntax/components.md
+++ b/docs/sources/concepts/configuration-syntax/components.md
@@ -1,11 +1,11 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/concepts/configuration-syntax/components/
 description: Learn about the components configuration language
-title: Components configuration language
+title: Components configuration
 weight: 300
 ---
 
-# Components configuration language
+# Components configuration
 
 Components are the defining feature of {{< param "PRODUCT_NAME" >}}.
 Components are small, reusable pieces of business logic that perform a single task like retrieving secrets or collecting Prometheus metrics, and you can wire them together to form programmable pipelines of telemetry data.
diff --git a/docs/sources/introduction/_index.md b/docs/sources/introduction/_index.md
index 5c21b5434e..ba31aa20d0 100644
--- a/docs/sources/introduction/_index.md
+++ b/docs/sources/introduction/_index.md
@@ -75,9 +75,9 @@ binaries and images with BoringCrypto enabled. Builds and Docker images for Linu
 
 * [Install][] {{< param "PRODUCT_NAME" >}}.
 * Learn about the core [Concepts][] of {{< param "PRODUCT_NAME" >}}.
-* Follow the [Tutorials][] for hands-on learning of {{< param "PRODUCT_NAME" >}}.
+* Follow the [Tutorials][] for hands-on learning about {{< param "PRODUCT_NAME" >}}.
 * Consult the [Tasks][] instructions to accomplish common objectives with {{< param "PRODUCT_NAME" >}}.
-* Check out the [Reference][] documentation to find specific information you might be looking for.
+* Check out the [Reference][] documentation to find information about the Alloy components, configuration blocks, and command line tools.
 
 [OpenTelemetry]: https://opentelemetry.io/ecosystem/distributions/
 [Install]: ../get-started/install/
diff --git a/docs/sources/reference/components/discovery.azure.md b/docs/sources/reference/components/discovery.azure.md
index 985c295baf..d558f902f3 100644
--- a/docs/sources/reference/components/discovery.azure.md
+++ b/docs/sources/reference/components/discovery.azure.md
@@ -13,7 +13,7 @@ title: discovery.azure
 ## Usage
 
 ```alloy
-discovery.azure "LABEL" {
+discovery.azure "<LABEL>" {
 }
 ```
 
@@ -64,9 +64,9 @@ Name            | Type     | Description          | Default | Required
 ### managed_identity block
 The `managed_identity` block configures Managed Identity authentication for the Azure API.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`client_id` | `string` | Managed Identity client ID. | | yes
+Name        | Type     | Description                 | Default | Required
+------------|----------|-----------------------------|---------|---------
+`client_id` | `string` | Managed Identity client ID. |         | yes
 
 ### tls_config block
 
@@ -77,7 +77,7 @@ Name | Type | Description | Default | Required
 The following fields are exported and can be referenced by other components:
 
 Name      | Type                | Description
---------- | ------------------- | -----------
+----------|---------------------|--------------------------------------------------
 `targets` | `list(map(string))` | The set of targets discovered from the Azure API.
 
 Each target includes the following labels:
@@ -100,28 +100,27 @@ Each discovered VM maps to a single target. The `__address__` label is set to th
 
 ## Component health
 
-`discovery.azure` is only reported as unhealthy when given an invalid
-configuration. In those cases, exported fields retain their last healthy
-values.
+`discovery.azure` is only reported as unhealthy when given an invalid configuration.
+In those cases, exported fields retain their last healthy values.
 
 ## Debug information
 
-`discovery.azure` does not expose any component-specific debug information.
+`discovery.azure` doesn't expose any component-specific debug information.
 
 ## Debug metrics
 
-`discovery.azure` does not expose any component-specific debug metrics.
+`discovery.azure` doesn't expose any component-specific debug metrics.
 
 ## Example
 
 ```alloy
 discovery.azure "example" {
   port = 80
-  subscription_id = AZURE_SUBSCRIPTION_ID
+  subscription_id = <AZURE_SUBSCRIPTION_ID>
   oauth {
-      client_id = AZURE_CLIENT_ID
-      client_secret = AZURE_CLIENT_SECRET
-      tenant_id = AZURE_TENANT_ID
+      client_id = <AZURE_CLIENT_ID>
+      client_secret = <AZURE_CLIENT_SECRET>
+      tenant_id = <AZURE_TENANT_ID>
   }
 }
 
@@ -132,23 +131,24 @@ prometheus.scrape "demo" {
 
 prometheus.remote_write "demo" {
   endpoint {
-    url = PROMETHEUS_REMOTE_WRITE_URL
+    url = <PROMETHEUS_REMOTE_WRITE_URL>
 
     basic_auth {
-      username = USERNAME
-      password = PASSWORD
+      username = <USERNAME>
+      password = <PASSWORD>
     }
   }
 }
 ```
+
 Replace the following:
-  - `AZURE_SUBSCRIPTION_ID`: Your Azure subscription ID.
-  - `AZURE_CLIENT_ID`: Your Azure client ID.
-  - `AZURE_CLIENT_SECRET`: Your Azure client secret.
-  - `AZURE_TENANT_ID`: Your Azure tenant ID.
-  - `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-  - `USERNAME`: The username to use for authentication to the remote_write API.
-  - `PASSWORD`: The password to use for authentication to the remote_write API.
+  - _`<AZURE_SUBSCRIPTION_ID>`_: Your Azure subscription ID.
+  - _`<AZURE_CLIENT_ID>`_: Your Azure client ID.
+  - _`<AZURE_CLIENT_SECRET>`_: Your Azure client secret.
+  - _`<AZURE_TENANT_ID>`_: Your Azure tenant ID.
+  - _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+  - _`<USERNAME>`_: The username to use for authentication to the remote_write API.
+  - _`<PASSWORD>`_: The password to use for authentication to the remote_write API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery.consul.md b/docs/sources/reference/components/discovery.consul.md
index 1cf447e8e6..8244542a09 100644
--- a/docs/sources/reference/components/discovery.consul.md
+++ b/docs/sources/reference/components/discovery.consul.md
@@ -153,19 +153,19 @@ prometheus.scrape "demo" {
 
 prometheus.remote_write "demo" {
   endpoint {
-    url = PROMETHEUS_REMOTE_WRITE_URL
+    url = <PROMETHEUS_REMOTE_WRITE_URL>
 
     basic_auth {
-      username = USERNAME
-      password = PASSWORD
+      username = <USERNAME>
+      password = <PASSWORD>
     }
   }
 }
 ```
 Replace the following:
-  - `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-  - `USERNAME`: The username to use for authentication to the remote_write API.
-  - `PASSWORD`: The password to use for authentication to the remote_write API.
+  - _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+  - _`<USERNAME>`_: The username to use for authentication to the remote_write API.
+  - _`<PASSWORD>`_: The password to use for authentication to the remote_write API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery.consulagent.md b/docs/sources/reference/components/discovery.consulagent.md
index 659e8e50b3..1f70c8faf7 100644
--- a/docs/sources/reference/components/discovery.consulagent.md
+++ b/docs/sources/reference/components/discovery.consulagent.md
@@ -24,18 +24,18 @@ discovery.consulagent "LABEL" {
 
 The following arguments are supported:
 
-| Name               | Type           | Description                                                                                                                               | Default          | Required |
-| ------------------ | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | -------- |
-| `server`           | `string`       | Host and port of the Consul Agent API.                                                                                                    | `localhost:8500` | no       |
-| `token`            | `secret`       | Secret token used to access the Consul Agent API.                                                                                         |                  | no       |
-| `datacenter`       | `string`       | Datacenter in which the Consul Agent is configured to run. If not provided, the datacenter will be retrieved from the local Consul Agent. |                  | no       |
-| `tag_separator`    | `string`       | The string by which Consul tags are joined into the tag label.                                                                            | `,`              | no       |
-| `scheme`           | `string`       | The scheme to use when talking to the Consul Agent.                                                                                       | `http`           | no       |
-| `username`         | `string`       | The username to use.                                                                                                                      |                  | no       |
-| `password`         | `secret`       | The password to use.                                                                                                                      |                  | no       |
-| `services`         | `list(string)` | A list of services for which targets are retrieved. If omitted, all services are scraped.                                                 |                  | no       |
-| `tags`             | `list(string)` | An optional list of tags used to filter nodes for a given service. Services must contain all tags in the list.                            |                  | no       |
-| `refresh_interval` | `duration`     | Frequency to refresh list of containers.                                                                                                  | `"30s"`          | no       |
+| Name               | Type           | Description                                                                                                                          | Default          | Required |
+|--------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------|------------------|----------|
+| `server`           | `string`       | Host and port of the Consul Agent API.                                                                                               | `localhost:8500` | no       |
+| `token`            | `secret`       | Secret token used to access the Consul Agent API.                                                                                    |                  | no       |
+| `datacenter`       | `string`       | Datacenter in which the Consul Agent is configured to run. If not provided, the datacenter is retrieved from the local Consul Agent. |                  | no       |
+| `tag_separator`    | `string`       | The string by which Consul tags are joined into the tag label.                                                                       | `,`              | no       |
+| `scheme`           | `string`       | The scheme to use when talking to the Consul Agent.                                                                                  | `http`           | no       |
+| `username`         | `string`       | The username to use.                                                                                                                 |                  | no       |
+| `password`         | `secret`       | The password to use.                                                                                                                 |                  | no       |
+| `services`         | `list(string)` | A list of services for which targets are retrieved. If omitted, all services are scraped.                                            |                  | no       |
+| `tags`             | `list(string)` | An optional list of tags used to filter nodes for a given service. Services must contain all tags in the list.                       |                  | no       |
+| `refresh_interval` | `duration`     | Frequency to refresh list of containers.                                                                                             | `"30s"`          | no       |
 
 ## Blocks
 
@@ -62,28 +62,27 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-- `__meta_consulagent_address`: the address of the target.
-- `__meta_consulagent_dc`: the datacenter name for the target.
-- `__meta_consulagent_health`: the health status of the service.
-- `__meta_consulagent_metadata_<key>`: each node metadata key value of the target.
-- `__meta_consulagent_node`: the node name defined for the target.
-- `__meta_consulagent_service`: the name of the service the target belongs to.
-- `__meta_consulagent_service_address`: the service address of the target.
-- `__meta_consulagent_service_id`: the service ID of the target.
-- `__meta_consulagent_service_metadata_<key>`: each service metadata key value of the target.
-- `__meta_consulagent_service_port`: the service port of the target.
-- `__meta_consulagent_tagged_address_<key>`: each node tagged address key value of the target.
-- `__meta_consulagent_tags`: the list of tags of the target joined by the tag separator.
+- `__meta_consulagent_address`: The address of the target.
+- `__meta_consulagent_dc`: The datacenter name for the target.
+- `__meta_consulagent_health`: The health status of the service.
+- `__meta_consulagent_metadata_<key>`: Each node metadata key value of the target.
+- `__meta_consulagent_node`: The node name defined for the target.
+- `__meta_consulagent_service`: The name of the service the target belongs to.
+- `__meta_consulagent_service_address`: The service address of the target.
+- `__meta_consulagent_service_id`: The service ID of the target.
+- `__meta_consulagent_service_metadata_<key>`: Each service metadata key value of the target.
+- `__meta_consulagent_service_port`: The service port of the target.
+- `__meta_consulagent_tagged_address_<key>`: Each node tagged address key value of the target.
+- `__meta_consulagent_tags`: The list of tags of the target joined by the tag separator.
 
 ## Component health
 
-`discovery.consulagent` is only reported as unhealthy when given an invalid
-configuration. In those cases, exported fields retain their last healthy
-values.
+`discovery.consulagent` is only reported as unhealthy when given an invalid configuration.
+In those cases, exported fields retain their last healthy values.
 
 ## Debug information
 
-`discovery.consulagent` does not expose any component-specific debug information.
+`discovery.consulagent` doesn't expose any component-specific debug information.
 
 ## Debug metrics
 
@@ -111,11 +110,11 @@ prometheus.scrape "demo" {
 
 prometheus.remote_write "demo" {
   endpoint {
-    url = PROMETHEUS_REMOTE_WRITE_URL
+    url = <PROMETHEUS_REMOTE_WRITE_URL>
 
     basic_auth {
-      username = USERNAME
-      password = PASSWORD
+      username = <USERNAME>
+      password = <PASSWORD>
     }
   }
 }
@@ -123,9 +122,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-- `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-- `USERNAME`: The username to use for authentication to the remote_write API.
-- `PASSWORD`: The password to use for authentication to the remote_write API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the remote_write API.
+- _`<PASSWORD>`_: The password to use for authentication to the remote_write API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery.digitalocean.md b/docs/sources/reference/components/discovery.digitalocean.md
index d7f83700e3..707d48081b 100644
--- a/docs/sources/reference/components/discovery.digitalocean.md
+++ b/docs/sources/reference/components/discovery.digitalocean.md
@@ -46,7 +46,7 @@ Exactly one of the [`bearer_token`](#arguments) and [`bearer_token_file`](#argum
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
 ## Blocks
-The `discovery.digitalocean` component does not support any blocks, and is configured fully through arguments.
+The `discovery.digitalocean` component doesn't support any blocks, and is configured fully through arguments.
 
 
 ## Exported fields
@@ -83,11 +83,11 @@ values.
 
 ## Debug information
 
-`discovery.digitalocean` does not expose any component-specific debug information.
+`discovery.digitalocean` doesn't expose any component-specific debug information.
 
 ## Debug metrics
 
-`discovery.digitalocean` does not expose any component-specific debug metrics.
+`discovery.digitalocean` doesn't expose any component-specific debug metrics.
 
 ## Example
 
@@ -106,19 +106,19 @@ prometheus.scrape "demo" {
 
 prometheus.remote_write "demo" {
   endpoint {
-    url = PROMETHEUS_REMOTE_WRITE_URL
+    url = <PROMETHEUS_REMOTE_WRITE_URL>
 
     basic_auth {
-      username = USERNAME
-      password = PASSWORD
+      username = <USERNAME>
+      password = <PASSWORD>
     }
   }
 }
 ```
 Replace the following:
-  - `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-  - `USERNAME`: The username to use for authentication to the remote_write API.
-  - `PASSWORD`: The password to use for authentication to the remote_write API.
+  - _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+  - _`<USERNAME>`_: The username to use for authentication to the remote_write API.
+  - _`<PASSWORD>`_: The password to use for authentication to the remote_write API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/tasks/migrate/_index.md b/docs/sources/tasks/migrate/_index.md
index 8520edc74c..5af3451bb6 100644
--- a/docs/sources/tasks/migrate/_index.md
+++ b/docs/sources/tasks/migrate/_index.md
@@ -6,7 +6,7 @@ title: Migrate to Grafana Alloy
 weight: 100
 ---
 
-# HMigrate to {{% param "FULL_PRODUCT_NAME" %}}
+# Migrate to {{% param "FULL_PRODUCT_NAME" %}}
 
 This section details how to migrate to {{< param "PRODUCT_NAME" >}} from other common solutions.
 
diff --git a/docs/sources/tasks/migrate/from-operator.md b/docs/sources/tasks/migrate/from-operator.md
index a181c735d9..7048e42781 100644
--- a/docs/sources/tasks/migrate/from-operator.md
+++ b/docs/sources/tasks/migrate/from-operator.md
@@ -31,7 +31,7 @@ You can migrate from Grafana Agent Operator to {{< param "PRODUCT_NAME" >}}.
       create: false
     ```
 
-    This configuration deploys {{< param "PRODUCT_NAME" >}} as a `StatefulSet` using the built-in [clustering][] functionality to allow distributing scrapes across all {{< param "PRODUCT_NAME" >}} Pods.
+    This configuration deploys {{< param "PRODUCT_NAME" >}} as a `StatefulSet` using the built-in [clustering][] functionality to allow distributing scrapes across all {{< param "PRODUCT_NAME" >}} pods.
 
     This is one of many deployment possible modes. For example, you may want to use a `DaemonSet` to collect host-level logs or metrics.
     See the {{< param "PRODUCT_NAME" >}} [deployment guide][] for more details about different topologies.
@@ -142,10 +142,10 @@ alloy:
     varlog: true
 ```
 
-This command installs a release named `grafana-agent-logs` in the `monitoring` namespace:
+This command installs a release named `alloy-logs` in the `monitoring` namespace:
 
 ```
-helm upgrade grafana-agent-logs grafana/grafana-agent -i -n monitoring -f values-logs.yaml --set-file agent.configMap.content=agent-logs.alloy
+helm upgrade alloy-logs grafana/alloy -i -n monitoring -f values-logs.yaml --set-file alloy.configMap.content=config-logs.alloy
 ```
 
 This simple configuration scrapes logs for every Pod on each node:
@@ -268,7 +268,7 @@ The logging subsystem is very powerful and has many options for processing logs.
 ## Integrations
 
 The `Integration` CRD isn't supported with {{< param "PRODUCT_NAME" >}}.
-However, all Grafana Agent Static integrations have an equivalent component in the [`prometheus.exporter`][prometheus.exporter] namespace.
+However, all Grafana Agent Static mode integrations have an equivalent component in the [`prometheus.exporter`][prometheus.exporter] namespace.
 The [reference documentation][component documentation] should help convert those integrations to their {{< param "PRODUCT_NAME" >}} equivalent.
 
 <!-- ToDo: Validate path -->
diff --git a/docs/sources/tutorials/first-components-and-stdlib/index.md b/docs/sources/tutorials/first-components-and-stdlib/index.md
index cd262935e3..afd5aa4d36 100644
--- a/docs/sources/tutorials/first-components-and-stdlib/index.md
+++ b/docs/sources/tutorials/first-components-and-stdlib/index.md
@@ -1,7 +1,7 @@
 ---
 canonical: https://grafana.com/docs/alloy/latest/tutorials/first-components-and-stdlib/
 description: Learn about the basics of the {{< param "PRODUCT_NAME" >}} configuration syntax
-title: First components and introducing the standard library
+title: First components and the standard library
 weight: 20
 ---
 
@@ -10,12 +10,16 @@ weight: 20
 This tutorial covers the basics of the {{< param "PRODUCT_NAME" >}} configuration syntax and the standard library.
 It introduces a basic pipeline that collects metrics from the host and sends them to Prometheus.
 
-## {{< param "PRODUCT_NAME" >}} configuration syntax basics
+## Prerequisites
+
+Set up a local Grafana instance as described in [Get started with {{< param "FULL_PRODUCT_NAME" >}}][get started]
 
-**Recommended reading**
+### Recommended reading
 
 - [{{< param "PRODUCT_NAME" >}} configuration syntax][Configuration syntax]
 
+## {{< param "PRODUCT_NAME" >}} configuration syntax basics
+
 An {{< param "PRODUCT_NAME" >}} configuration file is comprised of three things:
 
 1. **Attributes**
@@ -60,15 +64,17 @@ Comments in {{< param "PRODUCT_NAME" >}} syntax are prefixed with `//` and are s
 
 ## Components
 
-**Recommended reading**
+Components are the building blocks of an {{< param "PRODUCT_NAME" >}} configuration. They are configured and linked to create pipelines that collect, process, and output your telemetry data. Components are configured with `Arguments` and have `Exports` that may be referenced by other components.
+
+### Recommended reading
 
 - [Components][]
 - [Components configuration language][]
 - [Component controller][]
 
-Components are the building blocks of an {{< param "PRODUCT_NAME" >}} configuration. They are configured and linked to create pipelines that collect, process, and output your telemetry data. Components are configured with `Arguments` and have `Exports` that may be referenced by other components.
+### An example pipeline
 
-Let's look at a simple example pipeline:
+Look at the following simple pipeline:
 
 ```alloy
 local.file "example" {
@@ -112,16 +118,20 @@ The `local.file` component's label is set to `"example"`, so the fully qualified
 The `prometheus.remote_write` component's label is set to `"local_prom"`, so the fully qualified name of the component is `prometheus.remote_write.local_prom`.
 {{< /admonition >}}
 
-This example pipeline still doesn't do anything, so let's add some more components to it.
+This example pipeline still doesn't do anything, so its time to add some more components to it.
 
 ## Shipping your first metrics
 
-**Recommended reading**
+Now that you have a simple pipeline, you can ship your first metrics.
+
+### Recommended reading
 
 - Optional: [prometheus.exporter.unix][]
 - Optional: [prometheus.scrape][]
 - Optional: [prometheus.remote_write][]
 
+### Modify your pipeline and scrape the metrics
+
 Make a simple pipeline with a `prometheus.exporter.unix` component, a `prometheus.scrape` component to scrape it, and a `prometheus.remote_write` component to send the scraped metrics to Prometheus.
 
 ```alloy
@@ -146,7 +156,7 @@ prometheus.remote_write "local_prom" {
 }
 ```
 
-Run {{< param "PRODUCT_NAME" >}} with:
+Run {{< param "PRODUCT_NAME" >}} with the following command:
 
 ```bash
 <BINARY_FILE_PATH> run config.alloy
@@ -164,7 +174,7 @@ Try querying for `node_memory_Active_bytes` to see the active memory of your hos
 <img src="/media/docs/alloy/screenshot-memory-usage.png" alt="Screenshot of node_memory_Active_bytes query in Grafana" />
 </p>
 
-## Visualizing the relationship between components
+## Visualize the relationship between components
 
 The following diagram is an example pipeline:
 
@@ -172,26 +182,28 @@ The following diagram is an example pipeline:
 <img src="/media/docs/agent/diagram-flow-by-example-full-0.svg" alt="Example pipeline with a prometheus.scrape, prometheus.exporter.unix, and prometheus.remote_write components" width="400" />
 </p>
 
-The preceding configuration defines three components:
+Your pipeline configuration defines three components:
 
 - `prometheus.scrape` - A component that scrapes metrics from components that export targets.
 - `prometheus.exporter.unix` - A component that exports metrics from the host, built around [node_exporter][].
 - `prometheus.remote_write` - A component that sends metrics to a Prometheus remote-write compatible endpoint.
 
 The `prometheus.scrape` component references the `prometheus.exporter.unix` component's targets export, which is a list of scrape targets.
-The `prometheus.scrape` component then forwards the scraped metrics to the `prometheus.remote_write` component.
+The `prometheus.scrape` component forwards the scraped metrics to the `prometheus.remote_write` component.
 
 One rule is that components can't form a cycle.
 This means that a component can't reference itself directly or indirectly.
 This is to prevent infinite loops from forming in the pipeline.
 
-## Exercise for the reader
+## Exercise
 
-**Recommended Reading**
+The following exercise guides you through modifying your pipeline to scrape metrics from Redis.
+
+### Recommended Reading
 
 - Optional: [prometheus.exporter.redis][]
 
-Let's start a container running Redis and configure {{< param "PRODUCT_NAME" >}} to scrape metrics from it.
+Start a container running Redis and configure {{< param "PRODUCT_NAME" >}} to scrape the metrics.
 
 ```bash
 docker container run -d --name alloy-redis -p 6379:6379 --rm redis
@@ -206,13 +218,13 @@ To give a visual hint, you want to create a pipeline that looks like this:
 <img src="/media/docs/agent/diagram-flow-by-example-exercise-0.svg" alt="Exercise pipeline, with a scrape, unix_exporter, redis_exporter, and remote_write component" width="600" />
 </p>
 
-{{< admonition type="note" >}}
-You may find the [concat][] standard library function useful.
+{{< admonition type="tip" >}}
+Refer to the [concat][] standard library function for information about combining lists of values into a single list.
 
 [concat]: ../../reference/stdlib/concat/
 {{< /admonition >}}
 
-You can run {{< param "PRODUCT_NAME" >}} with the new configuration file by running:
+You can run {{< param "PRODUCT_NAME" >}} with the new configuration file with the following command:
 
 ```bash
 <BINARY_FILE_PATH> run config.alloy
@@ -282,9 +294,10 @@ If you look in the directory, do you notice anything interesting? The directory
 If you'd like to store the data elsewhere, you can specify a different directory by supplying the `--storage.path` flag to {{< param "PRODUCT_NAME" >}}'s run command, for example, `<BINARY_FILE_PATH> run config.alloy --storage.path /etc/alloy`. Replace _`<BINARY_FILE_PATH>`_ with the path to the {{< param "PRODUCT_NAME" >}} binary.
 Generally, you can use a persistent directory for this, as some components may use the data stored in this directory to perform their function.
 
-In the next tutorial, you will look at how to configure {{< param "PRODUCT_NAME" >}} to collect logs from a file and send them to Loki.
-You will also look at using different components to process metrics and logs before sending them.
+In the next tutorial, you learn how to configure {{< param "PRODUCT_NAME" >}} to collect logs from a file and send them to Loki.
+You also learn how to use different components to process metrics and logs.
 
+[get started]: ../get-started/#set-up-a-local-grafana-instance
 [Configuration syntax]: ../../concepts/configuration-syntax/
 [Standard library documentation]: ../../reference/stdlib/
 [node_exporter]: https://github.com/prometheus/node_exporter
diff --git a/docs/sources/tutorials/get-started.md b/docs/sources/tutorials/get-started.md
index a9459b37ed..afeacfc96e 100644
--- a/docs/sources/tutorials/get-started.md
+++ b/docs/sources/tutorials/get-started.md
@@ -5,23 +5,24 @@ title: Get started
 weight: 10
 ---
 
-## Who is this for?
+## Get started with {{% param "PRODUCT_NAME" %}}
 
-This set of tutorials contains a collection of examples that build on each other to demonstrate how to configure and use [{{< param "PRODUCT_NAME" >}}][alloy]. It assumes you have a basic understanding of what {{< param "PRODUCT_NAME" >}} is and telemetry collection in general. It also assumes a base level of familiarity with Prometheus and PromQL, Loki and LogQL, and basic Grafana navigation. It assumes no knowledge of the {{< param "PRODUCT_NAME" >}} configuration syntax concepts.
+This set of tutorials contains a collection of examples that build on each other to demonstrate how to configure and use [{{< param "PRODUCT_NAME" >}}][alloy].
+To follow these tutorials, you need to have a basic understanding of what {{< param "PRODUCT_NAME" >}} is and telemetry collection in general.
+You should also be familiar with with Prometheus and PromQL, Loki and LogQL, and basic Grafana navigation.
+You don't need to know about the {{< param "PRODUCT_NAME" >}} [configuration syntax][configuration] concepts.
 
-## What is {{% param "PRODUCT_NAME" %}}?
+## Prerequisites
 
-{{< param "PRODUCT_NAME" >}} uses a [configuration syntax][configuration] that allows you to define a pipeline of telemetry collection, processing, and output.
-
-## What do I need to get started?
-
-You will need a Linux or Unix environment with Docker installed. The examples are designed to be run on a single host so that you can run them on your laptop or in a VM. You are encouraged to follow along with the examples using a `config.alloy` file and experiment with the examples yourself.
+The tutorials require a Linux or Unix environment with Docker installed.
+The examples run on a single host so that you can run them on your laptop or in a Virtual Machine.
+You are encouraged to try the examples using a `config.alloy` file and experiment with the examples yourself.
 
 To run the examples, you should have an {{< param "PRODUCT_NAME" >}} binary available. You can follow the instructions on how to [Install {{< param "PRODUCT_NAME" >}} as a Standalone Binary][install] to get a binary.
 
-## How should I follow along?
+## Set up a local Grafana instance
 
-You can use this Docker Compose file to set up a local Grafana instance alongside Loki and Prometheus pre-configured as datasources. The examples are designed to be run locally, so you can follow along and experiment with them yourself.
+You can use the following Docker Compose file to set up a local Grafana instance alongside Loki and Prometheus which are pre-configured as datasources. You can run and experiment with the examples on your local system.
 
 ```yaml
 version: '3'
@@ -77,9 +78,9 @@ services:
 
 After running `docker-compose up`, open [http://localhost:3000](http://localhost:3000) in your browser to view the Grafana UI.
 
-The tutorials are designed to be followed in order and generally build on each other. Each example explains what it does and how it works. They are designed to be run locally, so you can follow along and experiment with them yourself.
+The tutorials are designed to be followed in order and generally build on each other. Each example explains what it does and how it works.
 
-The Recommended Reading sections in each tutorial provide a list of documentation topics. To help you understand the concepts used in the example, read the recommended topics in the order given.
+The Recommended Reading sections in each tutorial provide a list of documentation topics. Read the recommended topics in the order given to help you understand the concepts used in the example.
 
 [alloy]: https://grafana.com/docs/alloy/latest/
 [configuration]: ../../concepts/configuration-syntax/
diff --git a/docs/sources/tutorials/logs-and-relabeling-basics/index.md b/docs/sources/tutorials/logs-and-relabeling-basics/index.md
index 186ae248c7..1e8e769c36 100644
--- a/docs/sources/tutorials/logs-and-relabeling-basics/index.md
+++ b/docs/sources/tutorials/logs-and-relabeling-basics/index.md
@@ -7,19 +7,25 @@ weight: 30
 
 # Logs and relabeling basics
 
-This tutorial assumes you have completed the [First components and introducing the standard library][] tutorial, or are at least familiar with the concepts of components, attributes, and expressions and how to use them.
-You will cover some basic metric relabeling, followed by how to send logs to Loki.
+This tutorial covers some basic metric relabeling, and shows you how to send logs to Loki.
+
+## Prerequisites
+
+Complete the [First components and the standard library][first] tutorial.
 
 ## Relabel metrics
 
-**Recommended reading**
+Now that you have built a basic pipeline and scraped some metrics, you can use the `prometheus.relabel` component to relabel metrics.
+
+### Recommended reading
 
 - Optional: [prometheus.relabel][]
 
-Before moving on to logs, let's look at how we can use the `prometheus.relabel` component to relabel metrics.
+### Add a `prometheus.relabel` component to your pipeline
+
 The `prometheus.relabel` component allows you to perform Prometheus relabeling on metrics and is similar to the `relabel_configs` section of a Prometheus scrape configuration.
 
-Let's add a `prometheus.relabel` component to a basic pipeline and see how to add labels.
+Add a `prometheus.relabel` component to a basic pipeline and add labels.
 
 ```alloy
 prometheus.exporter.unix "localhost" { }
@@ -52,7 +58,7 @@ prometheus.remote_write "local_prom" {
 }
 ```
 
-We have now created the following pipeline:
+You have created the following pipeline:
 
 ![Diagram of pipeline that scrapes prometheus.exporter.unix, relabels the metrics, and remote_writes them](/media/docs/agent/diagram-flow-by-example-relabel-0.svg)
 
@@ -82,16 +88,20 @@ If you would like to keep or act on these kinds of labels, use a [discovery.rela
 
 ## Send logs to Loki
 
-**Recommended reading**
+Now that you've created components and chained them together, you can collect some logs and send them to Loki.
+
+### Recommended reading
 
 - Optional: [local.file_match][]
 - Optional: [loki.source.file][]
 - Optional: [loki.write][]
 
-Now that you're comfortable creating components and chaining them together, let's collect some logs and send them to Loki.
-We will use the `local.file_match` component to perform file discovery, the `loki.source.file` to collect the logs, and the `loki.write` component to send the logs to Loki.
+### Find and collect the logs
 
-Before doing this, make sure you have a log file to scrape. You can use the `echo` command to create a file with some log content.
+You can use the `local.file_match` component to perform file discovery, the `loki.source.file` to collect the logs, and the `loki.write` component to send the logs to Loki.
+
+Before doing this, make sure you have a log file to scrape.
+You can use the `echo` command to create a file with some log content.
 
 ```bash
 mkdir -p /tmp/alloy-logs
@@ -137,15 +147,17 @@ If you delete this file, {{< param "PRODUCT_NAME" >}} starts reading from the be
 
 ## Exercise
 
-**Recommended reading**
+The following exercise guides you through adding a label to the logs, and filtering the results.
+
+### Recommended reading
 
 - [loki.relabel][]
 - [loki.process][]
 
 ### Add a Label to Logs
 
-This exercise will have two parts, building on the previous example.
-Let's start by adding an `os` label (just like the Prometheus example) to all of the logs we collect.
+This exercise has two parts, and builds on the previous example.
+Start by adding an `os` label (just like the Prometheus example) to all of the logs we collect.
 
 Modify the following snippet to add the label `os` with the value of the `os` constant.
 
@@ -166,14 +178,14 @@ loki.write "local_loki" {
 }
 ```
 
-{{< admonition type="note" >}}
+{{< admonition type="tip" >}}
 You can use the [loki.relabel][] component to relabel and add labels, just like you can with the [prometheus.relabel][] component.
 
 [loki.relabel]: ../../reference/components/loki.relabel
 [prometheus.relabel]: ../../reference/components/prometheus.relabel
 {{< /admonition >}}
 
-Once you have your completed configuration, run {{< param "PRODUCT_NAME" >}} and execute the following:
+Run {{< param "PRODUCT_NAME" >}} and execute the following:
 
 ```bash
 echo 'level=info msg="INFO: This is an info level log!"' >> /tmp/alloy-logs/log.log
@@ -182,9 +194,9 @@ echo 'level=debug msg="DEBUG: This is a debug level log!"' >> /tmp/alloy-logs/lo
 ```
 
 Navigate to [localhost:3000/explore][] and switch the Datasource to `Loki`.
-Try querying for `{filename="/tmp/alloy-logs/log.log"}` and see if you can find the new label!
+Try querying for `{filename="/tmp/alloy-logs/log.log"}` and see if you can find the new label.
 
-Now that we have added new labels, we can also filter on them. Try querying for `{os!=""}`.
+Now that you have added new labels, you can also filter on them. Try querying for `{os!=""}`.
 You should only see the lines you added in the previous step.
 
 {{< collapse title="Solution" >}}
@@ -223,23 +235,23 @@ loki.write "local_loki" {
 
 {{< admonition type="note" >}}
 This exercise is more challenging than the previous one.
-If you are having trouble, skip it and move to the next section, which will cover some of the concepts used here.
+If you are having trouble, skip it and move to the next section, which covers some of the concepts used here.
 You can always come back to this exercise later.
 {{< /admonition >}}
 
-This exercise will build on the previous one, though it's more involved.
+This exercise builds on the previous one, though it's more involved.
 
-Let's say we want to extract the `level` from the logs and add it as a label. As a starting point, look at [loki.process][].
+Assume you want to extract the `level` from the logs and add it as a label. As a starting point, look at [loki.process][].
 This component allows you to perform processing on logs, including extracting values from log contents.
 
 Try modifying your configuration from the previous section to extract the `level` from the logs and add it as a label.
 If needed, you can find a solution to the previous exercise at the end of the [previous section](#add-a-label-to-logs).
 
-{{< admonition type="note" >}}
+{{< admonition type="tip" >}}
 The `stage.logfmt` and `stage.labels` blocks for `loki.process` may be helpful.
 {{< /admonition >}}
 
-Once you have your completed configuration, run {{< param "PRODUCT_NAME" >}} and execute the following:
+Run {{< param "PRODUCT_NAME" >}} and execute the following:
 
 ```bash
 echo 'level=info msg="INFO: This is an info level log!"' >> /tmp/alloy-logs/log.log
@@ -247,7 +259,8 @@ echo 'level=warn msg="WARN: This is a warn level log!"' >> /tmp/alloy-logs/log.l
 echo 'level=debug msg="DEBUG: This is a debug level log!"' >> /tmp/alloy-logs/log.log
 ```
 
-Navigate to [localhost:3000/explore][] and switch the Datasource to `Loki`. Try querying for `{level!=""}` to see the new labels in action.
+Navigate to [localhost:3000/explore][] and switch the Datasource to `Loki`.
+Try querying for `{level!=""}` to see the new labels in action.
 
 ![Grafana Explore view of example log lines, now with the extracted 'level' label](/media/docs/agent/screenshot-flow-by-example-log-line-levels.png)
 
@@ -307,10 +320,11 @@ loki.write "local_loki" {
 
 ## Finishing up and next steps
 
-You have learned the concepts of components, attributes, and expressions. You have also seen how to use some standard library components to collect metrics and logs.
-In the next tutorial, you will learn more about how to use the `loki.process` component to extract values from logs and use them.
+You have learned the concepts of components, attributes, and expressions.
+You have also seen how to use some standard library components to collect metrics and logs.
+In the next tutorial, you learn more about how to use the `loki.process` component to extract values from logs and use them.
 
-[First components and introducing the standard library]: ../first-components-and-stdlib/
+[first]: ../first-components-and-stdlib/
 [prometheus.relabel]: ../../reference/components/prometheus.relabel/
 [constants]: ../../reference/stdlib/constants/
 [localhost:3000/explore]: http://localhost:3000/explore
diff --git a/docs/sources/tutorials/processing-logs/index.md b/docs/sources/tutorials/processing-logs/index.md
index 05f551a2b2..9ee257c2d6 100644
--- a/docs/sources/tutorials/processing-logs/index.md
+++ b/docs/sources/tutorials/processing-logs/index.md
@@ -10,20 +10,26 @@ weight: 40
 This tutorial assumes you are familiar with setting up and connecting components.
 It covers using `loki.source.api` to receive logs over HTTP, processing and filtering them, and sending them to Loki.
 
-## Receive logs over HTTP and Process
+## Prerequisites
 
-**Recommended reading**
+Complete the [Logs and relabeling basics][logs] tutorial.
 
-- Optional: [loki.source.api][]
+## Receive logs over HTTP and Process
 
 The `loki.source.api` component can receive logs over HTTP.
 It can be useful for receiving logs from other {{< param "PRODUCT_NAME" >}}s or collectors, or directly from applications that can send logs over HTTP, and then processing them centrally.
 
+### Recommended reading
+
+- Optional: [loki.source.api][]
+
+### Set up the `loki.source.api` component
+
 Your pipeline is going to look like this:
 
 ![Loki Source API Pipeline](/media/docs/agent/diagram-flow-by-example-logs-pipeline.svg)
 
-Let's start by setting up the `loki.source.api` component:
+Start by setting up the `loki.source.api` component:
 
 ```alloy
 loki.source.api "listener" {
@@ -40,16 +46,19 @@ loki.source.api "listener" {
 
 This is a simple configuration.
 You are configuring the `loki.source.api` component to listen on `127.0.0.1:9999` and attach a `source="api"` label to the received log entries, which are then forwarded to the `loki.process.process_logs` component's exported receiver.
-Next, you can configure the `loki.process` and `loki.write` components.
 
 ## Process and Write Logs
 
-**Recommended reading**
+### Recommended reading
 
 - [loki.process#stage.drop][]
 - [loki.process#stage.json][]
 - [loki.process#stage.labels][]
 
+### Configure the `loki.process` and `loki.write` components
+
+Now that you have set up the `loki.source.api` component, you can configure the `loki.process` and `loki.write` components.
+
 ```alloy
 // Let's send and process more logs!
 
@@ -126,8 +135,7 @@ loki.write "local_loki" {
 }
 ```
 
-You can skip to the next section if you successfully completed the previous section's exercises.
-If not, or if you were unsure how things worked, let's break down what's happening in the `loki.process` component.
+{{< collapse title="How the components work" >}}
 
 Many of the `stage.*` blocks in `loki.process` act on reading or writing a shared map of values extracted from the logs.
 You can think of this extracted map as a hashmap or table that each stage has access to, and it is referred to as the "extracted map" from here on.
@@ -151,7 +159,7 @@ Here is our example log line:
 }
 ```
 
-### Stage 1
+#### Stage 1
 
 ```alloy
 stage.json {
@@ -198,7 +206,7 @@ Extracted map _after_ performing this stage:
 }
 ```
 
-### Stage 2
+#### Stage 2
 
 ```alloy
 stage.timestamp {
@@ -212,7 +220,7 @@ The value of `ts` is parsed in the format of `RFC3339` and added as the timestam
 This is useful if you want to use the timestamp present in the log itself, rather than the time the log is ingested.
 This stage doesn't modify the extracted map.
 
-### Stage 3
+#### Stage 3
 
 ```alloy
 stage.json {
@@ -278,7 +286,7 @@ Extracted map _after_ performing this stage:
 }
 ```
 
-### Stage 4
+#### Stage 4
 
 ```alloy
 stage.drop {
@@ -292,7 +300,7 @@ This stage drops the log line if the value of `is_secret` is `"true"` and doesn'
 There are many other ways to filter logs, but this is a simple example.
 Refer to the [loki.process#stage.drop][] documentation for more information.
 
-### Stage 5
+#### Stage 5
 
 ```alloy
 stage.labels {
@@ -306,7 +314,7 @@ This stage adds a label to the log using the same shorthand as above (so this is
 This stage adds a label with key `level` and the value of `level` in the extracted map to the log (`"info"` from our example log line).
 This stage does not modify the extracted map.
 
-### Stage 6
+#### Stage 6
 
 ```alloy
 stage.output {
@@ -319,9 +327,11 @@ Rather than sending the entire JSON blob to Loki, you are only sending `original
 
 This stage doesn't modify the extracted map.
 
-## Putting it all together
+{{< /collapse >}}
+
+## Put it all together
 
-Now that you have all of the pieces, let's run {{< param "PRODUCT_NAME" >}} and send some logs to it.
+Now that you have all of the pieces, you can run {{< param "PRODUCT_NAME" >}} and send some logs to it.
 Modify `config.alloy` with the configuration from the previous example and start {{< param "PRODUCT_NAME" >}} with:
 
 ```bash
@@ -344,7 +354,7 @@ Try executing the following, replacing the `"timestamp"` value:
 curl localhost:9999/loki/api/v1/raw -XPOST -H "Content-Type: application/json" -d '{"log": {"is_secret": "false", "level": "debug", "message": "This is a debug message!"}, "timestamp": <YOUR TIMESTAMP HERE>}'
 ```
 
-Now that you have sent some logs, let's see how they look in Grafana.
+Now that you have sent some logs, its time to see how they look in Grafana.
 Navigate to [localhost:3000/explore][] and switch the Datasource to `Loki`.
 Try querying for `{source="demo-api"}` and see if you can find the logs you sent.
 
@@ -355,8 +365,8 @@ You can also try adding more stages to the `loki.process` component to extract m
 
 ## Exercise
 
-Since you are already using Docker and Docker exports logs, let's get those logs into Loki.
-You can refer to the [discovery.docker][] and [loki.source.docker][] documentation for more information.
+Since you are already using Docker and Docker exports logs, you can send those logs to Loki.
+Refer to the [discovery.docker][] and [loki.source.docker][] documentation for more information.
 
 To ensure proper timestamps and other labels, make sure you use a `loki.process` component to process the logs before sending them to Loki.
 
@@ -407,6 +417,7 @@ loki.write "local_loki" {
 
 {{< /collapse >}}
 
+[logs]: ../logs-and-relabeling-basics/
 [loki.source.api]: ../../reference/components/loki.source.api/
 [loki.process#stage.drop]: ../../reference/components/loki.process/#stagedrop-block
 [loki.process#stage.json]: ../../reference/components/loki.process/#stagejson-block