From 5293554f27b7036cb273eb8c5038cab606cc177a Mon Sep 17 00:00:00 2001 From: Paulin Todev Date: Fri, 16 Feb 2024 09:52:58 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> --- .../sources/flow/reference/components/otelcol.auth.headers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/flow/reference/components/otelcol.auth.headers.md b/docs/sources/flow/reference/components/otelcol.auth.headers.md index 04039dc16622..6b70a021de35 100644 --- a/docs/sources/flow/reference/components/otelcol.auth.headers.md +++ b/docs/sources/flow/reference/components/otelcol.auth.headers.md @@ -72,9 +72,9 @@ block. The `value` attribute sets the value of the header directly. Alternatively, `from_context` can be used to dynamically retrieve the header value from request metadata. -In order for `from_context` to work, other components in the pipeline also need to be configured appropriately: +For `from_context` to work, other components in the pipeline also need to be configured appropriately: * If an `otelcol.processor.batch` is present in the pipeline, it must be configured to preserve client metadata. - Do this by adding the value which `from_context` needs to the `metadata_keys` of the batch processor. + Do this by adding the value that `from_context` needs to the `metadata_keys` of the batch processor. * `otelcol` receivers must be configured with `include_metadata` set to `true` so that metadata keys are available to the pipeline. ## Exported fields