Small tweaks from code review

grafana · Dec 6, 2023 · 882e47f · 882e47f
1 parent 42ba914
commit 882e47f
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/sources/flow/getting-started/migrating-from-operator.md b/docs/sources/flow/getting-started/migrating-from-operator.md
@@ -272,7 +272,7 @@ The logging subsystem is very powerful and has many options for processing logs.
 
 The `Integration` CRD isn't supported with {{< param "PRODUCT_NAME" >}}.
 However, all static mode integrations have an equivalent component in the [`prometheus.exporter`][] namespace.
-The reference docs should help convert those integrations to their {{< param "PRODUCT_NAME" >}} equivalent.
+The [reference documentation][component documentation] should help convert those integrations to their {{< param "PRODUCT_NAME" >}} equivalent.
 
 [default values]: https://github.com/grafana/agent/blob/main/operations/helm/charts/grafana-agent/values.yaml
 

diff --git a/docs/sources/flow/getting-started/migrating-from-static.md b/docs/sources/flow/getting-started/migrating-from-static.md
@@ -65,7 +65,7 @@ This conversion will enable you to take full advantage of the many additional fe
 
 ### Debugging
 
-1. If the convert command cannot convert a [Static] configuration, diagnostic information is sent to `stderr`.
+1. If the convert command can't convert a [Static][] configuration, diagnostic information is sent to `stderr`.
    You can use the `--bypass-errors` flag to bypass any non-critical issues and output the {{< param "PRODUCT_NAME" >}} configuration using a best-effort conversion.
 
    {{% admonition type="caution" %}}

diff --git a/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md b/docs/sources/flow/getting-started/opentelemetry-to-lgtm-stack.md
@@ -42,7 +42,7 @@ This topic describes how to:
 
 ## The pipeline
 
-You can start with the {{< param "PRODUCT_NAME" >}} configuration you created in the previous Getting Started guide.
+You can start with the {{< param "PRODUCT_NAME" >}} configuration you created in the [Collect open telemetry data][] Getting Started guide.
 
 ```river
 otelcol.receiver.otlp "example" {