Merge pull request #2024 from fluent/alexakreizinger/sc-143163/vale-final-sweep-through-pipeline-inputs

Author: alexakreizinger

.vale.ini

@@ -5,7 +5,7 @@ IgnoredScopes = tt, code
 [formats]
 mdx = md
 
-[*.{md,markdown,txt,htm,html}]
+[*.{md,markdown}]
 BasedOnStyles = FluentBit
 
 FluentBit.Terms = YES

README.md

@@ -24,7 +24,7 @@ description: High Performance Telemetry Agent for Logs, Metrics and Traces
   - Connect nearly any source to nearly any destination using preexisting plugins
   - Extensibility:
     - Write input, filter, or output plugins in the C language
-    - WASM: [WASM Filter Plugins](development/wasm-filter-plugins.md) or [WASM Input Plugins](development/wasm-input-plugins.md)
+    - Wasm: [Wasm Filter Plugins](development/wasm-filter-plugins.md) or [Wasm Input Plugins](development/wasm-input-plugins.md)
     - Write [Filters in Lua](pipeline/filters/lua.md) or [Output plugins in Golang](development/golang-output-plugins.md)
 - [Monitoring](administration/monitoring.md): Expose internal metrics over HTTP in JSON and [Prometheus](https://prometheus.io/) format
 - [Stream Processing](stream-processing/introduction.md): Perform data selection and transformation using simple SQL queries

SUMMARY.md

@@ -98,7 +98,7 @@
   * [Docker events](pipeline/inputs/docker-events.md)
   * [Docker metrics](pipeline/inputs/docker-metrics.md)
   * [Dummy](pipeline/inputs/dummy.md)
-  * [Ebpf](pipeline/inputs/ebpf.md)
+  * [eBPF](pipeline/inputs/ebpf.md)
   * [Elasticsearch](pipeline/inputs/elasticsearch.md)
   * [Exec WASI](pipeline/inputs/exec-wasi.md)
   * [Exec](pipeline/inputs/exec.md)

pipeline/inputs/disk-io-metrics.md

@@ -78,4 +78,4 @@ pipeline:
 
 Total interval (sec) = `Interval_Sec` + `(Interval_Nsec` / 1000000000)
 
-For example: `1.5s` = `1s` + `500000000ns`
+For example: `1.5s` = `1s` + `500000000ns`

pipeline/inputs/ebpf.md

@@ -1,4 +1,4 @@
-# Ebpf
+# eBPF
 
 {% hint style="info" %}
 This plugin is experimental and might be unstable. Use it in development or testing environments only. Its features and behavior are subject to change.

pipeline/inputs/elasticsearch.md

@@ -11,12 +11,12 @@ The plugin supports the following configuration parameters:
 | `buffer_max_size`   | Set the maximum size of buffer.                                                                                                          | `4M`          |
 | `buffer_chunk_size` | Set the buffer chunk size.                                                                                                               | `512K`        |
 | `tag_key`           | Specify a key name for extracting as a tag.                                                                                              | `NULL`        |
-| `meta_key`          | Specify a key name for meta information.                                                                                                 | "@meta"       |
-| `hostname`          | Specify hostname or fully qualified domain name. This parameter can be used for "sniffing" (auto-discovery of) cluster node information. | "localhost"   |
-| `version`           | Specify Elasticsearch server version. This parameter is effective for checking a version of Elasticsearch/OpenSearch server version.     | "8.0.0"       |
+| `meta_key`          | Specify a key name for meta information.                                                                                                 | `@meta`       |
+| `hostname`          | Specify hostname or fully qualified domain name. This parameter can be used for "sniffing" (auto-discovery of) cluster node information. | `localhost`   |
+| `version`           | Specify Elasticsearch server version. This parameter is effective for checking a version of Elasticsearch/OpenSearch server version.     | `8.0.0`       |
 | `threaded`          | Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs).                                  | `false`       |
 
-The Elasticsearch cluster uses "sniffing" to optimize the connections between its cluster and clients. Elasticsearch can build its cluster and dynamically generate a connection list which is called "sniffing". The `hostname` will be used for sniffing information and this is handled by the sniffing endpoint.
+The Elasticsearch cluster uses "sniffing" to optimize the connections between its cluster and clients, which means it builds its cluster and dynamically generate a connection list. The `hostname` will be used for sniffing information and this is handled by the sniffing endpoint.
 
 ## Get started
 

pipeline/inputs/exec-wasi.md

@@ -10,7 +10,7 @@ The plugin supports the following configuration parameters:
 |:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------|
 | `WASI_Path`        | The location of a Wasm program file.                                                                                                         |
 | `Parser`           | Specify the name of a parser to interpret the entry as a structured message.                                                                 |
-| `Accessible_Paths` | Specify the allowed list of paths to be able to access paths from WASM programs.                                                             |
+| `Accessible_Paths` | Specify the allowed list of paths to be able to access paths from Wasm programs.                                                             |
 | `Interval_Sec`     | Polling interval (seconds).                                                                                                                  |
 | `Interval_NSec`    | Polling interval (nanosecond).                                                                                                               |
 | `Wasm_Heap_Size`   | Size of the heap size of Wasm execution. Review [unit sizes](../../administration/configuring-fluent-bit/unit-sizes.md) for allowed values.  |
@@ -23,11 +23,11 @@ The plugin supports the following configuration parameters:
 
 Here is a configuration example.
 
-`in_exec_wasi` can handle parsers. To retrieve from structured data from a WASM program, you must create a `parser.conf`:
+`in_exec_wasi` can handle parsers. To retrieve from structured data from a Wasm program, you must create a `parser.conf`:
 
 The `Time_Format` should be aligned for the format of your using timestamp.
 
-This example assumes the WASM program writes JSON style strings to `stdout`.
+This example assumes the Wasm program writes JSON style strings to `stdout`.
 
 {% tabs %}
 {% tab title="parsers.yaml" %}

pipeline/inputs/exec.md

@@ -194,4 +194,4 @@ The previous script would be safer if written with:
   -p command='echo '"$(printf '%q' "$@")" \
 ```
 
-It's generally best to avoid dynamically generating the command or handling untrusted arguments.
+It's generally best to avoid dynamically generating the command or handling untrusted arguments.

pipeline/inputs/forward.md

@@ -57,7 +57,7 @@ pipeline:
       port: 24224
       buffer_chunk_size: 1M
       buffer_max_size: 6M
-      
+
   outputs:
     - name: stdout
       match: '*'
@@ -82,7 +82,7 @@ pipeline:
 {% endtab %}
 {% endtabs %}
 
-## Fluent Bit and Secure Forward Setup
+## Fluent Bit and secure forward setup
 
 In Fluent Bit v3 or later, `in_forward` can handle secure forward protocol.
 

pipeline/inputs/http.md

@@ -51,7 +51,7 @@ pipeline:
     - name: http
       listen: 0.0.0.0
       port: 8888
-      
+
   outputs:
     - name: stdout
       match: app.log
@@ -171,7 +171,7 @@ The `success_header` parameter lets you set multiple HTTP headers on success. Th
 pipeline:
   inputs:
     - name: http
-      success_header: 
+      success_header:
         - X-Custom custom-answer
         - X-Another another-answer
 ```
@@ -233,4 +233,4 @@ pipeline:
 
 ```shell
  fluent-bit -i http -p port=8888 -o stdout
-```
+```