diff --git a/concepts/buffering.md b/concepts/buffering.md
index b7f82affd..a45a4e963 100644
--- a/concepts/buffering.md
+++ b/concepts/buffering.md
@@ -1,22 +1,32 @@
 ---
-description: Performance and Data Safety
+description: Performance and data safety
 ---
 
 # Buffering
 
-When [Fluent Bit](https://fluentbit.io) processes data, it uses the system memory \(heap\) as a primary and temporary place to store the record logs before they get delivered, in this private memory area the records are processed.
+When [Fluent Bit](https://fluentbit.io) processes data, it uses the system memory
+(heap) as a primary and temporary place to store the record logs before they get
+delivered. The records are processed in this private memory area.
 
-Buffering refers to the ability to store the records somewhere, and while they are processed and delivered, still be able to store more. Buffering in memory is the fastest mechanism, but there are certain scenarios where it requires special strategies to deal with [backpressure](../administration/backpressure.md), data safety or reduce memory consumption by the service in constrained environments.
+Buffering is the ability to store the records, and continue storing incoming data
+while previous data is processed and delivered. Buffering in memory is the fastest
+mechanism, but there are scenarios requiring special strategies to deal with
+[backpressure](../administration/backpressure.md), data safety, or to reduce memory
+consumption by the service in constrained environments.
 
-{% hint style="info" %}
-Network failures or latency on third party service is pretty common, and on scenarios where we cannot deliver data fast enough as we receive new data to process, we likely will face backpressure.
+Network failures or latency in third party service is common. When data can't be
+delivered fast enough and new data to process arrives, the system can face
+backpressure.
 
-Our buffering strategies are designed to solve problems associated with backpressure and general delivery failures.
-{% endhint %}
+Fluent Bit buffering strategies are designed to solve problems associated with
+backpressure and general delivery failures. Fluent Bit offers a primary buffering
+mechanism in memory and an optional secondary one using the file system. With
+this hybrid solution you can accommodate any use case safely and keep a high
+performance while processing your data.
 
-Fluent Bit as buffering strategies go, offers a primary buffering mechanism in **memory** and an optional secondary one using the **file system**. With this hybrid solution you can accommodate any use case safely and keep a high performance while processing your data.
-
-Both mechanisms are not mutually exclusive and when the data is ready to be processed or delivered it will 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, please jump to the [Buffering & Storage](../administration/buffering-and-storage.md) section.
+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).
diff --git a/vale-styles/FluentBit/Spelling-exceptions.txt b/vale-styles/FluentBit/Spelling-exceptions.txt
index fa3157ce2..18b032117 100644
--- a/vale-styles/FluentBit/Spelling-exceptions.txt
+++ b/vale-styles/FluentBit/Spelling-exceptions.txt
@@ -8,6 +8,7 @@ autoscale
 autoscaler
 autoscaling
 backoff
+backpressure
 Blackhole
 blocklist
 Buildkite