Merge pull request #1999 from fluent/lynettemiles/sc-143290/remove-remaining-and-turn-on-vale-to-error

Author: esmerel

administration/backpressure.md

@@ -2,17 +2,17 @@
 
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=63e37cfe-9ce3-4a18-933a-76b9198958c1" />
 
-It's possible for logs or data to be ingested or created faster than the ability toflush it to some destinations. A common scenario is when reading from big log files, especially with a large backlog, and dispatching the logs to a backend over the network, which takes time to respond. This generates _backpressure_, leading to high memory consumption in the service.
+It's possible for logs or data to be ingested or created faster than the ability to flush it to some destinations. A common scenario is when reading from big log files, especially with a large backlog, and dispatching the logs to a backend over the network, which takes time to respond. This generates _backpressure_, leading to high memory consumption in the service.
 
 To avoid backpressure, Fluent Bit implements a mechanism in the engine that restricts the amount of data an input plugin can ingest. Restriction is done through the configuration parameters `Mem_Buf_Limit` and `storage.Max_Chunks_Up`.
 
 As described in the [Buffering](../concepts/buffering.md) concepts section, Fluent Bit offers two modes for data handling: in-memory only (default) and in-memory and filesystem (optional).
 
 The default `storage.type memory` buffer can be restricted with `Mem_Buf_Limit`. If memory reaches this limit and you reach a backpressure scenario, you won't be able to ingest more data until the data chunks that are in memory can be flushed. The input pauses and Fluent Bit [emits](https://github.com/fluent/fluent-bit/blob/v2.0.0/src/flb_input_chunk.c#L1334) a `[warn] [input] {input name or alias} paused (mem buf overlimit)` log message.
 
