GitBook: [1.4] 117 pages and one asset modified

Author: edsiper

.gitbook/assets/logo_documentation_1.3.png

@@ -4,13 +4,13 @@ description: The Production Grade Ecosystem
 
 # Fluentd & Fluent Bit
 
-Logging and data processing in general can be complex, and at scale a bit more, that's why [Fluentd](https://www.fluentd.org) was born. But now is more than a simple tool, it's a full ecosystem that contains SDKs for different languages and sub projects like [Fluent Bit](https://fluentbit.io). 
+Logging and data processing in general can be complex, and at scale a bit more, that's why [Fluentd](https://www.fluentd.org) was born. But now is more than a simple tool, it's a full ecosystem that contains SDKs for different languages and sub projects like [Fluent Bit](https://fluentbit.io).
 
 On this page, we will describe the relationship between the [Fluentd](http://fluentd.org) and [Fluent Bit](http://fluentbit.io) open source projects, as a summary we can say both are:
 
 * Licensed under the terms of Apache License v2.0
 * Hosted projects by the [Cloud Native Computing Foundation \(CNCF\)](https://cncf.io)
-* Production Grade solutions: deployed **thousands** of times every single day, **millions** per ****month.
+* Production Grade solutions: deployed **thousands** of times every single day, **millions** per _\*\*_month.
 * Community driven projects
 * Widely Adopted by the Industry: trusted by all major companies like AWS, Microsoft, Google Cloud and hundred of others.
 * Originally created by [Treasure Data](https://www.treasuredata.com). 
@@ -29,5 +29,5 @@ The following table describes a comparison in different areas of the projects:
 | Plugins | More than 1000 plugins available | Around 50 plugins available |
 | License | [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0) | [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0) |
 
-Both Fluentd and Fluent Bit can work as Aggregators of Forwarders, they both can complement each other or use them as standalone solutions. 
+Both Fluentd and Fluent Bit can work as Aggregators of Forwarders, they both can complement each other or use them as standalone solutions.
 

about/fluentd-and-fluent-bit.md

@@ -4,13 +4,13 @@ description: Performance and data safety
 
 # Buffering
 
-When [Fluent Bit](https://fluentbit.io) process data, it uses the system memory \(heap\) as a primary and temporal place to store the record logs before they get delivered, on this private memory area the records are processed. 
+When [Fluent Bit](https://fluentbit.io) process data, it uses the system memory \(heap\) as a primary and temporal place to store the record logs before they get delivered, on this private memory area the records are processed.
 
 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 the mechanism requires special strategies to deal with [backpressure](../administration/backpressure.md), data safety or reduce memory consumption by the service in constraint environments.
 
 Fluent Bit as buffering strategies, offers a primary buffering mechanism in **memory** and an optional secondary one using the **file system**. With this hybrid solution you can adjust to any use case safety and keep a high performance while processing your data.
 
-Both mechanisms are not exclusive and when the data is ready to be processed or delivered it will be always **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. 
+Both mechanisms are not exclusive and when the data is ready to be processed or delivered it will be always **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.