diff --git a/pipeline/outputs/elasticsearch.md b/pipeline/outputs/elasticsearch.md
index cfb83f572..63c9d4f6c 100644
--- a/pipeline/outputs/elasticsearch.md
+++ b/pipeline/outputs/elasticsearch.md
@@ -230,6 +230,7 @@ If you see `action_request_validation_exception` errors on your pipeline with Fl
 Elastic Cloud is now on version 8 so the type option must be removed by setting `Suppress_Type_Name On` as indicated above.
 
 Without this you will see errors like:
-```
+
+```text
 {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}
 ```
diff --git a/pipeline/outputs/opensearch.md b/pipeline/outputs/opensearch.md
index b7c76faf4..735a903c2 100644
--- a/pipeline/outputs/opensearch.md
+++ b/pipeline/outputs/opensearch.md
@@ -146,3 +146,13 @@ Example configuration:
 ```
 
 Notice that the `Port` is set to `443`, `tls` is enabled, and `AWS_Region` is set.
+
+### Action/metadata contains an unknown parameter type
+
+Similarly to Elastic Cloud, OpenSearch in version 2.0 and above needs to have type option being removed by setting `Suppress_Type_Name On`.
+
+Without this you will see errors like:
+
+```text
+{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"}],"type":"illegal_argument_exception","reason":"Action/metadata line [1] contains an unknown parameter [_type]"},"status":400}
+```