[DOCS-15518] Update docs for multiple sources

hugo/content/en/observability_pipelines/_index.md

@@ -105,7 +105,7 @@ The Observability Pipelines UI provides a centralized control plane where you ca
 1. Navigate to [Observability Pipelines][1].
 1. Select a [template](#common-use-cases-and-templates) based on your use case.
 1. Set up your pipeline:
-    1. Choose a log [source][2].
+    1. Choose your log [sources][2].
     1. Configure [processors][3].
     1. Add one or more [destinations][4].
 1. [Install the Worker][5] in your environment

hugo/content/en/observability_pipelines/configuration/_index.md

@@ -23,7 +23,7 @@ further_reading:
 
 Observability Pipelines lets you collect and process logs and metrics within your own infrastructure, and then route them to different destinations. A pipeline consists of three core components:
 
-- [Source][1]: Receives data from a tool like the Datadog Agent.
+- [Sources][1]: Receive data from tools like the Datadog Agent.
 - [Processors][2]: Transform, enrich, or filter data.
 - [Destinations][3]: Where data is sent (for example, Datadog, Amazon S3, Splunk, Google Security Operations, and Microsoft Sentinel).
 
@@ -50,7 +50,7 @@ Use one of the [logs templates][1] to create a log pipeline.
 - Sensitive Data Redaction
 - Split Logs
 
-See [Set Up Pipelines][2] for more information on setting up a source, processors, and destinations.
+See [Set Up Pipelines][2] for more information on setting up sources, processors, and destinations.
 
 [1]: /observability_pipelines/configuration/explore_templates/?tab=logs#templates
 [2]: /observability_pipelines/configuration/set_up_pipelines/
@@ -61,7 +61,7 @@ See [Set Up Pipelines][2] for more information on setting up a source, processor
 
 Use the [Metric Tag Governance][1] template to create a metrics pipeline.
 
-See [Set Up Pipelines][2] for more information on setting up a source, processors and destination.
+See [Set Up Pipelines][2] for more information on setting up sources, processors, and destinations.
 
 ### Metrics data
 

hugo/content/en/observability_pipelines/configuration/set_up_pipelines.md

@@ -27,7 +27,7 @@ further_reading:
 <div class="alert alert-info">The pipelines and processors outlined in this documentation are specific to on-premises logging environments. To aggregate, process, and route cloud-based logs, see <a href="https://docs.datadoghq.com/logs/log_configuration/pipelines/?tab=source">Log Management Pipelines</a>.</div>
 
 In Observability Pipelines, a pipeline is a sequential path with three types of components:
-- [Source][1]: Receives data from your data source (for example, the Datadog Agent).
+- [Sources][1]: Receive data from your data sources (for example, the Datadog Agent).
 - [Processors][2]: Enrich and transform your data.
 - [Destinations][3]: Where your processed data is sent.
 
@@ -50,7 +50,7 @@ See [Export a Pipeline Configuration to JSON or Terraform][14] if you want to pr
 
 1. Navigate to [Observability Pipelines][1].
 1. Select a [template][2] based on your use case, or click {{< ui >}}New Pipeline{{< /ui >}} and select {{< ui >}}Logs Pipeline{{< /ui >}}.
-1. Select and set up a [log source][3].
+1. Select and set up your [log sources][3].
 1. Select and set up [destinations][5] for your processed logs.
 1. Click {{< ui >}}Edit{{< /ui >}} on a processor group to add, update, and validate your [processors][4] using [Pipeline Simulation][6].
     - **Notes**: