diff --git a/administration/multithreading.md b/administration/multithreading.md
index 57d792d9c..845fa1d94 100644
--- a/administration/multithreading.md
+++ b/administration/multithreading.md
@@ -6,15 +6,15 @@ description: Learn how to run Fluent Bit in multiple threads for improved scalab
 
 Fluent Bit has one event loop to handle critical operations, like managing
 timers, receiving internal messages, scheduling flushes, and handling retries.
-This event loop runs in Fluent Bit's main thread.
+This event loop runs in the main Fluent Bit thread.
 
 To free up resources in the main thread, you can configure
 [inputs](../pipeline/inputs/README.md) and [outputs](../pipeline/outputs/README.md)
 to run in their own self-contained threads. However, inputs and outputs implement
-multithreading in distinct ways: inputs can run in **threaded** mode, and outputs
-can use one or more **workers**.
+multithreading in distinct ways: inputs can run in threaded mode, and outputs
+can use one or more workers.
 
-Threading also affects certain processes related to inputs and outputs. For example, 
+Threading also affects certain processes related to inputs and outputs. For example,
 [filters](../pipeline/filters/README.md) always run in the main thread, but
 [processors](../pipeline/processors/README.md) run in the self-contained threads of
 their respective inputs or outputs, if applicable.
@@ -22,7 +22,7 @@ their respective inputs or outputs, if applicable.
 ## Inputs
 
 When inputs collect telemetry data, they can either perform this process
-inside Fluent Bit's main thread or inside a separate dedicated thread. You can
+inside the main Fluent Bit thread or inside a separate dedicated thread. You can
 configure this behavior by enabling or disabling the `threaded` setting.
 
 All inputs are capable of running in threaded mode, but certain inputs always
@@ -33,7 +33,7 @@ run in threaded mode regardless of configuration. These always-threaded inputs a
 - [Process Exporter Metrics](../pipeline/inputs/process-exporter-metrics.md)
 - [Windows Exporter Metrics](../pipeline/inputs/windows-exporter-metrics.md)
 
-Inputs are not internally aware of multithreading. If an input runs in threaded
+Inputs aren't internally aware of multithreading. If an input runs in threaded
 mode, Fluent Bit manages the logistics of that input's thread.
 
 ## Outputs
diff --git a/vale-styles/FluentBit/Spelling-exceptions.txt b/vale-styles/FluentBit/Spelling-exceptions.txt
index f2da97b32..d0ca2092f 100644
--- a/vale-styles/FluentBit/Spelling-exceptions.txt
+++ b/vale-styles/FluentBit/Spelling-exceptions.txt
@@ -89,6 +89,7 @@ matchers
 Minishift
 minikube
 MTTx
+multithreading
 namespace
 namespaces
 Nginx