docs: Fix typos (#14339)

docs/CONFIGURATION.md

@@ -231,7 +231,7 @@ combining an integer value and time unit as a string value.  Valid time units ar
 
 Global tags can be specified in the `[global_tags]` table in key="value"
 format. All metrics that are gathered will be tagged with the tags specified.
-Global tags are overriden by tags set by plugins.
+Global tags are overridden by tags set by plugins.
 
 ```toml
 [global_tags]
@@ -375,7 +375,7 @@ Parameters that can be used with any input plugin:
   Overrides the `precision` setting of the [agent][Agent] for the plugin.
   Collected metrics are rounded to the precision specified as an [interval][].
 
-  When this value is set on a service input, multiple events occuring at the
+  When this value is set on a service input, multiple events occurring at the
   same timestamp may be merged by the output database.
 
 - **collection_jitter**:

docs/developers/REVIEWS.md

@@ -70,7 +70,7 @@ In case you still want to continue with the PR, feel free to reopen it.
 
 ## Linting
 
-Each pull request will have the appriopriate linters checking the files for any common mistakes. The github action Super Linter is used: [super-pinter](https://github.com/github/super-linter). If it is failing you can click on the action and read the logs to figure out the issue. You can also run the github action locally by following these instructions: [run-linter-locally.md](https://github.com/github/super-linter/blob/main/docs/run-linter-locally.md). You can find more information on each of the linters in the super linter readme.
+Each pull request will have the appropriate linters checking the files for any common mistakes. The github action Super Linter is used: [super-pinter](https://github.com/github/super-linter). If it is failing you can click on the action and read the logs to figure out the issue. You can also run the github action locally by following these instructions: [run-linter-locally.md](https://github.com/github/super-linter/blob/main/docs/run-linter-locally.md). You can find more information on each of the linters in the super linter readme.
 
 ## Testing
 

plugins/inputs/modbus/README.md

@@ -149,7 +149,7 @@ See the [CONFIGURATION.md][CONFIGURATION.md] for more details.
     register = "coil"
 
     ## Name of the measurement.
-    ## Can be overriden by the individual field definitions. Defaults to "modbus"
+    ## Can be overridden by the individual field definitions. Defaults to "modbus"
     # measurement = "modbus"
 
     ## Request optimization algorithm.

plugins/inputs/modbus/sample_request.conf

@@ -22,7 +22,7 @@
     register = "coil"
 
     ## Name of the measurement.
-    ## Can be overriden by the individual field definitions. Defaults to "modbus"
+    ## Can be overridden by the individual field definitions. Defaults to "modbus"
     # measurement = "modbus"
 
     ## Request optimization algorithm.

plugins/inputs/mqtt_consumer/README.md

@@ -25,7 +25,7 @@ See the [CONFIGURATION.md][CONFIGURATION.md] for more details.
 
 ## Secret-store support
 
-This plugin supports secrets from secret-stores for the `usernane` and
+This plugin supports secrets from secret-stores for the `username` and
 `password` option.
 See the [secret-store documentation][SECRETSTORE] for more details on how
 to use them.

plugins/parsers/prometheus/parser_test.go

@@ -335,7 +335,7 @@ func TestDefautTags(t *testing.T) {
 	parser := Parser{
 		DefaultTags: map[string]string{
 			"defaultTag":    "defaultTagValue",
-			"dockerVersion": "to_be_overriden",
+			"dockerVersion": "to_be_overridden",
 		},
 	}
 	metrics, err := parser.Parse([]byte(validUniqueGauge))