docs: decoders: trying to fix a table

Signed-off-by: Lynette Miles <[email protected]>
fluent · Sep 11, 2024 · ae9d5d4 · ae9d5d4
1 parent 70ae6ac
commit ae9d5d4
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/pipeline/parsers/decoders.md b/pipeline/parsers/decoders.md
@@ -49,10 +49,10 @@ extra action if the decoder can't succeed.
 
 ### Decoder options
 
-| Name | Description |
-| :--- | :--- |
-| `json` | Handle the field content as a JSON map. If it finds a JSON map, it replaces the content with a structured map. |
-| `escaped` | Decode an escaped string. |
+| Name           | Description |
+| -------------- | ----------- |
+| `json`         | Handle the field content as a JSON map. If it finds a JSON map, it replaces the content with a structured map. |
+| `escaped`      | Decode an escaped string. |
 | `escaped_utf8` | Decode a UTF8 escaped string. |
 
 ### Optional Actions
@@ -61,7 +61,7 @@ If a decoder fails to decode the field or, you want to try another decoder, you
 define an optional action. Available actions are:
 
 | Name | Description |
-| :--- | :--- |
+| -----| ----------- |
 | `try_next` | if the decoder failed, apply the next decoder in the list for the same field. |
 | `do_next` | if the decoder succeeded or failed, apply the next decoder in the list for the same field. |