Standardize wording for endpoint

Signed-off-by: Lynette Miles <[email protected]>

Author: esmerel

pipeline/filters/kubernetes.md

@@ -26,7 +26,7 @@ The plugin supports the following configuration parameters:
 | Key | Description | Default |
 | :--- | :--- | :--- |
 | `Buffer_Size` | Set the buffer size for HTTP client when reading responses from Kubernetes API server. The value must conform to the [unit size](../../administration/configuring-fluent-bit/unit-sizes.md) specification. A value of `0` results in no limit, and the buffer will expand as-needed. If pod specifications exceed the buffer limit, the API response is discarded when retrieving metadata, and some Kubernetes metadata will fail to be injected to the logs. | `32k` |
-| `Kube_URL` | API Server end-point | [https://kubernetes.default.svc:443](https://kubernetes.default.svc:443) |
+| `Kube_URL` | API Server endpoint | [https://kubernetes.default.svc:443](https://kubernetes.default.svc:443) |
 | `Kube_CA_File` | CA certificate file | `/var/run/secrets/kubernetes.io/serviceaccount/ca.crt` |
 | `Kube_CA_Path` | Absolute path to scan for certificate files | _none_ |
 | `Kube_Token_File` | Token file | `/var/run/secrets/kubernetes.io/serviceaccount/token` |
@@ -304,7 +304,7 @@ parsers:
     - name: custom-tag
       format: regex
       regex: '^(?<namespace_name>[^_]+)\.(?<pod_name>[a-z0-9](?:[-a-z0-9]*[a-z0-9])?(?:\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*)\.(?<container_name>.+)\.(?<container_id>[a-z0-9]{64})'
-      
+
 pipeline:
     inputs:
         - name: tail
@@ -590,4 +590,6 @@ Learn how to solve them to ensure that the Fluent Bit Kubernetes filter is opera
 
 ## Credit
 
-The Kubernetes Filter plugin is fully inspired by the [Fluentd Kubernetes Metadata Filter](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter) written by [Jimmi Dyson](https://github.com/jimmidyson).
+The Kubernetes Filter plugin is fully inspired by the [Fluentd Kubernetes Metadata
+Filter](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter)
+written by [Jimmi Dyson](https://github.com/jimmidyson).

pipeline/inputs/windows-exporter-metrics.md

@@ -77,7 +77,7 @@ In the following configuration file, the input plugin `windows_exporter_metrics`
 # Node Exporter Metrics + Prometheus Exporter
 # -------------------------------------------
 # The following example collect host metrics on Linux and expose
-# them through a Prometheus HTTP end-point.
+# them through a Prometheus HTTP endpoint.
 #
 # After starting the service try it with:
 #
@@ -86,13 +86,13 @@ In the following configuration file, the input plugin `windows_exporter_metrics`
 service:
    flush: 1
    log_level: info
-   
+
 pipeline:
   inputs:
     - name: windows_exporter_metrics
       tag: node_metrics
       scrape_interval: 2
-  
+
   outputs:
     - name: prometheus_exporter
       match: node_metrics
@@ -106,7 +106,7 @@ pipeline:
 # Node Exporter Metrics + Prometheus Exporter
 # -------------------------------------------
 # The following example collect host metrics on Linux and expose
-# them through a Prometheus HTTP end-point.
+# them through a Prometheus HTTP endpoint.
 #
 # After starting the service try it with:
 #
@@ -239,4 +239,4 @@ The WMI query will be called with the translated parameter as:
 
 The plugin implements a subset of the available collectors in the original Prometheus Windows Exporter. If you would like a specific collector prioritized, open a GitHub issue by using the following template:
 
-- [`in_windows_exporter_metrics`](https://github.com/fluent/fluent-bit/issues/new?assignees=\&labels=\&template=feature_request.md\&title=in_windows_exporter_metrics:%20add%20ABC%20collector)
+- [`in_windows_exporter_metrics`](https://github.com/fluent/fluent-bit/issues/new?assignees=\&labels=\&template=feature_request.md\&title=in_windows_exporter_metrics:%20add%20ABC%20collector)

pipeline/outputs/prometheus-exporter.md

@@ -31,7 +31,7 @@ The Prometheus exporter works only with metrics captured from metric plugins. In
 # Node Exporter Metrics + Prometheus Exporter
 # -------------------------------------------
 # The following example collect host metrics on Linux and expose
-# them through a Prometheus HTTP end-point.
+# them through a Prometheus HTTP endpoint.
 #
 # After starting the service try it with:
 #
@@ -65,7 +65,7 @@ pipeline:
 # Node Exporter Metrics + Prometheus Exporter
 # -------------------------------------------
 # The following example collect host metrics on Linux and expose
-# them through a Prometheus HTTP end-point.
+# them through a Prometheus HTTP endpoint.
 #
 # After starting the service try it with:
 #

pipeline/outputs/stackdriver.md

@@ -267,7 +267,7 @@ An upstream connection error means Fluent Bit wasn't able to reach Google servic
 [2019/01/07 23:24:09] [error] [oauth2] could not get an upstream connection
 ```
 
-This is due to a network issue in the environment where Fluent Bit is running. Make sure that the Host, Container or Pod can reach the following Google end-points:
+This is due to a network issue in the environment where Fluent Bit is running. Make sure that the Host, Container or Pod can reach the following Google endpoints:
 
 - [https://www.googleapis.com](https://www.googleapis.com)
 - [https://logging.googleapis.com](https://logging.googleapis.com)

vale-styles/FluentBit/Endpoint.yml

@@ -1,8 +1,9 @@
 extends: substitution
-message: "'%s' is not the preferred term; use 'endpoint' instead."
+message: 'Use "%s" instead of "%s".'
 level: error
 ignorecase: true
 swap:
-  "end point": "endpoint"
-  end-point: "endpoint"
-  end-points: "endpoints"
+  end point: endpoint
+  end-point: endpoint
+  end points: endpoints
+  end-points: endpoints