Apply suggestions from code review

Co-authored-by: Alexa Kreizinger <[email protected]>
Signed-off-by: Lynette  Miles <[email protected]>

Author: esmerel

administration/configuring-fluent-bit/classic-mode/format-schema.md

@@ -5,7 +5,7 @@ Fluent Bit might optionally use a configuration file to define how the service w
 The schema is defined by three concepts:
 
 - Sections
-- Entries: Key/Value
+- Entries: key/value
 - Indented Configuration Mode
 
 An example of a configuration file is as follows:
@@ -19,16 +19,15 @@ An example of a configuration file is as follows:
 
 ## Sections
 
-A section is defined by a name or title inside brackets. Using the previous example,
-a Service section has been set using `[SERVICE]` definition. The following rules apply:
+A section is defined by a name or title inside brackets. Using the previous example, a Service section has been set using `[SERVICE]` definition. The following rules apply:
 
-- All section content must be indented (4 spaces ideally).
+- All section content must be indented (four spaces ideally).
 - Multiple sections can exist on the same file.
 - A section must have comments and entries.
 - Any commented line under a section must be indented too.
 - End-of-line comments aren't supported, only full-line comments.
 
-## Entries: Key/Value
+## Entries: key/value
 
 A section can contain entries. An entry is defined by a line of text that contains a `Key` and a `Value`. Using the previous example, the `[SERVICE]` section contains two entries: one is the key `Daemon` with value `off` and the other is the key `Log_Level` with the value `debug`. The following rules apply:
 
@@ -54,5 +53,4 @@ Fluent Bit configuration files are based in a strict indented mode. Each configu
     KeyN  3.14
 ```
 
-This example shows two sections with multiple entries and comments. Empty lines are
-allowed.
+This example shows two sections with multiple entries and comments. Empty lines are allowed.