Unify related documentation verbiage (#11421) (#11425)

opensearch-trigger-bot[bot] · web-flow · commit 7cf0aae63967 · 2025-10-27T12:22:23.000Z
diff --git a/_clients/javascript/helpers.md b/_clients/javascript/helpers.md
@@ -201,5 +201,5 @@ client.helpers.bulk({
 ```
 {% include copy.html %}
 
-## Related articles
+## Related documentation
 https://github.com/opensearch-project/opensearch-js/tree/main/guides
diff --git a/_dashboards/dashboards-assistant/index.md b/_dashboards/dashboards-assistant/index.md
@@ -142,7 +142,7 @@ For information about additional Dashboards Assistant capabilities, see the foll
 - [Generating anomaly detector suggestions]({{site.url}}{{site.baseurl}}/dashboards/dashboards-assistant/suggest-anomaly-detector/)
 - [Generating visualizations from text]({{site.url}}{{site.baseurl}}/dashboards/dashboards-assistant/text-to-visualization/)
 
-## Related articles
+## Related documentation
 
 - [Getting started guide for OpenSearch Assistant in OpenSearch Dashboards](https://github.com/opensearch-project/dashboards-assistant/blob/main/GETTING_STARTED_GUIDE.md)
 - [OpenSearch Assistant configuration through the REST API]({{site.url}}{{site.baseurl}}/ml-commons-plugin/opensearch-assistant/)
diff --git a/_dashboards/visualize/selfhost-maps-server.md b/_dashboards/visualize/selfhost-maps-server.md
@@ -104,7 +104,7 @@ Configure the manifest URL in `opensearch_dashboards.yml`:
 
 Tiles are generated per [Terms of Use for Natural Earth vector map data](https://www.naturalearthdata.com/about/terms-of-use/) and [Copyright and License for OpenStreetMap](https://www.openstreetmap.org/copyright).
 
-## Related articles
+## Related documentation
 
 * [Configuring a Web Map Service (WMS)]({{site.url}}{{site.baseurl}}/dashboards/visualize/maptiles/)
 * [Using coordinate and region maps]({{site.url}}{{site.baseurl}}/dashboards/visualize/geojson-regionmaps/)
diff --git a/_data-prepper/pipelines/configuration/sources/otlp-source.md b/_data-prepper/pipelines/configuration/sources/otlp-source.md
@@ -328,7 +328,7 @@ otlp-pipeline:
 ```
 {% include copy.html %}
 
-## Related pages
+## Related documentation
 
 - [OTel logs source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/otel-logs-source/)
 - [OTel metrics source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/otel-metrics-source/)
diff --git a/_data-prepper/pipelines/expression-syntax.md b/_data-prepper/pipelines/expression-syntax.md
@@ -236,6 +236,6 @@ White space is optional around relational operators, regex equality operators, e
 | `,`                  | Set value delimiter      | No                   | `/a in {200, 202}`<br>`/a in {200,202}`<br>`/a in {200 , 202}` | `/a in {200,}`                        |
 | `typeof`             | Type check operator      | Yes                   | `/a typeof integer`<br>`/a typeof long`<br>`/a typeof string`<br> `/a typeof double`<br> `/a typeof boolean`<br>`/a typeof map`<br>`/a typeof array` |`/a typeof /b`<br>`/a typeof 2`                      |
 
-## Related articles
+## Related documentation
 
 - [Functions]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/functions/)
diff --git a/_data-prepper/pipelines/get-eventtype.md b/_data-prepper/pipelines/get-eventtype.md
@@ -81,6 +81,6 @@ processor:
 ```
 {% include copy.html %}
 
-## Related pages
+## Related documentation
 
 - [OTLP source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/otlp-source/)
diff --git a/_layouts/default.html b/_layouts/default.html
@@ -247,7 +247,7 @@
 
           {% if page.has_children == true and page.has_toc != false %}
             <hr>
-            <h2>Related articles</h2>
+            <h2>Related documentation</h2>
             <ul>
               {% for child in toc_list %}
                 <li>
diff --git a/_mappings/mapping-parameters/analyzer.md b/_mappings/mapping-parameters/analyzer.md
@@ -229,7 +229,7 @@ Term-level queries use the `search_analyzer`, which tokenizes the text and remov
 ```
 
 
-## Related articles
+## Related documentation
 
 - [Text analysis]({{site.url}}{{site.baseurl}}/analyzers/)
 - [Search analyzers]({{site.url}}{{site.baseurl}}/analyzers/search-analyzers/)
diff --git a/_mappings/supported-field-types/sparse-vector.md b/_mappings/supported-field-types/sparse-vector.md
@@ -161,7 +161,7 @@ GET sparse-vector-index/_search
 ```
 {% include copy-curl.html %}
 
-## Related pages
+## Related documentation
 
 - [Neural sparse ANN search]({{site.url}}{{site.baseurl}}/vector-search/ai-search/neural-sparse-ann/)
 - [Neural sparse query]({{site.url}}{{site.baseurl}}/query-dsl/specialized/neural-sparse/)
diff --git a/_migrate-or-upgrade/rolling-upgrade/index.md b/_migrate-or-upgrade/rolling-upgrade/index.md
@@ -275,7 +275,7 @@ To perform a rolling restart, follow the steps outlined in [Performing the upgra
 
 By preserving quorum and restarting nodes sequentially, rolling restarts ensure zero downtime and full data continuity.
 
-## Related articles
+## Related documentation
 
 - [Rolling upgrade lab]({{site.url}}{{site.baseurl}}/migrate-or-upgrade/rolling-upgrade/rolling-upgrade-lab/) -- A hands-on lab with step-by-step instructions for practicing rolling upgrades in a test environment.
 - [OpenSearch configuration]({{site.url}}{{site.baseurl}}/install-and-configure/configuring-opensearch/)
diff --git a/_ml-commons-plugin/agents-tools/tools/query-planning-tool.md b/_ml-commons-plugin/agents-tools/tools/query-planning-tool.md
@@ -526,6 +526,6 @@ Output:
 
 You can run this tool either as part of an agent workflow or independently using the [Execute Tool API]({{site.url}}{{site.baseurl}}/ml-commons-plugin/api/execute-tool/). The Execute Tool API is useful for testing individual tools or performing standalone operations.
 
-## Related pages
+## Related documentation
 
 - [Agentic search]({{site.url}}{{site.baseurl}}/vector-search/ai-search/agentic-search/index)
diff --git a/_observing-your-data/event-analytics.md b/_observing-your-data/event-analytics.md
@@ -114,7 +114,7 @@ With Live Tail, you can select intervals and seamlessly switch between them to c
 
 ![Live Tail]({{site.url}}{{site.baseurl}}/images/live_tail.gif)
 
-## Related articles
+## Related documentation
 
 - [Demonstrating the OpenSearch Assistant toolkit](https://www.youtube.com/watch?v=VTiJtGI2Sr4&t=152s)
 - [Getting started guide for OpenSearch Assistant in OpenSearch Dashboards](https://github.com/opensearch-project/dashboards-assistant/blob/main/GETTING_STARTED_GUIDE.md)
diff --git a/_search-plugins/search-pipelines/agentic-context-processor.md b/_search-plugins/search-pipelines/agentic-context-processor.md
@@ -98,7 +98,7 @@ The response contains the steps taken by the agent to translate the query, the m
 }
 ```
 
-## Related pages
+## Related documentation
 
 - [Agentic search]({{site.url}}{{site.baseurl}}/vector-search/ai-search/agentic-search/index/)
 - [Agentic query]({{site.url}}{{site.baseurl}}/query-dsl/specialized/agentic/)
diff --git a/_search-plugins/search-pipelines/agentic-query-translator-processor.md b/_search-plugins/search-pipelines/agentic-query-translator-processor.md
@@ -125,7 +125,7 @@ The response contains the matching documents:
 }
 ```
 
-## Related pages
+## Related documentation
 
 - [Agentic search queries]({{site.url}}{{site.baseurl}}/vector-search/ai-search/agentic-search/index/)
 - [Agentic query]({{site.url}}{{site.baseurl}}/query-dsl/specialized/agentic/)
diff --git a/_search-plugins/search-pipelines/system-generated-search-processors.md b/_search-plugins/search-pipelines/system-generated-search-processors.md
@@ -63,6 +63,6 @@ The following limitations apply to system-generated processors:
 
 - OpenSearch supports only **one system-generated processor per processor type and execution stage** for a given search request. Since each processor type (request and response) can run at two execution stages (before or after user-defined processors), a single search request can include multiple system-generated processors, as long as they are of different types or run at different execution stages. This limitation ensures deterministic execution order and predictable behavior.
 
-## Related pages
+## Related documentation
 
 - [Vector search with MMR reranking]({{site.url}}{{site.baseurl}}/vector-search/specialized-operations/vector-search-mmr/)
diff --git a/_search-plugins/search-relevance/template-query.md b/_search-plugins/search-relevance/template-query.md
@@ -209,7 +209,7 @@ The response contains the matching document:
 }
 ```
 
-## Related articles
+## Related documentation
 
 - [Template query]({{site.url}}{{site.baseurl}}/query-dsl/specialized/template/)
 - [ML inference search request processor]({{site.url}}{{site.baseurl}}/search-plugins/search-pipelines/ml-inference-search-request/)
diff --git a/_security-analytics/usage/detectors.md b/_security-analytics/usage/detectors.md
@@ -63,5 +63,5 @@ Threat detector actions allow you to stop and start detectors or delete a detect
 1. Select **Delete** in the dropdown list. The Delete detector popup window opens and asks you to verify that you want to delete the detector or detectors.
 1. Select **Cancel** to decline the action. Select **Delete detector** to delete the detector or detectors permanently from the list.
 
-## Related articles
+## Related documentation
 [Creating detectors]({{site.url}}{{site.baseurl}}/security-analytics/sec-analytics-config/detectors-config/)
diff --git a/_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md b/_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md
@@ -610,6 +610,6 @@ We strongly recommend against restoring `.opendistro_security` using an admin ce
 
 For index codec considerations, see [Index codecs]({{site.url}}{{site.baseurl}}/im-plugin/index-codecs/#snapshots).
 
-## Related articles
+## Related documentation
 
 - [Snapshot APIs]({{site.url}}{{site.baseurl}}/api-reference/snapshots/)
diff --git a/_tutorials/faceted-search.md b/_tutorials/faceted-search.md
@@ -1973,7 +1973,7 @@ The response contains only `Clothing` products:
 Similarly, you can aggregate the `Clothing>Shirts` category by specifying `"category_path": "Clothing>Shirts"` in the `prefix` query. Your application code can then strip prefixes to provide a cleaner display (for example, change `Clothing>Shirts` to `Shirts`) if necessary. OpenSearch does the heavy lifting (tokenizing and aggregating), while your application code handles the display formatting by stripping prefixes based on hierarchy level.
 
 
-## Related articles
+## Related documentation
 
 - [Mappings and field types]({{site.url}}{{site.baseurl}}/mappings/)
 - [Supported field types]({{site.url}}{{site.baseurl}}/mappings/supported-field-types/)
diff --git a/_vector-search/specialized-operations/vector-search-mmr.md b/_vector-search/specialized-operations/vector-search-mmr.md
@@ -124,6 +124,6 @@ The following limitations apply to vector search with MMR reranking:
 
 - **Remote index requirements**: When querying remote indexes, you must explicitly provide vector field information (`vector_field_path`, `vector_field_data_type`, and `vector_field_space_type`). Unlike a local index for which OpenSearch can automatically resolve this metadata from the index mapping, the system cannot reliably fetch this information from the remote cluster. Providing these details ensures correct parsing of the vector data and accurate similarity calculations.
 
-## Related pages
+## Related documentation
 
 - [System-generated search processors]({{site.url}}{{site.baseurl}}/search-plugins/search-pipelines/system-generated-search-processors/)
