Standardize the term "key-value" (#3283)

* s|key/value|key-value
* Use en dash in prefix to open compound "time series"

api-docs/cloud/swagger.yml

@@ -6446,7 +6446,7 @@ components:
           type: object
           additionalProperties: true
           description: |
-            Enumeration of key/value pairs that respresent parameters to be injected into query (can only specify either this field or extern and not both)
+            Enumeration of key-value pairs that respresent parameters to be injected into query (can only specify either this field or extern and not both)
         dialect:
           $ref: '#/components/schemas/Dialect'
         now:
@@ -6692,7 +6692,7 @@ components:
           items:
             $ref: '#/components/schemas/DictItem'
     DictItem:
-      description: A key/value pair in a dictionary
+      description: A key-value pair in a dictionary
       type: object
       properties:
         type:

api-docs/v2.0/swagger.yml

@@ -7562,7 +7562,7 @@ components:
           type: object
           additionalProperties: true
           description: |
-            Enumeration of key/value pairs that respresent parameters to be injected into query (can only specify either this field or extern and not both)
+            Enumeration of key-value pairs that respresent parameters to be injected into query (can only specify either this field or extern and not both)
         dialect:
           $ref: '#/components/schemas/Dialect'
         now:
@@ -7808,7 +7808,7 @@ components:
           items:
             $ref: '#/components/schemas/DictItem'
     DictItem:
-      description: A key/value pair in a dictionary
+      description: A key-value pair in a dictionary
       type: object
       properties:
         type:

content/influxdb/v1.3/concepts/storage_engine.md

@@ -350,7 +350,7 @@ When the InfluxDB project began, we picked LevelDB as the storage engine because
 We knew that it had great properties for write throughput and everything seemed to "just work".
 
 LevelDB is an implementation of a Log Structured Merge Tree (or LSM Tree) that was built as an open source project at Google.
-It exposes an API for a key/value store where the key space is sorted.
+It exposes an API for a key-value store where the key space is sorted.
 This last part is important for time series data as it allowed us to quickly scan ranges of time as long as the timestamp was in the key.
 
 LSM Trees are based on a log that takes writes and two structures known as Mem Tables and SSTables.

content/influxdb/v1.4/concepts/storage_engine.md

@@ -351,7 +351,7 @@ When the InfluxDB project began, we picked LevelDB as the storage engine because
 We knew that it had great properties for write throughput and everything seemed to "just work".
 
 LevelDB is an implementation of a Log Structured Merge Tree (or LSM Tree) that was built as an open source project at Google.
-It exposes an API for a key/value store where the key space is sorted.
+It exposes an API for a key-value store where the key space is sorted.
 This last part is important for time series data as it allowed us to quickly scan ranges of time as long as the timestamp was in the key.
 
 LSM Trees are based on a log that takes writes and two structures known as Mem Tables and SSTables.

content/influxdb/v1.5/concepts/storage_engine.md

@@ -351,7 +351,7 @@ When the InfluxDB project began, we picked LevelDB as the storage engine because
 We knew that it had great properties for write throughput and everything seemed to "just work".
 
 LevelDB is an implementation of a Log Structured Merge Tree (or LSM Tree) that was built as an open source project at Google.
-It exposes an API for a key/value store where the key space is sorted.
+It exposes an API for a key-value store where the key space is sorted.
 This last part is important for time series data as it allowed us to quickly scan ranges of time as long as the timestamp was in the key.
 
 LSM Trees are based on a log that takes writes and two structures known as Mem Tables and SSTables.

content/influxdb/v1.6/concepts/storage_engine.md

@@ -351,7 +351,7 @@ When the InfluxDB project began, we picked LevelDB as the storage engine because
 We knew that it had great properties for write throughput and everything seemed to "just work".
 
 LevelDB is an implementation of a Log Structured Merge Tree (or LSM Tree) that was built as an open source project at Google.
-It exposes an API for a key/value store where the key space is sorted.
+It exposes an API for a key-value store where the key space is sorted.
 This last part is important for time series data as it allowed us to quickly scan ranges of time as long as the timestamp was in the key.
 
 LSM Trees are based on a log that takes writes and two structures known as Mem Tables and SSTables.

content/influxdb/v2.0/api-guide/client-libraries/nodejs/write.md

@@ -49,7 +49,7 @@ The Javascript client library includes the following convenient features for wri
    - *`YOUR_BUCKET`*: InfluxDB bucket name
 
 3. To apply one or more [tags](/influxdb/v2.0/reference/glossary/#tag) to all points, use the `useDefaultTags()` method.
-   Provide tags as an object of key/value pairs.
+   Provide tags as an object of key-value pairs.
 
     ```js
     writeApi.useDefaultTags({region: 'west'})

content/influxdb/v2.0/reference/config-options.md

@@ -2015,13 +2015,13 @@ storage-series-file-max-concurrent-snapshot-compactions = 0
 Size of the internal cache used in the TSI index to store
 previously calculated series results.
 Cached results are returned quickly rather than needing to be recalculated when
-a subsequent query with the same tag key/value predicate is executed.
+a subsequent query with the same tag key-value predicate is executed.
 Setting this value to `0` will disable the cache and may decrease query performance.
 
 **Default:** `100`
 
 {{% note %}}
-This value should only be increased if the set of regularly used tag key/value
+This value should only be increased if the set of regularly used tag key-value
 predicates across all measurements for a database is larger than 100.
 An increase in cache size may lead to an increase in heap usage.
 {{% /note %}}

content/influxdb/v2.0/reference/internals/file-system-layout.md

@@ -32,7 +32,7 @@ configuration option.
 
 #### Bolt path
 File path to the [Boltdb](https://github.com/boltdb/bolt) database, a file-based
-key-value store for non-time series data, such as InfluxDB users, dashboards, tasks, etc.
+key-value store for non–time series data, such as InfluxDB users, dashboards, tasks, etc.
 To customize this path, use the [bolt-path](/influxdb/v2.0/reference/config-options/#bolt-path)
 configuration option.
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.10/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.11/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.12/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.13/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.14/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.15/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

content/telegraf/v1.16/data_formats/input/logfmt.md

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.16/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

content/telegraf/v1.17/data_formats/input/logfmt.md

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.17/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

content/telegraf/v1.18/data_formats/input/logfmt.md

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.18/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

content/telegraf/v1.19/data_formats/input/json_v2.md

@@ -89,7 +89,7 @@ In the sections that follow these configuration keys are defined in more detail.
 The following describes the high-level approach when parsing arrays and objects:
 
 - **Array**: Every element in an array is treated as a *separate* metric
-- **Object**: Every key/value in a object is treated as a *single* metric
+- **Object**: Every key-value in a object is treated as a *single* metric
 
 When handling nested arrays and objects, the rules above continue to apply as the parser creates metrics.
 When an object has multiple arrays as values,

content/telegraf/v1.19/data_formats/input/logfmt.md

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.19/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

content/telegraf/v1.20/data_formats/input/json_v2.md

@@ -89,7 +89,7 @@ In the sections that follow these configuration keys are defined in more detail.
 The following describes the high-level approach when parsing arrays and objects:
 
 - **Array**: Every element in an array is treated as a *separate* metric
-- **Object**: Every key/value in a object is treated as a *single* metric
+- **Object**: Every key-value in a object is treated as a *single* metric
 
 When handling nested arrays and objects, the rules above continue to apply as the parser creates metrics.
 When an object has multiple arrays as values,

content/telegraf/v1.20/data_formats/input/logfmt.md

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples

content/telegraf/v1.20/data_formats/output/carbon2.md

@@ -53,7 +53,7 @@ metric=weather field=wind location=us-midwest season=summer  100 1234567890
 
 ### Fields and tags with spaces
 
-When a field key or tag key/value have spaces, spaces will be replaced with `_`.
+When a field key or tag key-value have spaces, spaces will be replaced with `_`.
 
 ### Tags with empty values
 

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

@@ -31,7 +31,7 @@ The `logfmt` data format parses [logfmt] data into Telegraf metrics.
 
 ## Metrics
 
-Each key/value pair in the line is added to a new metric as a field.  The type
+Each key-value pair in the line is added to a new metric as a field.  The type
 of the field is automatically determined based on the contents of the value.
 
 ## Examples