-Depending on the input plugin in use, this might cause incoming data to be discarded (for example, TCP input plugin). The tail plugin can handle pauses without data ingloss, storing its current file offset and resuming reading later. When buffer memory is available, the input resumes accepting logs. Fluent Bit [emits](https://github.com/fluent/fluent-bit/blob/v2.0.0/src/flb_input_chunk.c#L1277) a `[info] [input] {input name or alias} resume (mem buf overlimit)` message.
+Depending on the input plugin in use, this might cause incoming data to be discarded (for example, TCP input plugin). The tail plugin can handle pauses without data loss, storing its current file offset and resuming reading later. When buffer memory is available, the input resumes accepting logs. Fluent Bit [emits](https://github.com/fluent/fluent-bit/blob/v2.0.0/src/flb_input_chunk.c#L1277) a `[info] [input] {input name or alias} resume (mem buf overlimit)` message.
 
-Mitigate the risk of data loss by configuring secondary storage on the filesystem using the `storage.type` of `filesystem` (as described in [Buffering & Storage](buffering-and-storage.md)). Initially, logs will be buffered to both memory and the filesystem. When the `storage.max_chunks_up` limit is reached, all new data will be stored in the filesystem. Fluent Bit stops queueing new data in memory and buffers only to the filesystem. When `storage.type filesystem` is set, the `Mem_Buf_Limit` setting no longer has any effect. Instead, the `[SERVICE]` level `storage.max_chunks_up` setting controls the size of the memory buffer.
+Mitigate the risk of data loss by configuring secondary storage on the filesystem using the `storage.type` of `filesystem` (as described in [Buffering and Storage](buffering-and-storage.md)). Initially, logs will be buffered to both memory and the filesystem. When the `storage.max_chunks_up` limit is reached, all new data will be stored in the filesystem. Fluent Bit stops queueing new data in memory and buffers only to the filesystem. When `storage.type filesystem` is set, the `Mem_Buf_Limit` setting no longer has any effect. Instead, the `[SERVICE]` level `storage.max_chunks_up` setting controls the size of the memory buffer.
 
 ## `Mem_Buf_Limit`
 
@@ -38,7 +38,7 @@ In a few seconds, if the scheduler was able to flush the initial 700&nbsp;KB of
 
 - Upon data buffer release (700&nbsp;KB), the internal counters get updated.
 - Counters now are set at 500&nbsp;KB.
-- Because 500&nbsp;KB isless than 1&nbsp;MB, it checks the input plugin state.
+- Because 500&nbsp;KB is less than 1&nbsp;MB, it checks the input plugin state.
 - If the plugin is paused, it invokes a `resume` callback.
 - The input plugin can continue appending more data.
 
@@ -50,7 +50,7 @@ The setting behaves similar to the `Mem_Buf_Limit` scenario when the non-default
 
 When (default) `storage.pause_on_chunks_overlimit` is disabled, the input won't pause when the memory limit is reached. Instead, it switches to buffering logs only in the filesystem. Limit the disk spaced used for filesystem buffering with `storage.total_limit_size`.
 
-See [Buffering & Storage](buffering-and-storage.md) docs for more information.
+See [Buffering and Storage](buffering-and-storage.md) docs for more information.
 
 ## About pause and resume callbacks
 

administration/transport-security.md

@@ -51,7 +51,7 @@ The following **output** plugins can take advantage of the TLS feature:
 - [Splunk](../pipeline/outputs/splunk.md)
 - [Stackdriver](../pipeline/outputs/stackdriver.md)
 - [Syslog](../pipeline/outputs/syslog.md)
-- [TCP & TLS](../pipeline/outputs/tcp-and-tls.md)
+- [TCO and TLS](../pipeline/outputs/tcp-and-tls.md)
 - [Treasure Data](../pipeline/outputs/treasure-data.md)
 - [WebSocket](../pipeline/outputs/websocket.md)
 
@@ -92,7 +92,7 @@ By default, the HTTP input plugin uses plain TCP. Run the following command to e
 ```
 
 {% hint style="info" %}
-See Tips & Trick section below for details on generating `self_signed.crt` and `self_signed.key` files shown in these examples.
+See the Tips and Tricks section below for details on generating `self_signed.crt` and `self_signed.key` files shown in these examples.
 {% endhint %}
 
 In the previous command, the two properties `tls` and `tls.verify` are set for demonstration purposes. Always enable verification in production environments.

concepts/buffering.md

@@ -14,4 +14,4 @@ Fluent Bit buffering strategies are designed to solve problems associated with b
 
 These mechanisms aren't mutually exclusive. When data is ready to be processed or delivered it's always be in memory, while other data in the queue might be in the file system until is ready to be processed and moved up to memory.
 
-To learn more about the buffering configuration in Fluent Bit, see [Buffering & Storage](../administration/buffering-and-storage.md).
+To learn more about the buffering configuration in Fluent Bit, see [Buffering and Storage](../administration/buffering-and-storage.md).

pipeline/outputs/opentelemetry.md

@@ -47,9 +47,9 @@ The OpenTelemetry plugin works with logs and only the metrics collected from one
 {% tab title="fluent-bit.yaml" %}
 
 ```yaml
-# Dummy Logs & traces with Node Exporter Metrics export using OpenTelemetry output plugin
+# Dummy Logs and traces with Node Exporter Metrics export using OpenTelemetry output plugin
 # -------------------------------------------
-# The following example collects host metrics on Linux and dummy logs & traces and delivers
+# The following example collects host metrics on Linux and dummy logs and traces and delivers
 # them through the OpenTelemetry plugin to a local collector :
 #
 service:
@@ -95,9 +95,9 @@ pipeline:
 {% tab title="fluent-bit.conf" %}
 
 ```text
-# Dummy Logs & traces with Node Exporter Metrics export using OpenTelemetry output plugin
+# Dummy Logs and traces with Node Exporter Metrics export using OpenTelemetry output plugin
 # -------------------------------------------
-# The following example collects host metrics on Linux and dummy logs & traces and delivers
+# The following example collects host metrics on Linux and dummy logs and traces and delivers
 # them through the OpenTelemetry plugin to a local collector :
 #
 [SERVICE]

vale-styles/FluentBit/Ampersand.yml

@@ -1,6 +1,6 @@
 extends: existence
 message: 'Use "and" instead of "&" in content.'
-level: warning
+level: error
 scope: text
 nonword: true
 tokens: