Merge pull request #1488 from fluent/lynettemiles/sc-105700/update-concepts-data-pipeline-parser-md-fluent

Author: esmerel

concepts/data-pipeline/parser.md

@@ -1,10 +1,12 @@
 ---
-description: Convert Unstructured to Structured messages
+description: Convert unstructured messages to structured messages
 ---
 
 # Parser
 
-Dealing with raw strings or unstructured messages is a constant pain; having a structure is highly desired. Ideally we want to set a structure to the incoming data by the Input Plugins as soon as they are collected:
+Dealing with raw strings or unstructured messages is difficult. Having a structure
+makes data more usable. Set a structure to the incoming data by using input
+plugins as data is collected:
 
 ```mermaid
 graph LR
@@ -19,13 +21,18 @@ graph LR
     E --> H[Output 3]
     style B stroke:darkred,stroke-width:2px;
 ```
-The Parser allows you to convert from unstructured to structured data. As a demonstrative example consider the following Apache (HTTP Server) log entry:
 
-```
+The parser converts unstructured data to structured data. As an example, consider the
+following Apache (HTTP Server) log entry:
+
+```text
 192.168.2.20 - - [28/Jul/2006:10:27:10 -0300] "GET /cgi-bin/try/ HTTP/1.0" 200 3395
 ```
 
-The above log line is a raw string without format, ideally we would like to give it a structure that can be processed later easily. If the proper configuration is used, the log entry could be converted to:
+This log line is a raw string without format. Structuring the log makes it easier
+to process the data later. If the
+[regular expression parser](pipeline/parsers/regular-expression) is used, the log
+entry could be converted to:
 
 ```javascript
 {
@@ -40,4 +47,6 @@ The above log line is a raw string without format, ideally we would like to give
  }
 ```
 
-Parsers are fully configurable and are independently and optionally handled by each input plugin, for more details please refer to the [Parsers](https://docs.fluentbit.io/manual/pipeline/parsers) section.
+Parsers are fully configurable and are independently and optionally handled by each
+input plugin. For more details, see
+[Parsers](https://docs.fluentbit.io/manual/pipeline/parsers).