docs: fix Vale and markdownlint findings across PR files

Resolve all Vale errors and suggestions in the config example validation
PR, plus markdownlint errors in the new scripts README.

- scripts/README.md: replace "e.g.," with "for example," (3 instances),
  convert 5 headings to sentence case, use "aren't" contraction, and fix
  markdownlint MD031/MD032/MD040 by adding blank lines around fences and
  lists and switching nested Markdown examples to 4-backtick outer fences
- installation/downloads/docker.md: spell out "K8s" as "Kubernetes"
- pipeline/inputs/tail.md: use "`inode` numbers" so the term is in code
  font and skipped by the spelling rule
- pipeline/filters/parser.md: use "shouldn't" contraction
- pipeline/outputs/kafka.md: use "isn't" contraction
- pipeline/parsers.md: remove leading ellipsis and rewrite as a complete
  sentence

Signed-off-by: Eric D. Schabell <eric@schabell.org>

Author: eschabell

installation/downloads/docker.md

@@ -303,7 +303,7 @@ The reasons for using distroless are well covered in
 - Reduces false positives on scans (and reduces resources required for scanning).
 - Reduces supply chain security requirements to only what you need.
 - Helps prevent unauthorised processes or users interacting with the container.
-- Less need to harden the container (and container runtime, K8s, and so on).
+- Less need to harden the container (and container runtime, Kubernetes, and so on).
 - Faster CI/CD processes.
 
 With any choice, there are downsides:

pipeline/filters/parser.md

@@ -16,7 +16,7 @@ The plugin supports the following configuration parameters:
 | `parser` | Specify the parser name to interpret the field. Multiple parser entries are allowed (one per line). | _none_ |
 | `preserve_key` | Keep the original `key_name` field in the parsed result. If false, the field will be removed. | `false` |
 | `reserve_data` | Keep all other original fields in the parsed result. If false, all other original fields will be removed. | `false` |
-| `Unescape_key` | Deprecated. This option is retained only for backward compatibility and should not be used in new configurations. | _deprecated_ |
+| `Unescape_key` | Deprecated. This option is retained only for backward compatibility and shouldn't be used in new configurations. | _deprecated_ |
 
 ## Get started
 

pipeline/inputs/tail.md

@@ -167,7 +167,7 @@ systemctl edit fluent-bit.service
 
 When the Linux inotify event queue overflows (indicated by an `IN_Q_OVERFLOW` event), Fluent Bit automatically reconciles all monitored files. During reconciliation it:
 
-- Detects rotated files by comparing inodes and file names and re-registers watches as needed.
+- Detects rotated files by comparing `inode` numbers and file names and re-registers watches as needed.
 - Resets offset tracking for files that have been truncated.
 - Retries watch registration for files that previously failed, for example due to `ENOSPC` when `fs.inotify.max_user_watches` is exhausted.
 

pipeline/outputs/kafka.md

@@ -88,7 +88,7 @@ pipeline:
 
 ### Avro support
 
-Fluent Bit comes with support for Avro encoding for the `out_kafka` plugin but this is not enabled by default for releases.
+Fluent Bit comes with support for Avro encoding for the `out_kafka` plugin but this isn't enabled by default for releases.
 
 Avro support is optional and must be activated at build time by using a build definition with `cmake`: `-DFLB_AVRO_ENCODER=On` such as in the following example which activates:
 

pipeline/parsers.md

