Merge pull request #1649 from fluent/lynettemiles/sc-135613/update-fluent-bit-fluent-bit-docs-administration

Author: esmerel

administration/configuring-fluent-bit/yaml/upstream-servers-section.md

@@ -1,8 +1,9 @@
-# Upstream Servers Section
+# Upstream servers
 
-The `Upstream Servers` section defines a group of endpoints, referred to as nodes, which are used by output plugins to distribute data in a round-robin fashion. This is particularly useful for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](https://docs.fluentbit.io/manual/pipeline/outputs/forward) and [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch).
+The `upstream_servers` section defines a group of endpoints, referred to as nodes. Nodes are used by output plugins to distribute data in a round-robin fashion. This is useful for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](https://docs.fluentbit.io/manual/pipeline/outputs/forward) and [Elasticsearch](https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch).
 
-In YAML, this section is named `upstream_servers` and requires specifying a `name` for the group and a list of `nodes`. Below is an example that defines two upstream server groups: `forward-balancing` and `forward-balancing-2`:
+The `upstream_servers` section require specifying a `name` for the group and a list
+of `nodes`. The following example defines two upstream server groups, `forward-balancing` and `forward-balancing-2`:
 
 ```yaml
 upstream_servers:
@@ -34,13 +35,8 @@ upstream_servers:
         port: 51000
 ```
 
-### Key Concepts
+Each node in the `upstream_servers` group must specify a `name`, `host`, and `port`.
+Additional settings like `tls`, `tls_verify`, and `shared_key` can be configured for
+secure communication.
 
-- Nodes: Each node in the upstream_servers group must specify a name, host, and port. Additional settings like tls, tls_verify, and shared_key can be configured as needed for secure communication.
-
-
-### Usage Note
-
-While the `upstream_servers` section can be defined globally, some output plugins may require the configuration to be specified in a separate YAML file. Be sure to consult the documentation for each specific output plugin to understand its requirements.
-
-For more details, refer to the documentation of the respective output plugins.
+While the `upstream_servers` section can be defined globally, some output plugins might require the configuration to be specified in a separate YAML file. Consult the documentation for each specific output plugin to understand its requirements.