chore: regenerate

loki/alloy-kafka-logs/step2.md

@@ -14,7 +14,7 @@ Grafana Alloy requires a configuration file to define the components and their r
 
 1. Click on the `config.alloy`{{copy}} file to open it in the code editor.
 
-The below configuration snippets will be added to the `config.alloy`{{copy}} file.
+You will copy all three of the following configuration snippets into the `config.alloy`{{copy}} file.
 
 ## Source logs from kafka
 
@@ -55,7 +55,7 @@ For more information on the `loki.source.kafka`{{copy}} configuration, see the [
 
 Next, we will configure the Loki relabel rules. The `loki.relabel`{{copy}} component rewrites the label set of each log entry passed to its receiver by applying one or more relabeling rules and forwards the results to the list of receivers in the component’s arguments. In our case we are directly calling the rule from the `loki.source.kafka`{{copy}} component.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 loki.relabel "kafka" {
@@ -81,7 +81,7 @@ For more information on the `loki.relabel`{{copy}} configuration, see the [Loki
 
 Lastly, we will configure the Loki write component. `loki.write`{{copy}} receives log entries from other loki components and sends them over the network using the Loki logproto format.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+And finally, add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 loki.write "http" {

loki/alloy-kafka-logs/step3.md

@@ -4,13 +4,13 @@ Next we will configure Alloy to also ingest OpenTelemetry logs via Kafka, we nee
 
 ## Open your Code Editor and Locate the `config.alloy`{{copy}} file
 
-Like before, we generate our next pipeline configuration within the same `config.alloy`{{copy}} file. The below configuration snippets will be added **in addition** to the existing configuration. Essentially, we are configuring two pipelines within the same Alloy configuration file.
+Like before, we generate our next pipeline configuration within the same `config.alloy`{{copy}} file. You will add the following configuration snippets to the file **in addition** to the existing configuration. Essentially, we are configuring two pipelines within the same Alloy configuration file.
 
 ## Source OpenTelemetry logs from Kafka
 
 First, we will configure the OpenTelemetry Kafaka receiver. `otelcol.receiver.kafka`{{copy}} accepts telemetry data from a Kafka broker and forwards it to other `otelcol.*`{{copy}} components.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 otelcol.receiver.kafka "default" {
@@ -43,7 +43,7 @@ For more information on the `otelcol.receiver.kafka`{{copy}} configuration, see
 
 Next, we will configure a OpenTelemetry processor. `otelcol.processor.batch`{{copy}} accepts telemetry data from other otelcol components and places them into batches. Batching improves the compression of data and reduces the number of outgoing network requests required to transmit data. This processor supports both size and time based batching.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 otelcol.processor.batch "default" {

loki/alloy-otel-logs/step2.md

@@ -10,17 +10,17 @@ Grafana Alloy requires a configuration file to define the components and their r
 
 1. Expand the `loki-fundamentals`{{copy}} directory in the file explorer of the `Editor`{{copy}} tab.
 
-1. Locate the `config.alloy`{{copy}} file in the `loki-fundamentals`{{copy}} directory (Top level directory).
+1. Locate the `config.alloy`{{copy}} file in the top level directory, `loki-fundamentals'.
 
 1. Click on the `config.alloy`{{copy}} file to open it in the code editor.
 
-The below configuration snippets will be added to the `config.alloy`{{copy}} file.
+You will copy all three of the following configuration snippets into the `config.alloy`{{copy}} file.
 
 ## Recive OpenTelemetry logs via gRPC and HTTP
 
 First, we will configure the OpenTelemetry receiver. `otelcol.receiver.otlp`{{copy}} accepts logs in the OpenTelemetry format via HTTP and gRPC. We will use this receiver to receive logs from the Carnivorous Greenhouse application.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
  otelcol.receiver.otlp "default" {
@@ -47,7 +47,7 @@ For more information on the `otelcol.receiver.otlp`{{copy}} configuration, see t
 
 Next, we will configure a OpenTelemetry processor. `otelcol.processor.batch`{{copy}} accepts telemetry data from other otelcol components and places them into batches. Batching improves the compression of data and reduces the number of outgoing network requests required to transmit data. This processor supports both size and time based batching.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 otelcol.processor.batch "default" {
@@ -67,7 +67,7 @@ For more information on the `otelcol.processor.batch`{{copy}} configuration, see
 
 Lastly, we will configure the OpenTelemetry exporter. `otelcol.exporter.otlphttp`{{copy}} accepts telemetry data from other otelcol components and writes them over the network using the OTLP HTTP protocol. We will use this exporter to send the logs to Loki’s native OTLP endpoint.
 
-Add the following configuration to the `config.alloy`{{copy}} file:
+Now add the following configuration to the `config.alloy`{{copy}} file:
 
 ```alloy
 otelcol.exporter.otlphttp "default" {