Skip to content

Commit 48fd48b

Browse files
committed
global: grammar fixes
Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
1 parent b9f5d84 commit 48fd48b

File tree

7 files changed

+7
-7
lines changed

7 files changed

+7
-7
lines changed

about/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,4 @@
44

55
We, [Treasure Data](http://treasuredata.com), as a Big Data company, provide an analytics infrastructure in the Cloud where we provide an end-to-end solution to collect, store and do analytics over the data. [Fluent Bit](http://fluentbit.io) is an integral part of this pipeline where it solve the log collection needs.
66

7-
Being an open source project, it have been widely adopted to solve logging needs in Cloud Native environments where Docker and Kubernetes are key components; Fluent Bit is a natural fit.
7+
Being an open source project, it has been widely adopted to solve logging needs in Cloud Native environments where Docker and Kubernetes are key components; Fluent Bit is a natural fit.

configuration/file.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ The following configuration file example demonstrates how to collect CPU metrics
124124

125125
To avoid complicated long configuration files is better to split specific parts in different files and call them (include) from one main file.
126126

127-
Starting from Fluent Bit 0.12 the new configuration command _@INCLUDE_ have been added and can be used in the following way:
127+
Starting from Fluent Bit 0.12 the new configuration command _@INCLUDE_ has been added and can be used in the following way:
128128

129129
```
130130
@INCLUDE somefile.conf

configuration/memory_usage.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Is well known that in intensive environments where memory allocations happens in
1818

1919
It's strongly suggested that in any production environment, Fluent Bit be build with Jemalloc enabled (-DFLB_JEMALLOC=On), which is an alternative memory allocator that have better strategies to reduce fragmentation among others for better performance.
2020

21-
You can check if Fluent Bit have been built with Jemalloc using the following command:
21+
You can check if Fluent Bit has been built with Jemalloc using the following command:
2222

2323
```
2424
$ bin/fluent-bit -h|grep JEMALLOC

configuration/schema.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ A simple example of a configuration file is as follows:
1717

1818
## Sections {#sections}
1919

20-
A section is defined by a name or title inside brackets. Looking at the example above a Server section have been set using __[SERVICE]__ definition. Section rules:
20+
A section is defined by a name or title inside brackets. Looking at the example above a Server section has been set using __[SERVICE]__ definition. Section rules:
2121

2222
* All section content must be indented (4 spaces ideally).
2323
* Multiples sections can exists on the same file.

development/library_api.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,7 @@ The properties allowed per output plugin are specified on each specific plugin d
199199

200200
## Start Fluent Bit Engine
201201

202-
Once the library context have been created and the input/output plugin instances are set, the next step is to start the engine. When started, the engine runs inside a new thread (POSIX thread) without blocking the caller application. To start the engine the function __flb_start()__ is used.
202+
Once the library context has been created and the input/output plugin instances are set, the next step is to start the engine. When started, the engine runs inside a new thread (POSIX thread) without blocking the caller application. To start the engine the function __flb_start()__ is used.
203203

204204
__Prototype__
205205

input/kmsg.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Copyright (C) Treasure Data
2020
...
2121
```
2222
23-
As described above, the plugin processed all messages that the Linux Kernel reported, the output have been truncated for clarification.
23+
As described above, the plugin processed all messages that the Linux Kernel reported, the output has been truncated for clarification.
2424
2525
### Configuration File
2626

parser/json.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -24,4 +24,4 @@ After processing, it internal representation will be:
2424
[1154103724, {"key1"=>12345, "key2"=>"abc"}]
2525
```
2626

27-
The time have been converted to Unix timestamp (UTC) and the map reduced to each component of the original message.
27+
The time has been converted to Unix timestamp (UTC) and the map reduced to each component of the original message.

0 commit comments

Comments
 (0)