@@ -22,7 +22,7 @@ For example, a parser can turn an unstructured log entry like this:
 192.168.2.20 - - [28/Jul/2006:10:27:10 -0300] "GET /cgi-bin/try/ HTTP/1.0" 200 3395
 ```
 
-...into a structured JSON object like this:
+The parser turns that entry into a structured JSON object like this:
 
 ```json
 {

scripts/README.md

@@ -1,14 +1,15 @@
-# Documentation Scripts
+# Documentation scripts
 
 This directory contains utility scripts for validating Fluent Bit configuration examples in the documentation.
 
-## Configuration Validation
+## Configuration validation
 
 ### `test-config.sh`
 
 Validates all Fluent Bit configuration examples in Markdown files by running them through `fluent-bit --dry-run`.
 
 **Usage:**
+
 ```bash
 ./scripts/test-config.sh <markdown-file>
 ```
@@ -23,6 +24,7 @@ The script uses a **two-stage approach** to ensure reliable error reporting:
 This approach ensures that extraction errors are always legitimate—never due to reaching the end of examples. Any extraction error indicates a genuine problem with the file structure.
 
 **Features:**
+
 - Supports multiple examples per Markdown file (processes all examples)
 - Validates both YAML (`fluent-bit.yaml`) and legacy `.conf` (`fluent-bit.conf`) formats
 - Reports all validation failures for a file (doesn't stop at first failure)
@@ -31,11 +33,13 @@ This approach ensures that extraction errors are always legitimate—never due t
 - Only reports errors that are legitimate (malformed examples or configuration issues)
 
 **Example - validate a single file:**
+
 ```bash
 ./scripts/test-config.sh pipeline/inputs/tail.md
 ```
 
 **Example - validate all documentation files:**
+
 ```bash
 find . -type f -iname "*.md" | while read -r file; do
     if ! ./scripts/test-config.sh "$file"; then
@@ -49,22 +53,26 @@ done
 Extracts Fluent Bit configuration code blocks from Markdown files. This is used internally by `test-config.sh` but can also be called directly.
 
 **Usage:**
+
 ```bash
 ./scripts/extract-config.sh <markdown-file> <tab-title> <fence-language> [index|count]
 ```
 
 **Parameters:**
+
 - `markdown-file`: Path to the Markdown file
-- `tab-title`: The tab title (e.g., `"fluent-bit.yaml"` or `"fluent-bit.conf"`)
-- `fence-language`: The code fence language (e.g., `yaml` or `text`)
+- `tab-title`: The tab title (for example, `"fluent-bit.yaml"` or `"fluent-bit.conf"`)
+- `fence-language`: The code fence language (for example, `yaml` or `text`)
 - `index|count` (Optional): Extract a specific example by index, or use `count` to get the total number of examples. Defaults to 1 (first example)
 
 **Features:**
+
 - Automatically removes common leading indentation from extracted examples
-- Handles indented tabs in Markdown (e.g., nested within list items or other structures)
+- Handles indented tabs in Markdown (for example, nested within list items or other structures)
 - Preserves relative indentation within the configuration
 
 **Examples:**
+
 ```bash
 # Count total YAML examples in a file
 ./scripts/extract-config.sh pipeline/inputs/tail.md "fluent-bit.yaml" yaml count
@@ -82,21 +90,23 @@ Extracts Fluent Bit configuration code blocks from Markdown files. This is used
 **Count mode:**
 
 The `count` parameter returns the total number of matching code fences for the specified language in the given tab. This is used by `test-config.sh` to:
+
 1. Determine how many examples to validate
 2. Avoid trying to extract examples that don't exist
 3. Ensure all extraction errors are legitimate
 
 Example output:
+
 ```bash
 $ ./scripts/extract-config.sh pipeline/inputs/tail.md "fluent-bit.yaml" yaml count
 5
 ```
 
-## Markdown Format
+## Markdown format
 
 Configuration examples should be formatted using Gitbook-style tabs:
 
-```markdown
+````markdown
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}
 ```yaml
@@ -111,12 +121,12 @@ service:
 ```
 {% endtab %}
 {% endtabs %}
-```
+````
 
 Multiple examples in the same file are supported:
 
-```markdown
-## First Example
+````markdown
+## First example
 
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}
@@ -126,7 +136,7 @@ Multiple examples in the same file are supported:
 {% endtab %}
 {% endtabs %}
 
-## Second Example
+## Second example
 
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}
@@ -135,14 +145,14 @@ Multiple examples in the same file are supported:
 ```
 {% endtab %}
 {% endtabs %}
-```
+````
 
-## Suppression List
+## Suppression list
 
 Some configuration examples are intentionally skipped in validation. These are configured in the `SUPPRESSED_FILES` array in `test-config.sh`. Files are suppressed if they:
 
 - Require additional plugins not included in the standard container image
-- Contain examples that are not yet supported
+- Contain examples that aren't yet supported
 - Are Windows-specific configurations
 
 Refer to the comments in `test-config.sh` for the complete list and reasons for each suppression.