fix: s/compatability/compatibility

content/influxdb/v1.5/supported_protocols/collectd.md

@@ -23,7 +23,7 @@ Each collectd input allows the binding address, target database, and target rete
 
 Each collectd input also performs internal batching of the points it receives, as batched writes to the database are more efficient. The default batch size is 1000, pending batch factor is 5, with a batch timeout of 1 second. This means the input will write batches of maximum size 1000, but if a batch has not reached 1000 points within 1 second of the first point being added to a batch, it will emit that batch regardless of size. The pending batch factor controls how many batches can be in memory at once, allowing the input to transmit a batch, while still building other batches.
 
-Multi-value plugins can be handled two ways.  Setting parse-multivalue-plugin to "split" will parse and store the multi-value plugin data (e.g., df free:5000,used:1000) into separate measurements (e.g., (df_free, value=5000) (df_used, value=1000)), while "join" will parse and store the multi-value plugin as a single multi-value measurement (e.g., (df, free=5000,used=1000)).  "split" is the default behavior for backward compatability with previous versions of influxdb.
+Multi-value plugins can be handled two ways.  Setting parse-multivalue-plugin to "split" will parse and store the multi-value plugin data (e.g., df free:5000,used:1000) into separate measurements (e.g., (df_free, value=5000) (df_used, value=1000)), while "join" will parse and store the multi-value plugin as a single multi-value measurement (e.g., (df, free=5000,used=1000)).  "split" is the default behavior for backward compatibility with previous versions of influxdb.
 
 The path to the collectd types database file may also be set.
 

content/influxdb/v2.0/reference/api/influxdb-1x/_index.md

@@ -59,7 +59,7 @@ Authorization: Token mYSuP3rs3cREtT0k3N
 
 ##### InfluxQL support
 
-The compatability API supports InfluxQL, with the following caveats:
+The compatibility API supports InfluxQL, with the following caveats:
 
 - The `INTO` clause (e.g. `SELECT ... INTO ...`) is not supported.
 - With the exception of [`DELETE`](/influxdb/v1.8/query_language/manage-database/#delete-series-with-delete) and 

content/telegraf/v1.10/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.11/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.12/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.13/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.14/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.15/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```

content/telegraf/v1.9/data_formats/input/collectd.md

@@ -43,6 +43,6 @@ You can also change the path to the typesdb or add additional typesdb using
   ## Multi-value plugins can be handled two ways.
   ## "split" will parse and store the multi-value plugin data into separate measurements
   ## "join" will parse and store the multi-value plugin as a single multi-value measurement.
-  ## "split" is the default behavior for backward compatability with previous versions of influxdb.
+  ## "split" is the default behavior for backward compatibility with previous versions of influxdb.
   collectd_parse_multivalue = "split"
 ```