diff --git a/pipeline/parsers/logfmt.md b/pipeline/parsers/logfmt.md
index fa83d178c..c98676637 100644
--- a/pipeline/parsers/logfmt.md
+++ b/pipeline/parsers/logfmt.md
@@ -1,6 +1,6 @@
 # Logfmt
 
-The **logfmt** parser allows to parse the logfmt format described in [https://brandur.org/logfmt](https://brandur.org/logfmt) . A more formal description is in [https://godoc.org/github.com/kr/logfmt](https://godoc.org/github.com/kr/logfmt) .
+The _logfmt_ parser lets you parse data in the [logfmt](https://pkg.go.dev/github.com/kr/logfmt?utm_source=godoc) format.
 
 Here is an example parsers configuration:
 
@@ -25,13 +25,13 @@ parsers:
 {% endtab %}
 {% endtabs %}
 
-The following log entry is a valid content for the parser defined above:
+The following log entry is valid for the previously defined parser:
 
 ```text
 key1=val1 key2=val2 key3
 ```
 
-After processing, it internal representation will be:
+After processing, its internal representation will be:
 
 ```text
 [1540936693, {"key1"=>"val1",
@@ -39,8 +39,7 @@ After processing, it internal representation will be:
               "key3"=>true}]
 ```
 
-If you want to be more strict than the logfmt standard and not parse lines where some attributes do
-not have values (such as `key3`) in the example above, you can configure the parser as follows:
+If you want to be more strict than the logfmt standard and not parse lines where certain keys lack values (such as `key3` in the previous example), you can configure the parser as follows:
 
 {% tabs %}
 {% tab title="parsers.yaml" %}
@@ -63,4 +62,4 @@ parsers:
 ```
 
 {% endtab %}
-{% endtabs %}
\ No newline at end of file
+{% endtabs %}
diff --git a/vale-styles/FluentBit/Spelling-exceptions.txt b/vale-styles/FluentBit/Spelling-exceptions.txt
index 39beb30d8..35fcf9e8d 100644
--- a/vale-styles/FluentBit/Spelling-exceptions.txt
+++ b/vale-styles/FluentBit/Spelling-exceptions.txt
@@ -100,6 +100,7 @@ Kusto
 labelset
 librdkafka
 loadgenerator
+logfmt
 Logstash
 Lua
 Lucene