README: minor fixes (fluent#75)

* README.md: fix typo Signed-off-by: James Callahan <[email protected]> * README.md: remove (incorrect) version from heading Signed-off-by: James Callahan <[email protected]>
Yolean · May 20, 2020 · 92c3cff · 92c3cff
1 parent 034c8fc
commit 92c3cff
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-# Kubernetes Logging with Fluent Bit v1.0.4
+# Kubernetes Logging with Fluent Bit
 
 
 
@@ -77,7 +77,7 @@ The default configuration of Fluent Bit makes sure of the following:
 
 - Consume all containers logs from the running Node.
 - The [Tail input plugin](http://fluentbit.io/documentation/0.12/input/tail.html) will not append more than __5MB__  into the engine until they are flushed to the Elasticsearch backend. This limit aims to provide a workaround for [backpressure](http://fluentbit.io/documentation/0.13/configuration/backpressure.html) scenarios.
-- The Kubernetes filter will enrigh the logs with Kubernetes metadata, specifically _labels_ and _annotations_. The filter only goes to the API Server when it cannot find the cached info, otherwise it uses the cache.
+- The Kubernetes filter will enrich the logs with Kubernetes metadata, specifically _labels_ and _annotations_. The filter only goes to the API Server when it cannot find the cached info, otherwise it uses the cache.
 - The default backend in the configuration is Elasticsearch set by the [Elasticsearch Output Plugin](http://fluentbit.io/documentation/0.13/output/elasticsearch.html). It uses the Logstash format to ingest the logs. If you need a different Index and Type, please refer to the plugin option and do your own adjustments.
 - There is an option called __Retry_Limit__ set to False that means if Fluent Bit cannot flush the records to Elasticsearch it will re-try indefinitely until it succeeds.