Processor plugin docs general config param updates and cleanup

pipeline/processors/content-modifier.md

@@ -68,13 +68,13 @@ The actions specify the type of operation to run on top of a specific key or con
 
 | Action  | Description                                                  |
 | ------- | ------------------------------------------------------------ |
-| `insert`  | Inserts a new key with a value into the target context. The `key` and `value` parameters are required. |
-| `upsert`  | Given a specific key with a value, the `upsert` operation will try to update the value of the key. If the key doesn't exist, a new key will be created. The `key` and `value` parameters are required. |
+| `convert` | Converts the data type of a key value. The `key` and `converted_type` parameters are required. |
 | `delete`  | Deletes a key from the target context. The `key` parameter is required. |
-| `rename`  | Changes the name of a key. The `value` set in the configuration will represent the new name. The `key` and `value` parameters are required. |
-| `hash`    | Replaces the key value with a hash generated by the SHA-256 algorithm, the binary value generated is finally set as a hex string representation. The `key` parameter is required. |
 | `extract` | Extracts the value of a single key as a list of key/value pairs. This action needs the configuration of a regular expression in the  `pattern` property. The `key` and `pattern` parameters are required. |
-| `convert` | Converts the data type of a key value. The `key` and `converted_type` parameters are required. |
+| `hash`    | Replaces the key value with a hash generated by the SHA-256 algorithm, the binary value generated is finally set as a hex string representation. The `key` parameter is required. |
+| `insert`  | Inserts a new key with a value into the target context. The `key` and `value` parameters are required. |
+| `rename`  | Changes the name of a key. The `value` set in the configuration will represent the new name. The `key` and `value` parameters are required. |
+| `upsert`  | Given a specific key with a value, the `upsert` operation will try to update the value of the key. If the key doesn't exist, a new key will be created. The `key` and `value` parameters are required. |
 
 #### Insert example
 

pipeline/processors/cumulative-to-delta.md

@@ -26,11 +26,11 @@ All other metric types (gauges, summaries) pass through unchanged.
 
 | Key | Description | Default |
 | --- | ----------- | ------- |
-| `initial_value` | Controls what happens with the first sample seen for a new series. Accepted values: `auto`, `keep`, `drop`. When unset, the `drop_first` compatibility option is used instead. | `unset` |
 | `drop_first` | Compatibility option. Used only when `initial_value` is `unset`. When `true`, the first sample for each new series is dropped. When `false`, the first sample is emitted as-is. | `true` |
 | `drop_on_reset` | When `true`, drops the sample when a counter or histogram reset is detected (that's when the new value is lower than the last recorded value). | `true` |
-| `max_staleness` | How long to retain per-series state after a series stops reporting. Accepts time values such as `30s`, `5m`, `1h`. Set to `0` to disable staleness eviction. | `1h` |
+| `initial_value` | Controls what happens with the first sample seen for a new series. Accepted values: `auto`, `keep`, `drop`. When unset, the `drop_first` compatibility option is used instead. | `unset` |
 | `max_series` | Maximum number of unique series whose state is tracked in memory. When the limit is reached, the oldest series is evicted. Set to `0` to disable size-based eviction. | `65536` |
+| `max_staleness` | How long to retain per-series state after a series stops reporting. Accepts time values such as `30s`, `5m`, `1h`. Set to `0` to disable staleness eviction. | `1h` |
 
 ### `initial_value` behavior