From 1ce4df0cfd7c5f52fb5dc82604add9965673afdf Mon Sep 17 00:00:00 2001
From: samipak458 <samipak458@gmail.com>
Date: Fri, 6 Oct 2023 21:54:21 +0500
Subject: [PATCH 01/14] Fix APIs File

Signed-off-by: samipak458 <samipak458@gmail.com>
---
 _api-reference/analyze-apis.md                |  2 ++
 _api-reference/cat/cat-aliases.md             |  4 ++--
 _api-reference/cat/cat-allocation.md          |  4 ++--
 _api-reference/cat/cat-cluster_manager.md     |  5 +++--
 _api-reference/cat/cat-count.md               |  4 ++--
 _api-reference/cat/cat-field-data.md          |  4 ++--
 _api-reference/cat/cat-health.md              |  4 ++--
 _api-reference/cat/cat-indices.md             |  4 ++--
 _api-reference/cat/cat-nodeattrs.md           |  4 ++--
 _api-reference/cat/cat-nodes.md               |  4 ++--
 _api-reference/cat/cat-pending-tasks.md       |  4 ++--
 _api-reference/cat/cat-plugins.md             |  4 ++--
 _api-reference/cat/cat-recovery.md            |  4 ++--
 _api-reference/cat/cat-repositories.md        |  4 ++--
 _api-reference/cat/cat-segment-replication.md |  4 ++--
 _api-reference/cat/cat-segments.md            |  4 ++--
 _api-reference/cat/cat-shards.md              |  4 ++--
 _api-reference/cat/cat-snapshots.md           |  4 ++--
 _api-reference/cat/cat-tasks.md               |  4 ++--
 .../cluster-api/cluster-allocation.md         |  4 ++--
 .../cluster-api/cluster-awareness.md          | 20 ++++++++++---------
 .../cluster-api/cluster-decommission.md       | 14 +++++++------
 _api-reference/cluster-api/cluster-health.md  |  4 ++--
 .../cluster-api/cluster-settings.md           |  8 ++++----
 _api-reference/cluster-api/cluster-stats.md   |  5 ++---
 _api-reference/cluster-api/index.md           |  2 ++
 _api-reference/common-parameters.md           | 14 +++++++------
 _api-reference/count.md                       |  5 ++---
 _api-reference/document-apis/bulk.md          |  4 ++--
 .../document-apis/delete-by-query.md          |  4 ++--
 .../document-apis/delete-document.md          |  4 ++--
 _api-reference/document-apis/get-documents.md |  4 ++--
 .../document-apis/index-document.md           |  4 ++--
 _api-reference/document-apis/index.md         |  2 ++
 _api-reference/document-apis/multi-get.md     |  2 +-
 _api-reference/document-apis/reindex.md       |  4 ++--
 .../document-apis/update-by-query.md          |  4 ++--
 .../document-apis/update-document.md          |  4 ++--
 _api-reference/explain.md                     |  4 ++--
 _api-reference/index-apis/alias.md            |  4 ++--
 .../index-apis/clear-index-cache.md           | 16 ++++++++-------
 _api-reference/index-apis/clone.md            |  4 +++-
 _api-reference/index-apis/close-index.md      |  4 ++--
 _api-reference/index-apis/create-index.md     |  2 +-
 _api-reference/index-apis/dangling-index.md   |  4 +++-
 _api-reference/index-apis/delete-index.md     |  4 ++--
 _api-reference/index-apis/exists.md           |  4 ++--
 _api-reference/index-apis/get-index.md        |  4 ++--
 _api-reference/index-apis/get-settings.md     |  4 ++--
 _api-reference/index-apis/index.md            |  2 ++
 _api-reference/index-apis/open-index.md       |  4 ++--
 _api-reference/index-apis/put-mapping.md      |  8 ++++----
 _api-reference/index-apis/shrink-index.md     |  8 +++++---
 _api-reference/index-apis/split.md            |  6 ++++--
 _api-reference/index-apis/stats.md            |  2 ++
 _api-reference/index-apis/update-settings.md  |  4 ++--
 _api-reference/index.md                       |  2 ++
 _api-reference/ingest-apis/create-ingest.md   |  2 ++
 _api-reference/ingest-apis/delete-ingest.md   |  2 ++
 _api-reference/ingest-apis/get-ingest.md      |  2 ++
 _api-reference/ingest-apis/index.md           |  2 ++
 .../ingest-apis/ingest-pipelines.md           |  4 +++-
 .../ingest-apis/ingest-processors.md          |  2 ++
 .../ingest-apis/pipeline-failures.md          |  2 ++
 .../ingest-apis/processors/append.md          |  2 ++
 .../ingest-apis/processors/bytes.md           |  2 ++
 .../ingest-apis/processors/convert.md         |  2 ++
 _api-reference/ingest-apis/processors/csv.md  |  2 ++
 _api-reference/ingest-apis/processors/date.md |  2 ++
 .../ingest-apis/processors/ip2geo.md          | 12 +++++------
 .../ingest-apis/processors/lowercase.md       |  2 ++
 .../ingest-apis/processors/remove.md          |  2 ++
 .../ingest-apis/processors/uppercase.md       |  2 ++
 _api-reference/ingest-apis/simulate-ingest.md |  6 ++++--
 _api-reference/multi-search.md                |  5 ++---
 _api-reference/nodes-apis/index.md            |  4 +++-
 .../nodes-apis/nodes-hot-threads.md           |  4 +++-
 _api-reference/nodes-apis/nodes-info.md       |  4 +++-
 .../nodes-apis/nodes-reload-secure.md         |  2 ++
 _api-reference/nodes-apis/nodes-stats.md      |  2 ++
 _api-reference/nodes-apis/nodes-usage.md      |  2 ++
 _api-reference/popular-api.md                 |  2 ++
 _api-reference/profile.md                     |  2 ++
 _api-reference/rank-eval.md                   |  2 ++
 _api-reference/remote-info.md                 |  2 +-
 .../script-apis/create-stored-script.md       | 12 ++++++-----
 _api-reference/script-apis/delete-script.md   | 10 ++++++----
 _api-reference/script-apis/exec-script.md     | 16 ++++++++-------
 .../script-apis/exec-stored-script.md         | 20 ++++++++++---------
 .../script-apis/get-script-contexts.md        |  6 ++++--
 .../script-apis/get-script-language.md        |  6 ++++--
 .../script-apis/get-stored-script.md          | 10 ++++++----
 _api-reference/script-apis/index.md           |  2 ++
 _api-reference/scroll.md                      |  4 ++--
 _api-reference/search.md                      |  4 ++--
 _api-reference/snapshots/create-repository.md |  6 ++++--
 _api-reference/snapshots/create-snapshot.md   | 12 ++++++-----
 .../snapshots/delete-snapshot-repository.md   |  6 ++++--
 _api-reference/snapshots/delete-snapshot.md   |  4 +++-
 .../snapshots/get-snapshot-repository.md      | 10 ++++++----
 .../snapshots/get-snapshot-status.md          | 10 ++++++----
 _api-reference/snapshots/get-snapshot.md      | 10 ++++++----
 _api-reference/snapshots/index.md             |  2 ++
 _api-reference/snapshots/restore-snapshot.md  | 10 ++++++----
 .../snapshots/verify-snapshot-repository.md   | 10 ++++++----
 _api-reference/tasks.md                       |  2 +-
 _api-reference/units.md                       |  2 ++
 107 files changed, 323 insertions(+), 209 deletions(-)

diff --git a/_api-reference/analyze-apis.md b/_api-reference/analyze-apis.md
index a820dd281e..a8d89bda27 100644
--- a/_api-reference/analyze-apis.md
+++ b/_api-reference/analyze-apis.md
@@ -9,6 +9,8 @@ redirect_from:
 ---
 
 # Analyze API
+**Introduced 1.0**
+{: .label .label-purple }
 
 The Analyze API allows you to perform [text analysis]({{site.url}}{{site.baseurl}}/api-reference/analyze-apis/), which is the process of converting unstructured text into individual tokens (usually words) that are optimized for search.
 
diff --git a/_api-reference/cat/cat-aliases.md b/_api-reference/cat/cat-aliases.md
index 2932dc3b9c..b6fc2ea4ad 100644
--- a/_api-reference/cat/cat-aliases.md
+++ b/_api-reference/cat/cat-aliases.md
@@ -10,12 +10,12 @@ has_children: false
 ---
 
 # CAT aliases
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT aliases operation lists the mapping of aliases to indexes, plus routing and filtering information.
 
-## Example
+**Example**
 
 ```json
 GET _cat/aliases?v
diff --git a/_api-reference/cat/cat-allocation.md b/_api-reference/cat/cat-allocation.md
index 52f8ede913..fde3b8f3a6 100644
--- a/_api-reference/cat/cat-allocation.md
+++ b/_api-reference/cat/cat-allocation.md
@@ -9,12 +9,12 @@ has_children: false
 ---
 
 # CAT allocation
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT allocation operation lists the allocation of disk space for indexes and the number of shards on each node.
 
-## Example
+**Example**
 
 ```json
 GET _cat/allocation?v
diff --git a/_api-reference/cat/cat-cluster_manager.md b/_api-reference/cat/cat-cluster_manager.md
index 152584dd57..d4e68c12af 100644
--- a/_api-reference/cat/cat-cluster_manager.md
+++ b/_api-reference/cat/cat-cluster_manager.md
@@ -9,12 +9,12 @@ has_children: false
 ---
 
 # CAT cluster_manager
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT cluster manager operation lists information that helps identify the elected cluster manager node.
 
-## Example
+**Example**
 
 ```
 GET _cat/cluster_manager?v
@@ -36,6 +36,7 @@ In addition to the [common URL parameters]({{site.url}}{{site.baseurl}}/api-refe
 Parameter | Type | Description
 :--- | :--- | :---
 cluster_manager_timeout | Time | The amount of time to wait for a connection to the cluster manager node. Default is 30 seconds.
+
 ## Response
 
 ```json
diff --git a/_api-reference/cat/cat-count.md b/_api-reference/cat/cat-count.md
index 7896037780..7286c3630e 100644
--- a/_api-reference/cat/cat-count.md
+++ b/_api-reference/cat/cat-count.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT count
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT count operation lists the number of documents in your cluster.
 
-## Example
+**Example**
 
 ```json
 GET _cat/count?v
diff --git a/_api-reference/cat/cat-field-data.md b/_api-reference/cat/cat-field-data.md
index f20d2eaf20..ed7d7d3ead 100644
--- a/_api-reference/cat/cat-field-data.md
+++ b/_api-reference/cat/cat-field-data.md
@@ -9,12 +9,12 @@ redirect_from:
 ---
 
 # CAT fielddata
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT fielddata operation lists the memory size used by each field per node.
 
-## Example
+**Example**
 
 ```json
 GET _cat/fielddata?v
diff --git a/_api-reference/cat/cat-health.md b/_api-reference/cat/cat-health.md
index 6d733435a9..a595462a2b 100644
--- a/_api-reference/cat/cat-health.md
+++ b/_api-reference/cat/cat-health.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT health
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT health operation lists the status of the cluster, how long the cluster has been up, the number of nodes, and other useful information that helps you analyze the health of your cluster.
 
-## Example
+**Example**
 
 ```json
 GET _cat/health?v
diff --git a/_api-reference/cat/cat-indices.md b/_api-reference/cat/cat-indices.md
index 06da384986..535adf0fdf 100644
--- a/_api-reference/cat/cat-indices.md
+++ b/_api-reference/cat/cat-indices.md
@@ -9,12 +9,12 @@ redirect_from:
 ---
 
 # CAT indices
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT indices operation lists information related to indexes, that is, how much disk space they are using, how many shards they have, their health status, and so on.
 
-## Example
+**Example**
 
 ```
 GET _cat/indices?v
diff --git a/_api-reference/cat/cat-nodeattrs.md b/_api-reference/cat/cat-nodeattrs.md
index 72128c391d..d4c9a13248 100644
--- a/_api-reference/cat/cat-nodeattrs.md
+++ b/_api-reference/cat/cat-nodeattrs.md
@@ -9,12 +9,12 @@ redirect_from:
 ---
 
 # CAT nodeattrs
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT nodeattrs operation lists the attributes of custom nodes.
 
-## Example
+**Example**
 
 ```
 GET _cat/nodeattrs?v
diff --git a/_api-reference/cat/cat-nodes.md b/_api-reference/cat/cat-nodes.md
index 188b2938ac..8303b90d27 100644
--- a/_api-reference/cat/cat-nodes.md
+++ b/_api-reference/cat/cat-nodes.md
@@ -10,14 +10,14 @@ redirect_from:
 ---
 
 # CAT nodes
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT nodes operation lists node-level information, including node roles and load metrics.
 
 A few important node metrics are `pid`, `name`, `cluster_manager`, `ip`, `port`, `version`, `build`, `jdk`, along with `disk`, `heap`, `ram`, and `file_desc`.
 
-## Example
+**Example**
 
 ```
 GET _cat/nodes?v
diff --git a/_api-reference/cat/cat-pending-tasks.md b/_api-reference/cat/cat-pending-tasks.md
index 370d624013..73597b8184 100644
--- a/_api-reference/cat/cat-pending-tasks.md
+++ b/_api-reference/cat/cat-pending-tasks.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT pending tasks
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT pending tasks operation lists the progress of all pending tasks, including task priority and time in queue.
 
-## Example
+**Example**
 
 ```
 GET _cat/pending_tasks?v
diff --git a/_api-reference/cat/cat-plugins.md b/_api-reference/cat/cat-plugins.md
index dd7eb292cd..b3bea30c8e 100644
--- a/_api-reference/cat/cat-plugins.md
+++ b/_api-reference/cat/cat-plugins.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT plugins
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT plugins operation lists the names, components, and versions of the installed plugins.
 
-## Example
+**Example**
 
 ```
 GET _cat/plugins?v
diff --git a/_api-reference/cat/cat-recovery.md b/_api-reference/cat/cat-recovery.md
index 5fe83f9268..79deb6c494 100644
--- a/_api-reference/cat/cat-recovery.md
+++ b/_api-reference/cat/cat-recovery.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT recovery
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT recovery operation lists all completed and ongoing index and shard recoveries.
 
-## Example
+**Example**
 
 ```
 GET _cat/recovery?v
diff --git a/_api-reference/cat/cat-repositories.md b/_api-reference/cat/cat-repositories.md
index adafa4c633..d8f2437972 100644
--- a/_api-reference/cat/cat-repositories.md
+++ b/_api-reference/cat/cat-repositories.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT repositories
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT repositories operation lists all completed and ongoing index and shard recoveries.
 
-## Example
+**Example**
 
 ```
 GET _cat/repositories?v
diff --git a/_api-reference/cat/cat-segment-replication.md b/_api-reference/cat/cat-segment-replication.md
index 2b5b5d2e0d..ef64fcd910 100644
--- a/_api-reference/cat/cat-segment-replication.md
+++ b/_api-reference/cat/cat-segment-replication.md
@@ -7,7 +7,7 @@ has_children: false
 ---
 
 # CAT segment replication
-Introduced 2.7
+**Introduced 2.7**
 {: .label .label-purple }
 
 The CAT segment replication operation returns information about active and last completed [segment replication]({{site.url}}{{site.baseurl}}/opensearch/segment-replication/index) events on each replica shard, including related shard-level metrics. These metrics provide information about how far behind the primary shard the replicas are lagging.
@@ -47,7 +47,7 @@ Parameter | Data type  | Description
 `v` | Boolean    | If `true`, the response includes column headings. Defaults to `false`.
 `s` | String     | Specifies to sort the results. For example, `s=shardId:desc` sorts by shardId in descending order.
 
-## Examples 
+### Examples 
 
 The following examples illustrate various segment replication responses.
 
diff --git a/_api-reference/cat/cat-segments.md b/_api-reference/cat/cat-segments.md
index 0fb56d7e26..876a9502cb 100644
--- a/_api-reference/cat/cat-segments.md
+++ b/_api-reference/cat/cat-segments.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT segments
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The cat segments operation lists Lucene segment-level information for each index.
 
-## Example
+**Example**
 
 ```
 GET _cat/segments?v
diff --git a/_api-reference/cat/cat-shards.md b/_api-reference/cat/cat-shards.md
index 5caf07f7af..92b69ed964 100644
--- a/_api-reference/cat/cat-shards.md
+++ b/_api-reference/cat/cat-shards.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT shards
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT shards operation lists the state of all primary and replica shards and how they are distributed.
 
-## Example
+**Example**
 
 ```
 GET _cat/shards?v
diff --git a/_api-reference/cat/cat-snapshots.md b/_api-reference/cat/cat-snapshots.md
index ff45623ab2..974735d349 100644
--- a/_api-reference/cat/cat-snapshots.md
+++ b/_api-reference/cat/cat-snapshots.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT snapshots
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT snapshots operation lists all snapshots for a repository.
 
-## Example
+**Example**
 
 ```
 GET _cat/snapshots?v
diff --git a/_api-reference/cat/cat-tasks.md b/_api-reference/cat/cat-tasks.md
index 07a353390b..4d5faa5de4 100644
--- a/_api-reference/cat/cat-tasks.md
+++ b/_api-reference/cat/cat-tasks.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT tasks
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT tasks operation lists the progress of all tasks currently running on your cluster.
 
-## Example
+**Example**
 
 ```
 GET _cat/tasks?v
diff --git a/_api-reference/cluster-api/cluster-allocation.md b/_api-reference/cluster-api/cluster-allocation.md
index edcd3ebacf..84184eecaa 100644
--- a/_api-reference/cluster-api/cluster-allocation.md
+++ b/_api-reference/cluster-api/cluster-allocation.md
@@ -9,7 +9,7 @@ redirect_from:
 ---
 
 # Cluster allocation explain
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The most basic cluster allocation explain request finds an unassigned shard and explains why it can't be allocated to a node.
@@ -17,7 +17,7 @@ The most basic cluster allocation explain request finds an unassigned shard and
 If you add some options, you can instead get information on a specific shard, including why OpenSearch assigned it to its current node.
 
 
-## Example
+**Example**
 
 ```json
 GET _cluster/allocation/explain?include_yes_decisions=true
diff --git a/_api-reference/cluster-api/cluster-awareness.md b/_api-reference/cluster-api/cluster-awareness.md
index cb9f6c4a86..74129fae06 100644
--- a/_api-reference/cluster-api/cluster-awareness.md
+++ b/_api-reference/cluster-api/cluster-awareness.md
@@ -10,6 +10,8 @@ redirect_from:
 ---
 
 # Cluster routing and awareness
+**Introduced 1.0**
+{: .label .label-purple }
 
 To control the distribution of search or HTTP traffic, you can use the weights per awareness attribute to control the distribution of search or HTTP traffic across zones. This is commonly used for zonal deployments, heterogeneous instances, and routing traffic away from zones during zonal failure.
 
@@ -49,11 +51,11 @@ In the following example request body, `zone_1` and `zone_2` receive 50 requests
 }
 ```
 
-## Example: Weighted round robin search
+#### Example: Weighted round robin search
 
 The following example request creates a round robin shard allocation for search traffic by using an undefined ratio:
 
-### Request
+#### Request
 
 ```json
 PUT /_cluster/routing/awareness/zone/weights
@@ -69,7 +71,7 @@ PUT /_cluster/routing/awareness/zone/weights
 ```
 {% include copy-curl.html %}
 
-### Response
+#### Response
 
 ```
 {
@@ -78,18 +80,18 @@ PUT /_cluster/routing/awareness/zone/weights
 ```
 
 
-## Example: Getting weights for all zones
+#### Example: Getting weights for all zones
 
 The following example request gets weights for all zones.
 
-### Request
+#### Request
 
 ```json
 GET /_cluster/routing/awareness/zone/weights
 ```
 {% include copy-curl.html %}
 
-### Response
+#### Response
 
 OpenSearch responds with the weight of each zone:
 
@@ -106,18 +108,18 @@ OpenSearch responds with the weight of each zone:
 }
 ```
 
-## Example: Deleting weights
+#### Example: Deleting weights
 
 You can remove your weight ratio for each zone using the `DELETE` method.
 
-### Request
+#### Request
 
 ```json
 DELETE /_cluster/routing/awareness/zone/weights
 ```
 {% include copy-curl.html %}
 
-### Response
+#### Response
 
 ```json
 {
diff --git a/_api-reference/cluster-api/cluster-decommission.md b/_api-reference/cluster-api/cluster-decommission.md
index b63720be02..221e551f83 100644
--- a/_api-reference/cluster-api/cluster-decommission.md
+++ b/_api-reference/cluster-api/cluster-decommission.md
@@ -10,6 +10,8 @@ redirect_from:
 ---
 
 # Cluster decommission
+**Introduced 1.0**
+{: .label .label-purple }
 
 The cluster decommission operation adds support decommissioning based on awareness. It greatly benefits multi-zone deployments, where awareness attributes, such as `zones`, can aid in applying new upgrades to a cluster in a controlled fashion. This is especially useful during outages, in which case, you can decommission the unhealthy zone to prevent replication requests from stalling and prevent your request backlog from becoming too large.
 
@@ -32,11 +34,11 @@ awareness_attribute_name | String | The name of awareness attribute, usually `zo
 awareness_attribute_value | String | The value of the awareness attribute. For example, if you have shards allocated in two different zones, you can give each zone a value of `zone-a` or `zoneb`. The cluster decommission operation decommissions the zone listed in the method.
 
 
-## Example: Decommissioning and recommissioning a zone
+#### Example: Decommissioning and recommissioning a zone
 
 You can use the following example requests to decommission and recommission a zone:
 
-### Request
+#### Request
 
 The following example request decommissions `zone-a`:
 
@@ -52,7 +54,7 @@ DELETE /_cluster/decommission/awareness
 ```
 {% include copy-curl.html %}
 
-### Response
+#### Response
 
 
 ```json
@@ -61,18 +63,18 @@ DELETE /_cluster/decommission/awareness
 }
 ```
 
-## Example: Getting zone decommission status
+#### Example: Getting zone decommission status
 
 The following example requests returns the decommission status of all zones.
 
-### Request
+#### Request
 
 ```json
 GET /_cluster/decommission/awareness/zone/_status
 ```
 {% include copy-curl.html %}
 
-### Response
+#### Response
 
 ```json
 {
diff --git a/_api-reference/cluster-api/cluster-health.md b/_api-reference/cluster-api/cluster-health.md
index b341f31070..570216f602 100644
--- a/_api-reference/cluster-api/cluster-health.md
+++ b/_api-reference/cluster-api/cluster-health.md
@@ -10,14 +10,14 @@ redirect_from:
 ---
 
 # Cluster health
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The most basic cluster health request returns a simple status of the health of your cluster. OpenSearch expresses cluster health in three colors: green, yellow, and red. A green status means all primary shards and their replicas are allocated to nodes. A yellow status means all primary shards are allocated to nodes, but some replicas aren't. A red status means at least one primary shard is not allocated to any node.
 
 To get the status of a specific index, provide the index name.
 
-## Example
+**Example**
 
 This request waits 50 seconds for the cluster to reach the yellow status or better:
 
diff --git a/_api-reference/cluster-api/cluster-settings.md b/_api-reference/cluster-api/cluster-settings.md
index 095f4f82cc..5f0cc15a5f 100644
--- a/_api-reference/cluster-api/cluster-settings.md
+++ b/_api-reference/cluster-api/cluster-settings.md
@@ -9,19 +9,19 @@ redirect_from:
 ---
 
 # Cluster settings
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The cluster settings operation lets you check the current settings for your cluster, review default settings, and change settings. When you update a setting using the API, OpenSearch applies it to all nodes in the cluster.
 
-### Path and HTTP methods
+## Path and HTTP methods
 
 ```
 GET _cluster/settings
 PUT _cluster/settings
 ```
 
-### Path parameters
+## Path parameters
 
 All cluster setting parameters are optional.
 
@@ -51,7 +51,7 @@ PUT _cluster/settings
 }
 ```
 
-### Request fields
+## Request fields
 
 The GET operation has no request body options. All cluster setting field parameters are optional.
 
diff --git a/_api-reference/cluster-api/cluster-stats.md b/_api-reference/cluster-api/cluster-stats.md
index 1083ff1dc5..9da37b3b57 100644
--- a/_api-reference/cluster-api/cluster-stats.md
+++ b/_api-reference/cluster-api/cluster-stats.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # Cluster stats
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The cluster stats API operation returns statistics about your cluster.
 
-## Examples
+**Examples**
 
 ```json
 GET _cluster/stats/nodes/_cluster_manager
@@ -29,7 +29,6 @@ GET _cluster/stats
 GET _cluster/stats/nodes/<node-filters>
 ```
 
-
 ## URL parameters
 
 All cluster stats parameters are optional.
diff --git a/_api-reference/cluster-api/index.md b/_api-reference/cluster-api/index.md
index 9ce04695f6..5a67c783ea 100644
--- a/_api-reference/cluster-api/index.md
+++ b/_api-reference/cluster-api/index.md
@@ -8,5 +8,7 @@ redirect_from:
 ---
 
 # Cluster APIs
+**Introduced 1.0**
+{: .label .label-purple }|
 
 The cluster APIs allow you to manage your cluster. You can use them to check cluster health, modify settings, retrieve statistics, and more.
diff --git a/_api-reference/common-parameters.md b/_api-reference/common-parameters.md
index eb0fae8cf7..347d38a0de 100644
--- a/_api-reference/common-parameters.md
+++ b/_api-reference/common-parameters.md
@@ -7,6 +7,8 @@ redirect_from:
 ---
 
 # Common REST parameters
+**Introduced 1.0**
+{: .label .label-purple }
 
 OpenSearch supports the following parameters for all REST operations:
 
@@ -14,7 +16,7 @@ OpenSearch supports the following parameters for all REST operations:
 
 To convert output units to human-readable values (for example, `1h` for 1 hour and `1kb` for 1,024 bytes), add `?human=true` to the request URL.  
 
-### Example request
+#### Example request
 
 The following request requires response values to be in human-readable format:
 
@@ -27,7 +29,7 @@ GET <index_name>/_search?human=true
 
 To get back JSON responses in a readable format, add `?pretty=true` to the request URL.  
 
-### Example request
+#### Example request
 
 The following request requires the response to be displayed in pretty JSON format:
 
@@ -40,7 +42,7 @@ GET <index_name>/_search?pretty=true
 
 To specify the type of content in the request body, use the `Content-Type` key name in the request header. Most operations support JSON, YAML, and CBOR formats.  
 
-### Example request
+#### Example request
 
 The following request specifies JSON format for the request body:
 
@@ -54,7 +56,7 @@ curl -H "Content-type: application/json" -XGET localhost:9200/_scripts/<template
 If the client library does not accept a request body for non-POST requests, use the `source` query string parameter to pass the request body. Also, specify the `source_content_type` parameter with a supported media type such as `application/json`.  
 
 
-### Example request
+#### Example request
 
 The following request searches the documents in the `shakespeare` index for a specific field and value:
 
@@ -67,7 +69,7 @@ GET shakespeare/search?source={"query":{"exists":{"field":"speaker"}}}&source_co
 
 To include the error stack trace in the response when an exception is raised, add `error_trace=true` to the request URL.  
 
-### Example request
+#### Example request
 
 The following request sets `error_trace` to `true` so that the response returns exception-triggered errors:
 
@@ -80,7 +82,7 @@ GET <index_name>/_search?error_trace=true
 
 To reduce the response size use the `filter_path` parameter to filter the fields that are returned. This parameter takes a comma-separated list of filters. It supports using wildcards to match any field or part of a field's name. You can also exclude fields with `-`.  
 
-### Example request
+#### Example request
 
 The following request specifies filters to limit the fields returned in the response:
 
diff --git a/_api-reference/count.md b/_api-reference/count.md
index 16959f833e..a95b948e8d 100644
--- a/_api-reference/count.md
+++ b/_api-reference/count.md
@@ -7,14 +7,13 @@ redirect_from:
 ---
 
 # Count
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The count API gives you quick access to the number of documents that match a query.
 You can also use it to check the document count of an index, data stream, or cluster.
 
-
-## Example
+**Example**
 
 To see the number of documents that match a query:
 
diff --git a/_api-reference/document-apis/bulk.md b/_api-reference/document-apis/bulk.md
index 657c1eb45f..83a0754301 100644
--- a/_api-reference/document-apis/bulk.md
+++ b/_api-reference/document-apis/bulk.md
@@ -8,7 +8,7 @@ redirect_from:
 ---
 
 # Bulk
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The bulk operation lets you add, update, or delete multiple documents in a single request. Compared to individual OpenSearch indexing requests, the bulk operation has significant performance benefits. Whenever practical, we recommend batching indexing operations into bulk requests.
@@ -17,7 +17,7 @@ The bulk operation lets you add, update, or delete multiple documents in a singl
 Beginning in OpenSearch 2.9, when indexing documents using the bulk operation, the document `_id` must be 512 bytes or less in size.
 {: .note}
 
-## Example
+**Example**
 
 ```json
 POST _bulk
diff --git a/_api-reference/document-apis/delete-by-query.md b/_api-reference/document-apis/delete-by-query.md
index d8e28762d0..d42656b0cc 100644
--- a/_api-reference/document-apis/delete-by-query.md
+++ b/_api-reference/document-apis/delete-by-query.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Delete by query
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple}
 
 You can include a query as part of your delete request so OpenSearch deletes all documents that match that query.
 
-## Example
+**Example**
 
 ```json
 POST sample-index1/_delete_by_query
diff --git a/_api-reference/document-apis/delete-document.md b/_api-reference/document-apis/delete-document.md
index f0bbd151a1..237a7fcb50 100644
--- a/_api-reference/document-apis/delete-document.md
+++ b/_api-reference/document-apis/delete-document.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Delete document
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 If you no longer need a document in your index, you can use the delete document API operation to delete it.
 
-## Example
+**Example**
 
 ```
 DELETE /sample-index1/_doc/1
diff --git a/_api-reference/document-apis/get-documents.md b/_api-reference/document-apis/get-documents.md
index 2c5c162da9..aba1f0849d 100644
--- a/_api-reference/document-apis/get-documents.md
+++ b/_api-reference/document-apis/get-documents.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Get document
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 After adding a JSON document to your index, you can use the get document API operation to retrieve the document's information and data.
 
-## Example
+**Example**
 
 ```json
 GET sample-index1/_doc/1
diff --git a/_api-reference/document-apis/index-document.md b/_api-reference/document-apis/index-document.md
index 05cb787e92..bff8dcbe5c 100644
--- a/_api-reference/document-apis/index-document.md
+++ b/_api-reference/document-apis/index-document.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Index document
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple}
 
 Before you can search for data, you must first add documents. This operation adds a single document to your index.
 
-## Example
+**Example**
 
 ```json
 PUT sample-index/_doc/1
diff --git a/_api-reference/document-apis/index.md b/_api-reference/document-apis/index.md
index 4713bcb809..9444efa5b9 100644
--- a/_api-reference/document-apis/index.md
+++ b/_api-reference/document-apis/index.md
@@ -8,6 +8,8 @@ redirect_from:
 ---
 
 # Document APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 The document APIs allow you to handle documents relative to your index, such as adding, updating, and deleting documents.
 
diff --git a/_api-reference/document-apis/multi-get.md b/_api-reference/document-apis/multi-get.md
index ff2e6de59b..16e9ceeb95 100644
--- a/_api-reference/document-apis/multi-get.md
+++ b/_api-reference/document-apis/multi-get.md
@@ -8,7 +8,7 @@ redirect_from:
 ---
 
 # Multi-get documents
-Introduced 1.0 
+**Introduced 1.0**
 {: .label .label-purple }
 
 The multi-get operation allows you to run multiple GET operations in one request, so you can get back all documents that match your criteria.
diff --git a/_api-reference/document-apis/reindex.md b/_api-reference/document-apis/reindex.md
index 845042f3f6..3bb3c69e9f 100644
--- a/_api-reference/document-apis/reindex.md
+++ b/_api-reference/document-apis/reindex.md
@@ -9,12 +9,12 @@ redirect_from:
 ---
 
 # Reindex document
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple}
 
 The reindex document API operation lets you copy all or a subset of your data from a source index into a destination index.
 
-## Example
+**Example**
 
 ```json
 POST /_reindex
diff --git a/_api-reference/document-apis/update-by-query.md b/_api-reference/document-apis/update-by-query.md
index 528d30e156..c6bef9f733 100644
--- a/_api-reference/document-apis/update-by-query.md
+++ b/_api-reference/document-apis/update-by-query.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Update by query
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple}
 
 You can include a query and a script as part of your update request so OpenSearch can run the script to update all of the documents that match the query.
 
-## Example
+**Example**
 
 ```json
 POST test-index1/_update_by_query
diff --git a/_api-reference/document-apis/update-document.md b/_api-reference/document-apis/update-document.md
index 7354277eaf..fad761af37 100644
--- a/_api-reference/document-apis/update-document.md
+++ b/_api-reference/document-apis/update-document.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Update document
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 If you need to update a document's fields in your index, you can use the update document API operation. You can do so by specifying the new data you want in your index or by including a script in your request body, which OpenSearch runs to update the document.
 
-## Example
+**Example**
 
 ```json
 POST /sample-index1/_update/1
diff --git a/_api-reference/explain.md b/_api-reference/explain.md
index 97f5f622de..179a08c9de 100644
--- a/_api-reference/explain.md
+++ b/_api-reference/explain.md
@@ -7,7 +7,7 @@ redirect_from:
 ---
 
 # Explain
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 Wondering why a specific document ranks higher (or lower) for a query? You can use the explain API for an explanation of how the relevance score (`_score`) is calculated for every result.
@@ -18,7 +18,7 @@ The explain API is an expensive operation in terms of both resources and time. O
 {: .warning }
 
 
-## Example
+**Example**
 
 To see the explain output for all results, set the `explain` flag to `true` either in the URL or in the body of the request:
 
diff --git a/_api-reference/index-apis/alias.md b/_api-reference/index-apis/alias.md
index 96272b4698..2007fd9ea5 100644
--- a/_api-reference/index-apis/alias.md
+++ b/_api-reference/index-apis/alias.md
@@ -9,13 +9,13 @@ redirect_from:
 ---
 
 # Alias
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 An alias is a virtual pointer that you can use to reference one or more indexes. Creating and updating aliases are atomic operations, so you can reindex your data and point an alias at it without any downtime.
 
 
-## Example
+**Example**
 
 ```json
 POST _aliases
diff --git a/_api-reference/index-apis/clear-index-cache.md b/_api-reference/index-apis/clear-index-cache.md
index 3f4e93e67b..55a5ce85d5 100644
--- a/_api-reference/index-apis/clear-index-cache.md
+++ b/_api-reference/index-apis/clear-index-cache.md
@@ -6,6 +6,8 @@ nav_order: 10
 ---
 
 # Clear cache
+**Introduced 1.0**
+{: .label .label-purple }
 
 The clear cache API operation clears the caches of one or more indexes. For data streams, the API clears the caches of the stream’s backing indexes.
 
@@ -36,11 +38,11 @@ All query parameters are optional.
 | query | Boolean | If `true`, clears the query cache. Defaults to `true`. |
 | request | Boolean | If `true`, clears the request cache. Defaults to `true`. |
 
-## Example requests
+#### Example requests
 
 The following example requests show multiple clear cache API uses.
 
-### Clear a specific cache
+##### Clear a specific cache
 
 The following request clears the fields cache only:
 
@@ -67,7 +69,7 @@ POST /my-index/_cache/clear?request=true
 ```
 {% include copy-curl.html %}
 
-### Clear the cache for specific fields
+#### Clear the cache for specific fields
 
 The following request clears the fields caches of `fielda` and `fieldb`:
 
@@ -76,7 +78,7 @@ POST /my-index/_cache/clear?fields=fielda,fieldb
 ```
 {% include copy-curl.html %}
 
-### Clear caches for specific data streams or indexes
+#### Clear caches for specific data streams or indexes
 
 The following request clears the cache for two specific indexes:
 
@@ -85,7 +87,7 @@ POST /my-index,my-index2/_cache/clear
 ```
 {% include copy-curl.html %}
 
-### Clear caches for all data streams and indexes
+#### Clear caches for all data streams and indexes
 
 The following request clears the cache for all data streams and indexes:
 
@@ -94,7 +96,7 @@ POST /_cache/clear
 ```
 {% include copy-curl.html %}
 
-### Clear unused entries from the cache on search-capable nodes
+#### Clear unused entries from the cache on search-capable nodes
 
 ```json
 POST /*/_cache/clear?file=true 
@@ -115,7 +117,7 @@ The `POST /books,hockey/_cache/clear` request returns the following fields:
 }
 ```
 
-#### Response fields
+## Response fields
 
 The `POST /books,hockey/_cache/clear` request returns the following response fields:
 
diff --git a/_api-reference/index-apis/clone.md b/_api-reference/index-apis/clone.md
index 52e558e48d..fc39ca1df3 100644
--- a/_api-reference/index-apis/clone.md
+++ b/_api-reference/index-apis/clone.md
@@ -8,10 +8,12 @@ redirect_from:
 ---
 
 # Clone index
+**Introduced 1.0**
+{: .label .label-purple }
 
 The clone index API operation clones all data in an existing read-only index into a new index. The new index cannot already exist.
 
-## Example
+**Example**
 
 ```json
 PUT /sample-index1/_clone/cloned-index1
diff --git a/_api-reference/index-apis/close-index.md b/_api-reference/index-apis/close-index.md
index 28675f1c98..6f6868a764 100644
--- a/_api-reference/index-apis/close-index.md
+++ b/_api-reference/index-apis/close-index.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Close index
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The close index API operation closes an index. Once an index is closed, you cannot add data to it or search for any data within the index.
 
-## Example
+**Example**
 
 ```json
 POST /sample-index/_close
diff --git a/_api-reference/index-apis/create-index.md b/_api-reference/index-apis/create-index.md
index 6a798fa87e..5e0d504fcc 100644
--- a/_api-reference/index-apis/create-index.md
+++ b/_api-reference/index-apis/create-index.md
@@ -9,7 +9,7 @@ redirect_from:
 ---
 
 # Create index
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 While you can create an index by using a document as a base, you can also create an empty index for later use.
diff --git a/_api-reference/index-apis/dangling-index.md b/_api-reference/index-apis/dangling-index.md
index 5f9c184d66..e05a588b53 100644
--- a/_api-reference/index-apis/dangling-index.md
+++ b/_api-reference/index-apis/dangling-index.md
@@ -6,6 +6,8 @@ nav_order: 30
 ---
 
 # Dangling indexes API
+**Introduced 1.0**
+{: .label .label-purple }
 
 After a node joins a cluster, dangling indexes occur if any shards exist in the node's local directory that do not already exist in the cluster. Dangling indexes can be listed, deleted, or imported.
 
@@ -47,7 +49,7 @@ accept_data_loss | Boolean | Must be set to `true` for an `import` or `delete` b
 timeout | Time units | The amount of time to wait for a response. If no response is received in the defined time period, an error is returned. Default is `30` seconds.
 cluster_manager_timeout | Time units | The amount of time to wait for a connection to the cluster manager. If no response is received in the defined time period, an error is returned. Default is `30` seconds.
 
-## Examples
+#### Examples
 
 The following are example requests and a example response.
 
diff --git a/_api-reference/index-apis/delete-index.md b/_api-reference/index-apis/delete-index.md
index 91b991b85d..fa1014429d 100644
--- a/_api-reference/index-apis/delete-index.md
+++ b/_api-reference/index-apis/delete-index.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Delete index
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 If you no longer need an index, you can use the delete index API operation to delete it.
 
-## Example
+**Example**
 
 ```json
 DELETE /sample-index
diff --git a/_api-reference/index-apis/exists.md b/_api-reference/index-apis/exists.md
index f06745157e..e95dcb7b06 100644
--- a/_api-reference/index-apis/exists.md
+++ b/_api-reference/index-apis/exists.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Index exists
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The index exists API operation returns whether or not an index already exists.
 
-## Example
+**Example**
 
 ```json
 HEAD /sample-index
diff --git a/_api-reference/index-apis/get-index.md b/_api-reference/index-apis/get-index.md
index f47f737826..8f2ff44162 100644
--- a/_api-reference/index-apis/get-index.md
+++ b/_api-reference/index-apis/get-index.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Get index
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 You can use the get index API operation to return information about an index.
 
-## Example
+**Example**
 
 ```json
 GET /sample-index
diff --git a/_api-reference/index-apis/get-settings.md b/_api-reference/index-apis/get-settings.md
index c6689a54a9..3ace352875 100644
--- a/_api-reference/index-apis/get-settings.md
+++ b/_api-reference/index-apis/get-settings.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Get settings
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The get settings API operation returns all the settings in your index.
 
-## Example
+**Example**
 
 ```json
 GET /sample-index1/_settings
diff --git a/_api-reference/index-apis/index.md b/_api-reference/index-apis/index.md
index 2428bcb3e0..4c059b3e48 100644
--- a/_api-reference/index-apis/index.md
+++ b/_api-reference/index-apis/index.md
@@ -8,6 +8,8 @@ redirect_from:
 ---
 
 # Index APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 The index API operations let you interact with indexes in your cluster. Using these operations, you can create, delete, close, and complete other index-related operations.
 
diff --git a/_api-reference/index-apis/open-index.md b/_api-reference/index-apis/open-index.md
index 90a4491898..25e6f1aaac 100644
--- a/_api-reference/index-apis/open-index.md
+++ b/_api-reference/index-apis/open-index.md
@@ -8,12 +8,12 @@ redirect_from:
 ---
 
 # Open index
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The open index API operation opens a closed index, letting you add or search for data within the index.
 
-## Example
+**Example**
 
 ```json
 POST /sample-index/_open
diff --git a/_api-reference/index-apis/put-mapping.md b/_api-reference/index-apis/put-mapping.md
index dfbbdc139c..59c7bd6b00 100644
--- a/_api-reference/index-apis/put-mapping.md
+++ b/_api-reference/index-apis/put-mapping.md
@@ -9,7 +9,7 @@ redirect_from:
 ---
 
 # Create or update mappings
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 If you want to create or add mappings and fields to an index, you can use the put mapping API operation. For an existing mapping, this operation updates the mapping.
@@ -43,9 +43,9 @@ The request body must contain `properties`, which has all of the mappings that y
 }
 ```
 
-## Optional request body fields
+#### Optional request body fields
 
-### dynamic
+#### dynamic
 
 You can make the document structure match the structure of the index mapping by setting the `dynamic` request body field to `strict`, as seen in the following example:
 
@@ -60,7 +60,7 @@ You can make the document structure match the structure of the index mapping by
 }
 ```
 
-## Optional query parameters
+#### Optional query parameters
 
 Optionally, you can add query parameters to make a more specific request. For example, to skip any missing or closed indexes in the response, you can add the `ignore_unavailable` query parameter to your request as follows:
 
diff --git a/_api-reference/index-apis/shrink-index.md b/_api-reference/index-apis/shrink-index.md
index 0476e19c68..13c803def0 100644
--- a/_api-reference/index-apis/shrink-index.md
+++ b/_api-reference/index-apis/shrink-index.md
@@ -8,10 +8,12 @@ redirect_from:
 ---
 
 # Shrink index
+**Introduced 1.0**
+{: .label .label-purple }
 
 The shrink index API operation moves all of your data in an existing index into a new index with fewer primary shards.
 
-## Example
+**Example**
 
 ```json
 POST /my-old-index/_shrink/my-new-index
@@ -66,7 +68,7 @@ alias | Object | Sets an alias for the target index. Can have the fields `filter
 settings | Object | Index settings you can apply to your target index. See [Index Settings]({{site.url}}{{site.baseurl}}/im-plugin/index-settings/).
 [max_shard_size](#the-max_shard_size-parameter) | Bytes | Specifies the maximum size of a primary shard in the target index. Because `max_shard_size` conflicts with the `index.number_of_shards` setting, you cannot set both of them at the same time. 
 
-### The `max_shard_size` parameter
+#### The `max_shard_size` parameter
 
 The `max_shard_size` parameter specifies the maximum size of a primary shard in the target index. OpenSearch uses `max_shard_size` and the total storage for all primary shards in the source index to calculate the number of primary shards and their size for the target index. 
 
@@ -80,6 +82,6 @@ The maximum number of primary shards for the target index is equal to the number
 The minimum number of primary shards for the target index is 1.
 {: .note}
 
-## Index codec considerations
+#### Index codec considerations
 
 For index codec considerations, see [Index codecs]({{site.url}}{{site.baseurl}}/im-plugin/index-codecs/#splits-and-shrinks).
\ No newline at end of file
diff --git a/_api-reference/index-apis/split.md b/_api-reference/index-apis/split.md
index fcf29998a9..66025253a4 100644
--- a/_api-reference/index-apis/split.md
+++ b/_api-reference/index-apis/split.md
@@ -8,10 +8,12 @@ redirect_from:
 ---
 
 # Split index
+**Introduced 1.0**
+{: .label .label-purple }
 
 The split index API operation splits an existing read-only index into a new index, cutting each primary shard into some amount of primary shards in the new index.
 
-## Example
+**Example**
 
 ```json
 PUT /sample-index1/_split/split-index1
@@ -74,6 +76,6 @@ The split index API operation creates a new target index, so you can specify any
 }
 ```
 
-## Index codec considerations
+#### Index codec considerations
 
 For index codec considerations, see [Index codecs]({{site.url}}{{site.baseurl}}/im-plugin/index-codecs/#splits-and-shrinks).
\ No newline at end of file
diff --git a/_api-reference/index-apis/stats.md b/_api-reference/index-apis/stats.md
index baffd2edb0..eb7349d3c5 100644
--- a/_api-reference/index-apis/stats.md
+++ b/_api-reference/index-apis/stats.md
@@ -6,6 +6,8 @@ nav_order: 72
 ---
 
 # Index Stats 
+**Introduced 1.0**
+{: .label .label-purple }
 
 The Index Stats API provides index statistics. For data streams, the API provides statistics for the stream's backing indexes. By default, the returned statistics are index level. To receive shard-level statistics, set the `level` parameter to `shards`.
 
diff --git a/_api-reference/index-apis/update-settings.md b/_api-reference/index-apis/update-settings.md
index ef20e395f6..c742e1c291 100644
--- a/_api-reference/index-apis/update-settings.md
+++ b/_api-reference/index-apis/update-settings.md
@@ -8,14 +8,14 @@ redirect_from:
 ---
 
 # Update settings
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 You can use the update settings API operation to update index-level settings. You can change dynamic index settings at any time, but static settings cannot be changed after index creation. For more information about static and dynamic index settings, see [Create index]({{site.url}}{{site.baseurl}}/api-reference/index-apis/create-index/).
 
 Aside from the static and dynamic index settings, you can also update individual plugins' settings. To get the full list of updatable settings, run `GET <target-index>/_settings?include_defaults=true`.
 
-## Example
+**Example**
 
 ```json
 PUT /sample-index1/_settings
diff --git a/_api-reference/index.md b/_api-reference/index.md
index 5022502c52..9913845824 100644
--- a/_api-reference/index.md
+++ b/_api-reference/index.md
@@ -10,6 +10,8 @@ redirect_from:
 ---
 
 # REST API reference
+**Introduced 1.0**
+{: .label .label-purple }
 
 You can use REST APIs for most operations in OpenSearch. In this reference, we provide a description of the API, and details that include the paths and HTTP methods, supported parameters, and example requests and responses.
 
diff --git a/_api-reference/ingest-apis/create-ingest.md b/_api-reference/ingest-apis/create-ingest.md
index 38e9b32b54..ff1a7d77e0 100644
--- a/_api-reference/ingest-apis/create-ingest.md
+++ b/_api-reference/ingest-apis/create-ingest.md
@@ -9,6 +9,8 @@ redirect_from:
 ---
 
 # Create pipeline
+**Introduced 1.0**
+{: .label .label-purple }
 
 Use the create pipeline API operation to create or update pipelines in OpenSearch. Note that the pipeline requires you to define at least one processor that specifies how to change the documents. 
 
diff --git a/_api-reference/ingest-apis/delete-ingest.md b/_api-reference/ingest-apis/delete-ingest.md
index 59383fb0aa..03de8d3fac 100644
--- a/_api-reference/ingest-apis/delete-ingest.md
+++ b/_api-reference/ingest-apis/delete-ingest.md
@@ -9,6 +9,8 @@ redirect_from:
 ---
 
 # Delete pipeline
+**Introduced 1.0**
+{: .label .label-purple }
 
 Use the following request to delete a pipeline. 
 
diff --git a/_api-reference/ingest-apis/get-ingest.md b/_api-reference/ingest-apis/get-ingest.md
index a56d7da584..65a47b70f4 100644
--- a/_api-reference/ingest-apis/get-ingest.md
+++ b/_api-reference/ingest-apis/get-ingest.md
@@ -9,6 +9,8 @@ redirect_from:
 ---
 
 # Get pipeline
+**Introduced 1.0**
+{: .label .label-purple }
 
 Use the get ingest pipeline API operation to retrieve all the information about the pipeline.
 
diff --git a/_api-reference/ingest-apis/index.md b/_api-reference/ingest-apis/index.md
index 462c699fc2..d656087404 100644
--- a/_api-reference/ingest-apis/index.md
+++ b/_api-reference/ingest-apis/index.md
@@ -8,6 +8,8 @@ redirect_from:
 ---
 
 # Ingest APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 Ingest APIs are a valuable tool for loading data into a system. Ingest APIs work together with [ingest pipelines]({{site.url}}{{site.baseurl}}/api-reference/ingest-apis/ingest-pipelines/) and [ingest processors]({{site.url}}{{site.baseurl}}/api-reference/ingest-apis/ingest-processors/) to process or transform data from a variety of sources and in a variety of formats. 
 
diff --git a/_api-reference/ingest-apis/ingest-pipelines.md b/_api-reference/ingest-apis/ingest-pipelines.md
index 38ea3fc7d5..02a2f9ecbc 100644
--- a/_api-reference/ingest-apis/ingest-pipelines.md
+++ b/_api-reference/ingest-apis/ingest-pipelines.md
@@ -7,6 +7,8 @@ nav_order: 5
 ---
 
 # Ingest pipelines
+**Introduced 1.0**
+{: .label .label-purple }
 
 An _ingest pipeline_ is a sequence of _processors_ that are applied to documents as they are ingested into an index. Each [processor]({{site.url}}{{site.baseurl}}/api-reference/ingest-apis/ingest-processors/) in a pipeline performs a specific task, such as filtering, transforming, or enriching data. 
 
@@ -33,7 +35,7 @@ A _pipeline definition_ describes the sequence of an ingest pipeline and can be
 }
 ```
 
-### Request body fields
+#### Request body fields
 
 Field | Required | Type | Description
 :--- | :--- | :--- | :---
diff --git a/_api-reference/ingest-apis/ingest-processors.md b/_api-reference/ingest-apis/ingest-processors.md
index 5a9a5e0d41..a32c6b7fb9 100644
--- a/_api-reference/ingest-apis/ingest-processors.md
+++ b/_api-reference/ingest-apis/ingest-processors.md
@@ -7,6 +7,8 @@ has_children: true
 ---
 
 # Ingest processors
+**Introduced 1.0**
+{: .label .label-purple }
 
 Ingest processors are a core component of [ingest pipelines]({{site.url}}{{site.baseurl}}/api-reference/ingest-apis/ingest-pipelines/) because they preprocess documents before indexing. For example, you can remove fields, extract values from text, convert data formats, or append additional information.
 
diff --git a/_api-reference/ingest-apis/pipeline-failures.md b/_api-reference/ingest-apis/pipeline-failures.md
index f8814f39c2..8a87d7231c 100644
--- a/_api-reference/ingest-apis/pipeline-failures.md
+++ b/_api-reference/ingest-apis/pipeline-failures.md
@@ -7,6 +7,8 @@ nav_order: 15
 ---
 
 # Handling pipeline failures
+**Introduced 1.0**
+{: .label .label-purple }
 
 Each ingest pipeline consists of a series of processors that are applied to the documents in sequence. If a processor fails, the entire pipeline will fail. You have two options for handling failures:
 
diff --git a/_api-reference/ingest-apis/processors/append.md b/_api-reference/ingest-apis/processors/append.md
index dee484a6aa..24973275e9 100644
--- a/_api-reference/ingest-apis/processors/append.md
+++ b/_api-reference/ingest-apis/processors/append.md
@@ -7,6 +7,8 @@ nav_order: 10
 ---
 
 # Append
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `append` processor is used to add values to a field:
 - If the field is an array, the `append` processor appends the specified values to that array.
diff --git a/_api-reference/ingest-apis/processors/bytes.md b/_api-reference/ingest-apis/processors/bytes.md
index 7d07766cbd..29b2550875 100644
--- a/_api-reference/ingest-apis/processors/bytes.md
+++ b/_api-reference/ingest-apis/processors/bytes.md
@@ -7,6 +7,8 @@ nav_order: 20
 ---
 
 # Bytes
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `bytes` processor converts a human-readable byte value to its equivalent value in bytes. The field can be a scalar or an array. If the field is a scalar, the value is converted and stored in the field. If the field is an array, all values of the array are converted.
 
diff --git a/_api-reference/ingest-apis/processors/convert.md b/_api-reference/ingest-apis/processors/convert.md
index 5b12c8e931..197eb9c588 100644
--- a/_api-reference/ingest-apis/processors/convert.md
+++ b/_api-reference/ingest-apis/processors/convert.md
@@ -7,6 +7,8 @@ nav_order: 30
 ---
 
 # Convert
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `convert` processor converts a field in a document to a different type, for example, a string to an integer or an integer to a string. For an array field, all values in the array are converted. The following is the syntax for the `convert` processor: 
 
diff --git a/_api-reference/ingest-apis/processors/csv.md b/_api-reference/ingest-apis/processors/csv.md
index e4009e162b..b8a20f9384 100644
--- a/_api-reference/ingest-apis/processors/csv.md
+++ b/_api-reference/ingest-apis/processors/csv.md
@@ -7,6 +7,8 @@ nav_order: 40
 ---
 
 # CSV
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `csv` processor is used to parse CSVs and store them as individual fields in a document. The processor ignores empty fields. The following is the syntax for the `csv` processor: 
 
diff --git a/_api-reference/ingest-apis/processors/date.md b/_api-reference/ingest-apis/processors/date.md
index 46e9b9115f..326e637c6c 100644
--- a/_api-reference/ingest-apis/processors/date.md
+++ b/_api-reference/ingest-apis/processors/date.md
@@ -7,6 +7,8 @@ nav_order: 50
 ---
 
 # Date
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `date` processor is used to parse dates from document fields and to add the parsed data to a new field. By default, the parsed data is stored in the `@timestamp` field. The following is the syntax for the `date` processor:
 
diff --git a/_api-reference/ingest-apis/processors/ip2geo.md b/_api-reference/ingest-apis/processors/ip2geo.md
index 4883974a0b..6533ce183e 100644
--- a/_api-reference/ingest-apis/processors/ip2geo.md
+++ b/_api-reference/ingest-apis/processors/ip2geo.md
@@ -7,7 +7,7 @@ nav_order: 130
 ---
 
 # IP2Geo
-Introduced 2.10
+**Introduced 2.10**
 {: .label .label-purple }
 
 The `ip2geo` processor adds information about the geographical location of an IPv4 or IPv6 address. The `ip2geo` processor uses IP geolocation (GeoIP) data from an external endpoint and therefore requires an additional component, `datasource`, that defines from where to download GeoIP data and how frequently to update the data.
@@ -43,7 +43,7 @@ OpenSearch provides the following endpoints for GeoLite2 City, GeoLite2 Country,
 
 If an OpenSearch cluster cannot update a data source from the endpoints within 30 days, the cluster does not add GeoIP data to the documents and instead adds `"error":"ip2geo_data_expired"`.
 
-### Data source options
+#### Data source options
 
 The following table lists the data source options for the `ip2geo` processor.   
 
@@ -65,7 +65,7 @@ PUT /_plugins/geospatial/ip2geo/datasource/my-datasource
 
 A `true` response means that the request was successful and that the server was able to process the request. A `false` response indicates that you should check the request to make sure it is valid, check the URL to make sure it is correct, or try again.
 
-### Sending a GET request
+#### Sending a GET request
 
 To get information about one or more IP2Geo data sources, send a GET request:  
 
@@ -112,7 +112,7 @@ You'll receive the following response:
 }
 ```
 
-### Updating an IP2Geo data source
+#### Updating an IP2Geo data source
 
 See the Creating the IP2Geo data source section for a list of endpoints and request field descriptions. 
 
@@ -127,7 +127,7 @@ PUT /_plugins/geospatial/ip2geo/datasource/my-datasource/_settings
 ```
 {% include copy-curl.html %}
 
-### Deleting the IP2Geo data source
+#### Deleting the IP2Geo data source
 
 To delete the IP2Geo data source, you must first delete all processors associated with the data source. Otherwise, the request fails. 
 
@@ -152,7 +152,7 @@ Once the data source is created, you can create the pipeline. The following is t
 ```
 {% include copy-curl.html %}
 
-### Configuration parameters
+#### Configuration parameters
 
 The following table lists the required and optional parameters for the `ip2geo` processor.
 
diff --git a/_api-reference/ingest-apis/processors/lowercase.md b/_api-reference/ingest-apis/processors/lowercase.md
index 535875ff7d..16bc389b8b 100644
--- a/_api-reference/ingest-apis/processors/lowercase.md
+++ b/_api-reference/ingest-apis/processors/lowercase.md
@@ -7,6 +7,8 @@ nav_order: 210
 ---
 
 # Lowercase
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `lowercase` processor converts all the text in a specific field to lowercase letters. The following is the syntax for the `lowercase` processor: 
 
diff --git a/_api-reference/ingest-apis/processors/remove.md b/_api-reference/ingest-apis/processors/remove.md
index db233a0b08..61d34f282e 100644
--- a/_api-reference/ingest-apis/processors/remove.md
+++ b/_api-reference/ingest-apis/processors/remove.md
@@ -7,6 +7,8 @@ nav_order: 230
 ---
 
 # Remove
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `remove` processor is used to remove a field from a document. The following is the syntax for the `remove` processor: 
 
diff --git a/_api-reference/ingest-apis/processors/uppercase.md b/_api-reference/ingest-apis/processors/uppercase.md
index 6ea5ebb137..49feaeedf9 100644
--- a/_api-reference/ingest-apis/processors/uppercase.md
+++ b/_api-reference/ingest-apis/processors/uppercase.md
@@ -7,6 +7,8 @@ nav_order: 310
 ---
 
 # Uppercase
+**Introduced 1.0**
+{: .label .label-purple }
 
 The `uppercase` processor converts all the text in a specific field to uppercase letters. The following is the syntax for the `uppercase` processor: 
 
diff --git a/_api-reference/ingest-apis/simulate-ingest.md b/_api-reference/ingest-apis/simulate-ingest.md
index 9ca40b791c..d4e2e9d417 100644
--- a/_api-reference/ingest-apis/simulate-ingest.md
+++ b/_api-reference/ingest-apis/simulate-ingest.md
@@ -9,6 +9,8 @@ redirect_from:
 ---
 
 # Simulate pipeline
+**Introduced 1.0**
+{: .label .label-purple }
 
 Use the simulate ingest pipeline API operation to run or test the pipeline.
 
@@ -121,7 +123,7 @@ The request returns the following response:
 }
 ```
 
-### Example: Verbose mode
+#### Example: Verbose mode
 
 When the previous request is run with the `verbose` parameter set to `true`, the response shows the sequence of transformations for each document. For example, for the document with the ID `1`, the response contains the results of applying each processor in the pipeline in sequence:
 
@@ -189,7 +191,7 @@ When the previous request is run with the `verbose` parameter set to `true`, the
 }
 ```
 
-### Example: Specify a pipeline in the request body
+#### Example: Specify a pipeline in the request body
 
 Alternatively, you can specify a pipeline directly in the request body without first creating a pipeline:
 
diff --git a/_api-reference/multi-search.md b/_api-reference/multi-search.md
index 9d6625e1fe..5457ef92fd 100644
--- a/_api-reference/multi-search.md
+++ b/_api-reference/multi-search.md
@@ -7,13 +7,12 @@ redirect_from:
 ---
 
 # Multi-search
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 As the name suggests, the multi-search operation lets you bundle multiple search requests into a single request. OpenSearch then executes the searches in parallel, so you get back the response more quickly compared to sending one request per search. OpenSearch executes each search independently, so the failure of one doesn't affect the others.
 
-
-## Example
+**Example**
 
 ```json
 GET _msearch
diff --git a/_api-reference/nodes-apis/index.md b/_api-reference/nodes-apis/index.md
index c6574f9661..ab6867ca9a 100644
--- a/_api-reference/nodes-apis/index.md
+++ b/_api-reference/nodes-apis/index.md
@@ -6,6 +6,8 @@ nav_order: 50
 ---
 
 # Nodes API
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes API makes it possible to retrieve information about individual nodes within your cluster. 
 
@@ -59,7 +61,7 @@ GET /_nodes/data:true/stats
 ```
 {% include copy-curl.html %}
 
-### Order of resolution mechanisms
+#### Order of resolution mechanisms
 
 The order of resolution mechanisms is applied sequentially, and each can add or remove nodes. The following examples yield different results.
 
diff --git a/_api-reference/nodes-apis/nodes-hot-threads.md b/_api-reference/nodes-apis/nodes-hot-threads.md
index 6f58cbf32f..6c9e3bd07c 100644
--- a/_api-reference/nodes-apis/nodes-hot-threads.md
+++ b/_api-reference/nodes-apis/nodes-hot-threads.md
@@ -6,10 +6,12 @@ nav_order: 30
 ---
 
 # Nodes hot threads
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes hot threads endpoint provides information about busy JVM threads for selected cluster nodes. It provides a unique view of the of activity each node.
 
-## Example
+**Example**
 
 ```json
 GET /_nodes/hot_threads
diff --git a/_api-reference/nodes-apis/nodes-info.md b/_api-reference/nodes-apis/nodes-info.md
index 3d5ba2bbef..a1f1a63810 100644
--- a/_api-reference/nodes-apis/nodes-info.md
+++ b/_api-reference/nodes-apis/nodes-info.md
@@ -6,6 +6,8 @@ nav_order: 10
 ---
 
 # Nodes info
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes info API represents mostly static information about your cluster's nodes, including but not limited to:
 
@@ -16,7 +18,7 @@ The nodes info API represents mostly static information about your cluster's nod
 - Thread pools settings 
 - Installed plugins
 
-## Example
+**Example**
 
 To get information about all nodes in a cluster, use the following query:
 
diff --git a/_api-reference/nodes-apis/nodes-reload-secure.md b/_api-reference/nodes-apis/nodes-reload-secure.md
index df4960f618..52b2ef67ab 100644
--- a/_api-reference/nodes-apis/nodes-reload-secure.md
+++ b/_api-reference/nodes-apis/nodes-reload-secure.md
@@ -6,6 +6,8 @@ nav_order: 50
 ---
 
 # Nodes reload secure settings
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes reload secure settings endpoint allows you to change secure settings on a node and reload the secure settings without restarting the node.
 
diff --git a/_api-reference/nodes-apis/nodes-stats.md b/_api-reference/nodes-apis/nodes-stats.md
index 8eaf965893..b3271aa69c 100644
--- a/_api-reference/nodes-apis/nodes-stats.md
+++ b/_api-reference/nodes-apis/nodes-stats.md
@@ -6,6 +6,8 @@ nav_order: 20
 ---
 
 # Nodes stats
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes stats API returns statistics about your cluster.
 
diff --git a/_api-reference/nodes-apis/nodes-usage.md b/_api-reference/nodes-apis/nodes-usage.md
index 4d83dcb21a..532ddb626b 100644
--- a/_api-reference/nodes-apis/nodes-usage.md
+++ b/_api-reference/nodes-apis/nodes-usage.md
@@ -6,6 +6,8 @@ nav_order: 40
 ---
 
 # Nodes usage
+**Introduced 1.0**
+{: .label .label-purple }
 
 The nodes usage endpoint returns low-level information about REST action usage on nodes.
 
diff --git a/_api-reference/popular-api.md b/_api-reference/popular-api.md
index 181a64a277..c258943c3c 100644
--- a/_api-reference/popular-api.md
+++ b/_api-reference/popular-api.md
@@ -7,6 +7,8 @@ redirect_from:
 ---
 
 # Popular APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 This page contains example requests for popular OpenSearch operations.
 
diff --git a/_api-reference/profile.md b/_api-reference/profile.md
index 27ea4d9c55..f8c3104a43 100644
--- a/_api-reference/profile.md
+++ b/_api-reference/profile.md
@@ -5,6 +5,8 @@ nav_order: 55
 ---
 
 # Profile
+**Introduced 1.0**
+{: .label .label-purple }
 
 The Profile API provides timing information about the execution of individual components of a search request. Using the Profile API, you can debug slow requests and understand how to improve their performance. The Profile API does not measure the following:
 
diff --git a/_api-reference/rank-eval.md b/_api-reference/rank-eval.md
index db12693b8e..04fd3cf5c0 100644
--- a/_api-reference/rank-eval.md
+++ b/_api-reference/rank-eval.md
@@ -5,6 +5,8 @@ nav_order: 60
 ---
 
 # Ranking evaluation
+**Introduced 1.0**
+{: .label .label-purple }
 
 The [rank]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/rank/) eval endpoint allows you to evaluate the quality of ranked search results.
 
diff --git a/_api-reference/remote-info.md b/_api-reference/remote-info.md
index 88fd8e8766..ac2971f294 100644
--- a/_api-reference/remote-info.md
+++ b/_api-reference/remote-info.md
@@ -7,7 +7,7 @@ redirect_from:
 ---
 
 # Remote cluster information
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 This operation provides connection information for any remote OpenSearch clusters that you've configured for the local cluster, such as the remote cluster alias, connection mode (`sniff` or `proxy`), IP addresses for seed nodes, and timeout settings.
diff --git a/_api-reference/script-apis/create-stored-script.md b/_api-reference/script-apis/create-stored-script.md
index 682398210d..04a73a205a 100644
--- a/_api-reference/script-apis/create-stored-script.md
+++ b/_api-reference/script-apis/create-stored-script.md
@@ -5,7 +5,9 @@ parent: Script APIs
 nav_order: 1
 ---
 
-## Create or update stored script
+# Create or update stored script
+**Introduced 1.0**
+{: .label .label-purple }
 
 Creates or updates a stored script or search template.
 
@@ -16,13 +18,13 @@ For additional information about Painless scripting, see:
 * [k-NN]({{site.url}}{{site.baseurl}}/search-plugins/knn/index/).
 
 
-### Path parameters
+## Path parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
 | script-id | String | Stored script or search template ID. Must be unique across the cluster. Required. |
 
-### Query parameters
+## Query parameters
 
 All parameters are optional.
 
@@ -32,7 +34,7 @@ All parameters are optional.
 | cluster_manager_timeout | Time | Amount of time to wait for a connection to the cluster manager. Defaults to 30 seconds. |
 | timeout | Time | The period of time to wait for a response. If a response is not received before the timeout value, the request fails and returns an error. Defaults to 30 seconds.|
 
-### Request fields
+## Request fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
@@ -138,7 +140,7 @@ To determine whether the script was successfully created, use the [Get stored sc
 
 The Painless script supports `params` to pass variables to the script. 
 
-### Example
+#### Example
 
 The following request creates the Painless script `multiplier-script`. The request sums the ratings for each book, multiplies the summed value by the `multiplier` parameter, and displays the result in the output:
 
diff --git a/_api-reference/script-apis/delete-script.md b/_api-reference/script-apis/delete-script.md
index a9cb3ca9c0..363b0152df 100644
--- a/_api-reference/script-apis/delete-script.md
+++ b/_api-reference/script-apis/delete-script.md
@@ -5,11 +5,13 @@ parent: Script APIs
 nav_order: 4
 ---
 
-## Delete script
+# Delete script
+**Introduced 1.0**
+{: .label .label-purple }
 
 Deletes a stored script
 
-### Path parameters
+## Path parameters
 
 Path parameters are optional. 
 
@@ -17,7 +19,7 @@ Path parameters are optional.
 :--- | :--- | :---
 | script-id | String | ID of script to delete. |
 
-### Query parameters
+## Query parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
@@ -45,7 +47,7 @@ The `DELETE _scripts/my-first-script` request returns the following field:
 
 To determine whether the stored script was successfully deleted, use the [Get stored script]({{site.url}}{{site.baseurl}}/api-reference/script-apis/get-stored-script/) API, passing the script name as the `script` path parameter.
 
-### Response fields
+## Response fields
 
 The <HTTP METHOD> <endpoint> request returns the following response fields:
 
diff --git a/_api-reference/script-apis/exec-script.md b/_api-reference/script-apis/exec-script.md
index 18e18478da..4ecb6a37fc 100644
--- a/_api-reference/script-apis/exec-script.md
+++ b/_api-reference/script-apis/exec-script.md
@@ -5,18 +5,20 @@ parent: Script APIs
 nav_order: 7
 ---
 
-## Execute Painless script
+# Execute Painless script
+**Introduced 1.0**
+{: .label .label-purple }
 
 The Execute Painless script API allows you to run a script that is not stored.
 
-### Path and HTTP methods
+## Path and HTTP methods
 
 ```json
 GET /_scripts/painless/_execute
 POST /_scripts/painless/_execute
 ```
 
-### Request fields
+## Request fields
 
 | Field | Description | 
 :--- | :---
@@ -52,7 +54,7 @@ The response contains the average of two script parameters:
 }
 ```
 
-### Response fields
+## Response fields
 
 | Field | Description | 
 :--- | :--- 
@@ -63,11 +65,11 @@ The response contains the average of two script parameters:
 
 Choose different contexts to control the variables that are available to the script and the result's return type. The default context is `painless_test`.
 
-### Painless test context
+## Painless test context
 
 The `painless_test` context is the default script context that provides only the `params` variable to the script. The returned result is always converted to a string. See the preceding example request for a usage example.
 
-### Filter context
+## Filter context
 
 The `filter` context runs the script as if the script were inside a script query. You must provide a test document in the context. The `_source`, stored fields, and `_doc` variables will be available to the script.
 
@@ -128,7 +130,7 @@ The response contains the result:
 }
 ```
 
-### Score context
+## Score context
 
 The `score` context runs a script as if the script were in a `script_score` function in a `function_score` query.
 
diff --git a/_api-reference/script-apis/exec-stored-script.md b/_api-reference/script-apis/exec-stored-script.md
index fccb325ca3..0483f92ccd 100644
--- a/_api-reference/script-apis/exec-stored-script.md
+++ b/_api-reference/script-apis/exec-stored-script.md
@@ -5,13 +5,15 @@ parent: Script APIs
 nav_order: 2
 ---
 
-## Execute Painless stored script
+# Execute Painless stored script
+**Introduced 1.0**
+{: .label .label-purple }
 
 Runs a stored script written in the Painless language. 
 
 OpenSearch provides several ways to run a script; the following sections show how to run a script by passing script information in the request body of a `GET <index>/_search` request.
 
-### Request fields
+## Request fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
@@ -102,7 +104,7 @@ The `GET books/_search` request returns the following fields:
 }
 ````
 
-### Response fields
+## Response fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
@@ -132,7 +134,7 @@ The `GET books/_search` request returns the following fields:
 
 To pass different parameters to the script each time when running a query, define `params` in `script_fields`.
 
-### Example
+#### Example
 
 The following request runs the stored script that was created in [Create or update stored script]({{site.url}}{{site.baseurl}}/api-reference/script-apis/create-stored-script/). The script sums the ratings for each book, multiplies the summed value by the `multiplier` parameter, and displays the result in the output.
 
@@ -164,7 +166,7 @@ GET books/_search
 ````
 {% include copy-curl.html %}
 
-### Example response
+#### Example response
 ````json
 {
   "took" : 12,
@@ -220,10 +222,10 @@ GET books/_search
 }
 ```
 
-## Sort results using painless stored script
-You can use painless stored script to sort results.
+**Sort results using painless stored script
+You can use painless stored script to sort results.**
 
-### Sample request
+#### Sample request
 
 ````json
 GET books/_search
@@ -256,7 +258,7 @@ GET books/_search
 }
 ```
 
-### Sample response
+#### Sample response
 
 ````json
 {
diff --git a/_api-reference/script-apis/get-script-contexts.md b/_api-reference/script-apis/get-script-contexts.md
index f9ca8052c8..40a155955f 100644
--- a/_api-reference/script-apis/get-script-contexts.md
+++ b/_api-reference/script-apis/get-script-contexts.md
@@ -5,7 +5,9 @@ parent: Script APIs
 nav_order: 5
 ---
 
-## Get stored script contexts
+# Get stored script contexts
+**Introduced 1.0**
+{: .label .label-purple }
 
 Retrieves all contexts for stored scripts.
 
@@ -545,7 +547,7 @@ The `GET _script_context` request returns the following fields:
 }
 ````
 
-### Response fields
+## Response fields
 
 The `GET _script_context` request returns the following response fields:
 
diff --git a/_api-reference/script-apis/get-script-language.md b/_api-reference/script-apis/get-script-language.md
index 6fb566b751..d53eb0487d 100644
--- a/_api-reference/script-apis/get-script-language.md
+++ b/_api-reference/script-apis/get-script-language.md
@@ -5,7 +5,9 @@ parent: Script APIs
 nav_order: 6
 ---
 
-## Get script language
+# Get script language
+**Introduced 1.0**
+{: .label .label-purple }
 
 The get script language API operation retrieves all supported script languages and their contexts.
 
@@ -87,7 +89,7 @@ The `GET _script_language` request returns the available contexts for each langu
 }
 ```
 
-### Response fields
+## Response fields
 
 The request contains the following response fields.
 
diff --git a/_api-reference/script-apis/get-stored-script.md b/_api-reference/script-apis/get-stored-script.md
index 374222623e..cc681cd0f4 100644
--- a/_api-reference/script-apis/get-stored-script.md
+++ b/_api-reference/script-apis/get-stored-script.md
@@ -5,17 +5,19 @@ parent: Script APIs
 nav_order: 3
 ---
 
-## Get stored script
+# Get stored script
+**Introduced 1.0**
+{: .label .label-purple }
 
 Retrieves a stored script.
 
-### Path parameters
+## Path parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
 | script | String | Stored script or search template name. Required.|
 
-### Query parameters
+## Query parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
@@ -51,7 +53,7 @@ The `GET _scripts/my-first-script` request returns the following fields:
 }
 ````
 
-### Response fields
+## Response fields
 
 The `GET _scripts/my-first-script` request returns the following response fields:
 
diff --git a/_api-reference/script-apis/index.md b/_api-reference/script-apis/index.md
index 836728894c..605faf3384 100644
--- a/_api-reference/script-apis/index.md
+++ b/_api-reference/script-apis/index.md
@@ -8,5 +8,7 @@ redirect_from:
 ---
 
 # Script APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 The script APIs allow you to work with stored scripts. Stored scripts are part of the cluster state and reduce compilation time and enhance search speed. The default scripting language is Painless.
diff --git a/_api-reference/scroll.md b/_api-reference/scroll.md
index f8bf82e598..8999e3ecf8 100644
--- a/_api-reference/scroll.md
+++ b/_api-reference/scroll.md
@@ -7,7 +7,7 @@ redirect_from:
 ---
 
 # Scroll
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 You can use the `scroll` operation to retrieve a large number of results. For example, for machine learning jobs, you can request an unlimited number of results in batches.
@@ -17,7 +17,7 @@ To use the `scroll` operation, add a `scroll` parameter to the request header wi
 Because search contexts consume a lot of memory, we suggest you don't use the `scroll` operation for frequent user queries. Instead, use the `sort` parameter with the `search_after` parameter to scroll responses for user queries.
 {: .note }
 
-## Example
+**Example**
 
 To set the number of results that you want returned for each batch, use the `size` parameter:
 
diff --git a/_api-reference/search.md b/_api-reference/search.md
index 215e77c7fe..cd8c523000 100644
--- a/_api-reference/search.md
+++ b/_api-reference/search.md
@@ -7,12 +7,12 @@ redirect_from:
 ---
 
 # Search
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The Search API operation lets you execute a search request to search your cluster for data.
 
-## Example
+**Example**
 
 ```json
 GET /movies/_search
diff --git a/_api-reference/snapshots/create-repository.md b/_api-reference/snapshots/create-repository.md
index b3a4e2034f..4b3fa39b67 100644
--- a/_api-reference/snapshots/create-repository.md
+++ b/_api-reference/snapshots/create-repository.md
@@ -6,6 +6,8 @@ nav_order: 1
 ---
 
 # Registering or updating a snapshot repository
+**Introduced 1.0**
+{: .label .label-purple }
 
 You can register a new repository in which to store snapshots or update information for an existing repository by using the snapshots API.
 
@@ -34,7 +36,7 @@ repository | String | Repository name |
 
 Request parameters depend on the type of repository: `fs` or `s3`.
 
-### fs repository
+#### fs repository
 
 Request field | Description
 :--- | :---
@@ -61,7 +63,7 @@ PUT /_snapshot/my-fs-repository
 ```
 {% include copy-curl.html %}
 
-### s3 repository
+#### s3 repository
 
 Request field | Description
 :--- | :---
diff --git a/_api-reference/snapshots/create-snapshot.md b/_api-reference/snapshots/create-snapshot.md
index dbffe42974..4f0a6d05cf 100644
--- a/_api-reference/snapshots/create-snapshot.md
+++ b/_api-reference/snapshots/create-snapshot.md
@@ -5,7 +5,9 @@ parent: Snapshot APIs
 nav_order: 5
 ---
 
-## Create snapshot
+# Create snapshot
+**Introduced 1.0**
+{: .label .label-purple }
 
 Creates a snapshot within an existing repository.
 
@@ -13,27 +15,27 @@ Creates a snapshot within an existing repository.
 
 * To view a list of your repositories, see [Get snapshot repository]({{site.url}}{{site.baseurl}}/api-reference/snapshots/get-snapshot-repository).
 
-### Path and HTTP methods
+## Path and HTTP methods
 
 ```json
 PUT /_snapshot/<repository>/<snapshot>
 POST /_snapshot/<repository>/<snapshot>
 ```
 
-### Path parameters
+## Path parameters
 
 Parameter | Data type | Description
 :--- | :--- | :---
 repository | String | Repostory name to contain the snapshot. |
 snapshot | String | Name of Snapshot to create. |
 
-### Query parameters
+## Query parameters
 
 Parameter | Data type | Description
 :--- | :--- | :---
 wait_for_completion | Boolean |  Whether to wait for snapshot creation to complete before continuing. If you include this parameter, the snapshot definition is returned after completion. |
 
-### Request fields
+## Request fields
 
 The request body is optional.
 
diff --git a/_api-reference/snapshots/delete-snapshot-repository.md b/_api-reference/snapshots/delete-snapshot-repository.md
index 5f4d446244..385205a5df 100644
--- a/_api-reference/snapshots/delete-snapshot-repository.md
+++ b/_api-reference/snapshots/delete-snapshot-repository.md
@@ -5,7 +5,9 @@ parent: Snapshot APIs
 nav_order: 3
 ---
 
-## Delete snapshot repository configuration
+# Delete snapshot repository configuration
+**Introduced 1.0**
+{: .label .label-purple }
 
  Deletes a snapshot repository configuration.  
  
@@ -13,7 +15,7 @@ nav_order: 3
 
  To learn more about repositories, see [Register or update snapshot repository]({{site.url}}{{site.baseurl}}/api-reference/snapshots/create-repository).
 
-### Path parameters
+## Path parameters
 
 Parameter | Data type | Description
 :--- | :--- | :---
diff --git a/_api-reference/snapshots/delete-snapshot.md b/_api-reference/snapshots/delete-snapshot.md
index 4dd25c49f1..e4232c20ec 100644
--- a/_api-reference/snapshots/delete-snapshot.md
+++ b/_api-reference/snapshots/delete-snapshot.md
@@ -6,6 +6,8 @@ nav_order: 7
 ---
 
 ## Delete snapshot
+**Introduced 1.0**
+{: .label .label-purple }
 
 Deletes a snapshot from a repository.
 
@@ -15,7 +17,7 @@ Deletes a snapshot from a repository.
 
 * To view a list of your snapshots, see [cat snapshots]({{site.url}}{{site.baseurl}}/api-reference/cat/cat-snapshots).
 
-### Path parameters
+## Path parameters
 
 Parameter | Data type | Description
 :--- | :--- | :---
diff --git a/_api-reference/snapshots/get-snapshot-repository.md b/_api-reference/snapshots/get-snapshot-repository.md
index 2ebe6921f7..e3664e11a8 100644
--- a/_api-reference/snapshots/get-snapshot-repository.md
+++ b/_api-reference/snapshots/get-snapshot-repository.md
@@ -5,7 +5,9 @@ parent: Snapshot APIs
 nav_order: 2
 ---
 
-## Get snapshot repository.
+# Get snapshot repository.
+**Introduced 1.0**
+{: .label .label-purple }
 
 Retrieves information about a snapshot repository.
 
@@ -14,13 +16,13 @@ To learn more about repositories, see [Register repository]({{site.url}}{{site.b
 You can also get details about a snapshot during and after snapshot creation. See [Get snapshot status]({{site.url}}{{site.baseurl}}/api-reference/snapshots/get-snapshot-status/).
 {: .note}
 
-### Path parameters
+## Path parameters
 
 | Parameter | Data type | Description |
 | :--- | :--- | :--- |
 | repository | String | A comma-separated list of snapshot repository names to retrieve. Wildcard (`*`) expressions are supported including combining wildcards with exclude patterns starting with `-`. |
 
-### Query parameters
+## Query parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
@@ -52,7 +54,7 @@ Upon success, the response returns repositry information. This sample is for an
 }
 ````
 
-### Response fields
+## Response fields
 
 | Field | Data type | Description |
 | :--- | :--- | :--- | 
diff --git a/_api-reference/snapshots/get-snapshot-status.md b/_api-reference/snapshots/get-snapshot-status.md
index adfac1b519..02aa419042 100644
--- a/_api-reference/snapshots/get-snapshot-status.md
+++ b/_api-reference/snapshots/get-snapshot-status.md
@@ -5,7 +5,9 @@ parent: Snapshot APIs
 nav_order: 8
 ---
 
-## Get snapshot status
+# Get snapshot status
+**Introduced 1.0**
+{: .label .label-purple }
 
 Returns details about a snapshot’s state during and after snapshot creation.
 
@@ -14,7 +16,7 @@ To learn about snapshot creation, see [Create snapshot]({{site.url}}{{site.baseu
 If you use the Security plugin, you must have the `monitor_snapshot`, `create_snapshot`, or `manage cluster` privileges.
 {: .note}
 
-### Path parameters
+## Path parameters
 
 Path parameters are optional. 
 
@@ -34,7 +36,7 @@ Three request variants provide flexibility:
 Using the API to return state for other than currently running snapshots can be very costly for (1) machine machine resources and (2) processing time if running in the cloud. For each snapshot, each request causes file reads from all a snapshot's shards. 
 {: .warning}
 
-### Request fields
+## Request fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
@@ -367,7 +369,7 @@ The `GET _snapshot/my-opensearch-repo/my-first-snapshot/_status` request returns
 }
 ````
 
-### Response fields
+## Response fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
diff --git a/_api-reference/snapshots/get-snapshot.md b/_api-reference/snapshots/get-snapshot.md
index 1b875e0964..da44c1f23d 100644
--- a/_api-reference/snapshots/get-snapshot.md
+++ b/_api-reference/snapshots/get-snapshot.md
@@ -5,18 +5,20 @@ parent: Snapshot APIs
 nav_order: 6
 ---
 
-## Get snapshot.
+# Get snapshot.
+**Introduced 1.0**
+{: .label .label-purple }
 
 Retrieves information about a snapshot.
 
-### Path parameters
+## Path parameters
 
 | Parameter | Data type | Description |
 | :--- | :--- | :--- |
 | repository | String | The repository that contains the snapshot to retrieve. |
 | snapshot | String | Snapshot to retrieve.
 
-### Query parameters
+## Query parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
@@ -71,7 +73,7 @@ Upon success, the response returns snapshot information:
   ]
 }
 ````
-### Response fields
+## Response fields
 
 | Field | Data type | Description |
 | :--- | :--- | :--- | 
diff --git a/_api-reference/snapshots/index.md b/_api-reference/snapshots/index.md
index 3f8278fb71..e341905ad5 100644
--- a/_api-reference/snapshots/index.md
+++ b/_api-reference/snapshots/index.md
@@ -9,5 +9,7 @@ redirect_from:
 ---
 
 # Snapshot APIs
+**Introduced 1.0**
+{: .label .label-purple }
 
 The snapshot APIs allow you to manage snapshots and snapshot repositories.
\ No newline at end of file
diff --git a/_api-reference/snapshots/restore-snapshot.md b/_api-reference/snapshots/restore-snapshot.md
index 7771ce44ce..7b82f72256 100644
--- a/_api-reference/snapshots/restore-snapshot.md
+++ b/_api-reference/snapshots/restore-snapshot.md
@@ -6,7 +6,9 @@ parent: Snapshot APIs
 nav_order: 9
 ---
 
-## Restore Snapshot
+# Restore Snapshot
+**Introduced 1.0**
+{: .label .label-purple }
 
 Restores a snapshot of a cluster or specified data streams and indices. 
 
@@ -17,14 +19,14 @@ Restores a snapshot of a cluster or specified data streams and indices.
 If open indexes with the same name that you want to restore already exist in the cluster, you must close, delete, or rename the indexes. See [Example request](#example-request) for information about renaming an index. See [Close index]({{site.url}}{{site.baseurl}}/api-reference/index-apis/close-index) for information about closing an index.
 {: .note}
 
-### Path parameters
+## Path parameters
 
 | Parameter | Data type | Description |
 :--- | :--- | :---
 repository | String | Repository containing the snapshot to restore. |
 | snapshot | String | Snapshot to restore. |
 
-### Query parameters
+## Query parameters
 
 Parameter | Data type | Description
 :--- | :--- | :---
@@ -90,7 +92,7 @@ Upon success, the response returns the following JSON object:
 ````
 Except for the snapshot name, all properties are empty or `0`. This is because any changes made to the volume after the snapshot was generated are lost. However, if you invoke the [Get snapshot]({{site.url}}{{site.baseurl}}/api-reference/snapshots/get-snapshot) API to examine the snapshot, a fully populated snapshot object is returned. 
 
-### Response fields
+## Response fields
 
 | Field | Data type | Description |
 | :--- | :--- | :--- | 
diff --git a/_api-reference/snapshots/verify-snapshot-repository.md b/_api-reference/snapshots/verify-snapshot-repository.md
index aa294978b1..2929952472 100644
--- a/_api-reference/snapshots/verify-snapshot-repository.md
+++ b/_api-reference/snapshots/verify-snapshot-repository.md
@@ -6,7 +6,9 @@ parent: Snapshot APIs
 nav_order: 4
 ---
 
-## Verify snapshot repository
+# Verify snapshot repository
+**Introduced 1.0**
+{: .label .label-purple }
 
 Verifies that a snapshot repository is functional. Verifies the repository on each node in a cluster.
 
@@ -15,7 +17,7 @@ If verification is successful, the verify snapshot repository API returns a list
 If you use the Security plugin, you must have the `manage cluster` privilege.
 {: .note}
 
-### Path parameters
+## Path parameters
 
 Path parameters are optional. 
 
@@ -23,7 +25,7 @@ Path parameters are optional.
 :--- | :--- | :---
 | repository | String | Name of repository to verify. |
 
-### Query parameters
+## Query parameters
 
 | Parameter | Data type | Description | 
 :--- | :--- | :---
@@ -68,7 +70,7 @@ In the preceding sample, one node is connected to the snapshot repository. If mo
 }
 ````
 
-### Response fields
+## Response fields
 
 | Field | Data type | Description | 
 :--- | :--- | :---
diff --git a/_api-reference/tasks.md b/_api-reference/tasks.md
index 72f88f0fc5..19ef373806 100644
--- a/_api-reference/tasks.md
+++ b/_api-reference/tasks.md
@@ -7,7 +7,7 @@ redirect_from:
 ---
 
 # Tasks
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 A task is any operation you run in a cluster. For example, searching your data collection of books for a title or author name is a task. When you run OpenSearch, a task is automatically created to monitor your cluster's health and performance. For more information about all of the tasks currently executing in your cluster, you can use the `tasks` API operation.
diff --git a/_api-reference/units.md b/_api-reference/units.md
index 1b9a3d07c9..8a0d2705f7 100644
--- a/_api-reference/units.md
+++ b/_api-reference/units.md
@@ -7,6 +7,8 @@ redirect_from:
 ---
 
 # Supported units
+**Introduced 1.0**
+{: .label .label-purple }
 
 OpenSearch supports the following units for all REST operations:
 

From f615491e589a29def79976ca6e648843d9bc489d Mon Sep 17 00:00:00 2001
From: samipak458 <samipak458@gmail.com>
Date: Fri, 13 Oct 2023 23:11:31 +0500
Subject: [PATCH 02/14] Update API files according to API template

Signed-off-by: samipak458 <samipak458@gmail.com>
---
 _api-reference/cat/cat-aliases.md                  | 2 +-
 _api-reference/cat/cat-allocation.md               | 2 +-
 _api-reference/cat/cat-cluster_manager.md          | 2 +-
 _api-reference/cat/cat-count.md                    | 2 +-
 _api-reference/cat/cat-field-data.md               | 2 +-
 _api-reference/cat/cat-health.md                   | 2 +-
 _api-reference/cat/cat-indices.md                  | 2 +-
 _api-reference/cat/cat-nodeattrs.md                | 2 +-
 _api-reference/cat/cat-nodes.md                    | 2 +-
 _api-reference/cat/cat-pending-tasks.md            | 2 +-
 _api-reference/cat/cat-plugins.md                  | 2 +-
 _api-reference/cat/cat-recovery.md                 | 2 +-
 _api-reference/cat/cat-repositories.md             | 2 +-
 _api-reference/cat/cat-segment-replication.md      | 2 +-
 _api-reference/cat/cat-segments.md                 | 2 +-
 _api-reference/cat/cat-shards.md                   | 2 +-
 _api-reference/cat/cat-snapshots.md                | 2 +-
 _api-reference/cat/cat-tasks.md                    | 2 +-
 _api-reference/cat/cat-templates.md                | 4 ++--
 _api-reference/cat/cat-thread-pool.md              | 4 ++--
 _api-reference/cat/index.md                        | 5 +++--
 _api-reference/cluster-api/cluster-allocation.md   | 2 +-
 _api-reference/cluster-api/cluster-health.md       | 2 +-
 _api-reference/cluster-api/cluster-stats.md        | 2 +-
 _api-reference/count.md                            | 2 +-
 _api-reference/document-apis/bulk.md               | 2 +-
 _api-reference/document-apis/delete-by-query.md    | 2 +-
 _api-reference/document-apis/delete-document.md    | 2 +-
 _api-reference/document-apis/get-documents.md      | 2 +-
 _api-reference/document-apis/index-document.md     | 2 +-
 _api-reference/document-apis/reindex.md            | 2 +-
 _api-reference/document-apis/update-by-query.md    | 2 +-
 _api-reference/document-apis/update-document.md    | 2 +-
 _api-reference/explain.md                          | 2 +-
 _api-reference/index-apis/alias.md                 | 2 +-
 _api-reference/index-apis/clone.md                 | 2 +-
 _api-reference/index-apis/close-index.md           | 2 +-
 _api-reference/index-apis/delete-index.md          | 2 +-
 _api-reference/index-apis/exists.md                | 2 +-
 _api-reference/index-apis/get-index.md             | 2 +-
 _api-reference/index-apis/get-settings.md          | 2 +-
 _api-reference/index-apis/open-index.md            | 2 +-
 _api-reference/index-apis/shrink-index.md          | 2 +-
 _api-reference/index-apis/split.md                 | 2 +-
 _api-reference/index-apis/update-settings.md       | 2 +-
 _api-reference/ingest-apis/processors/append.md    | 1 +
 _api-reference/ingest-apis/processors/bytes.md     | 1 +
 _api-reference/ingest-apis/processors/convert.md   | 5 ++++-
 _api-reference/ingest-apis/processors/csv.md       | 5 ++++-
 _api-reference/ingest-apis/processors/date.md      | 5 ++++-
 _api-reference/ingest-apis/processors/lowercase.md | 5 ++++-
 _api-reference/ingest-apis/processors/remove.md    | 5 ++++-
 _api-reference/ingest-apis/processors/uppercase.md | 5 ++++-
 _api-reference/multi-search.md                     | 2 +-
 _api-reference/nodes-apis/nodes-hot-threads.md     | 2 +-
 _api-reference/nodes-apis/nodes-info.md            | 2 +-
 _api-reference/scroll.md                           | 2 +-
 _api-reference/search.md                           | 2 +-
 58 files changed, 80 insertions(+), 59 deletions(-)

diff --git a/_api-reference/cat/cat-aliases.md b/_api-reference/cat/cat-aliases.md
index b6fc2ea4ad..984f76cd8c 100644
--- a/_api-reference/cat/cat-aliases.md
+++ b/_api-reference/cat/cat-aliases.md
@@ -15,7 +15,7 @@ has_children: false
 
 The CAT aliases operation lists the mapping of aliases to indexes, plus routing and filtering information.
 
-**Example**
+#### Example
 
 ```json
 GET _cat/aliases?v
diff --git a/_api-reference/cat/cat-allocation.md b/_api-reference/cat/cat-allocation.md
index fde3b8f3a6..3385e25d0d 100644
--- a/_api-reference/cat/cat-allocation.md
+++ b/_api-reference/cat/cat-allocation.md
@@ -14,7 +14,7 @@ has_children: false
 
 The CAT allocation operation lists the allocation of disk space for indexes and the number of shards on each node.
 
-**Example**
+#### Example
 
 ```json
 GET _cat/allocation?v
diff --git a/_api-reference/cat/cat-cluster_manager.md b/_api-reference/cat/cat-cluster_manager.md
index d4e68c12af..29eb313da9 100644
--- a/_api-reference/cat/cat-cluster_manager.md
+++ b/_api-reference/cat/cat-cluster_manager.md
@@ -14,7 +14,7 @@ has_children: false
 
 The CAT cluster manager operation lists information that helps identify the elected cluster manager node.
 
-**Example**
+#### Example
 
 ```
 GET _cat/cluster_manager?v
diff --git a/_api-reference/cat/cat-count.md b/_api-reference/cat/cat-count.md
index 7286c3630e..83ce3bc3f2 100644
--- a/_api-reference/cat/cat-count.md
+++ b/_api-reference/cat/cat-count.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT count operation lists the number of documents in your cluster.
 
-**Example**
+#### Example
 
 ```json
 GET _cat/count?v
diff --git a/_api-reference/cat/cat-field-data.md b/_api-reference/cat/cat-field-data.md
index ed7d7d3ead..6ab5123cc3 100644
--- a/_api-reference/cat/cat-field-data.md
+++ b/_api-reference/cat/cat-field-data.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT fielddata operation lists the memory size used by each field per node.
 
-**Example**
+#### Example
 
 ```json
 GET _cat/fielddata?v
diff --git a/_api-reference/cat/cat-health.md b/_api-reference/cat/cat-health.md
index a595462a2b..c8e2679ff6 100644
--- a/_api-reference/cat/cat-health.md
+++ b/_api-reference/cat/cat-health.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT health operation lists the status of the cluster, how long the cluster has been up, the number of nodes, and other useful information that helps you analyze the health of your cluster.
 
-**Example**
+#### Example
 
 ```json
 GET _cat/health?v
diff --git a/_api-reference/cat/cat-indices.md b/_api-reference/cat/cat-indices.md
index 535adf0fdf..d469838749 100644
--- a/_api-reference/cat/cat-indices.md
+++ b/_api-reference/cat/cat-indices.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT indices operation lists information related to indexes, that is, how much disk space they are using, how many shards they have, their health status, and so on.
 
-**Example**
+#### Example
 
 ```
 GET _cat/indices?v
diff --git a/_api-reference/cat/cat-nodeattrs.md b/_api-reference/cat/cat-nodeattrs.md
index d4c9a13248..69e6bf786e 100644
--- a/_api-reference/cat/cat-nodeattrs.md
+++ b/_api-reference/cat/cat-nodeattrs.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT nodeattrs operation lists the attributes of custom nodes.
 
-**Example**
+#### Example
 
 ```
 GET _cat/nodeattrs?v
diff --git a/_api-reference/cat/cat-nodes.md b/_api-reference/cat/cat-nodes.md
index 8303b90d27..1f5a0206b9 100644
--- a/_api-reference/cat/cat-nodes.md
+++ b/_api-reference/cat/cat-nodes.md
@@ -17,7 +17,7 @@ The CAT nodes operation lists node-level information, including node roles and l
 
 A few important node metrics are `pid`, `name`, `cluster_manager`, `ip`, `port`, `version`, `build`, `jdk`, along with `disk`, `heap`, `ram`, and `file_desc`.
 
-**Example**
+#### Example
 
 ```
 GET _cat/nodes?v
diff --git a/_api-reference/cat/cat-pending-tasks.md b/_api-reference/cat/cat-pending-tasks.md
index 73597b8184..e7d18cd546 100644
--- a/_api-reference/cat/cat-pending-tasks.md
+++ b/_api-reference/cat/cat-pending-tasks.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT pending tasks operation lists the progress of all pending tasks, including task priority and time in queue.
 
-**Example**
+#### Example
 
 ```
 GET _cat/pending_tasks?v
diff --git a/_api-reference/cat/cat-plugins.md b/_api-reference/cat/cat-plugins.md
index b3bea30c8e..24281926b6 100644
--- a/_api-reference/cat/cat-plugins.md
+++ b/_api-reference/cat/cat-plugins.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT plugins operation lists the names, components, and versions of the installed plugins.
 
-**Example**
+#### Example
 
 ```
 GET _cat/plugins?v
diff --git a/_api-reference/cat/cat-recovery.md b/_api-reference/cat/cat-recovery.md
index 79deb6c494..712d115a67 100644
--- a/_api-reference/cat/cat-recovery.md
+++ b/_api-reference/cat/cat-recovery.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT recovery operation lists all completed and ongoing index and shard recoveries.
 
-**Example**
+#### Example
 
 ```
 GET _cat/recovery?v
diff --git a/_api-reference/cat/cat-repositories.md b/_api-reference/cat/cat-repositories.md
index d8f2437972..4bbfdb9e87 100644
--- a/_api-reference/cat/cat-repositories.md
+++ b/_api-reference/cat/cat-repositories.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT repositories operation lists all completed and ongoing index and shard recoveries.
 
-**Example**
+#### Example
 
 ```
 GET _cat/repositories?v
diff --git a/_api-reference/cat/cat-segment-replication.md b/_api-reference/cat/cat-segment-replication.md
index ef64fcd910..d93f063905 100644
--- a/_api-reference/cat/cat-segment-replication.md
+++ b/_api-reference/cat/cat-segment-replication.md
@@ -47,7 +47,7 @@ Parameter | Data type  | Description
 `v` | Boolean    | If `true`, the response includes column headings. Defaults to `false`.
 `s` | String     | Specifies to sort the results. For example, `s=shardId:desc` sorts by shardId in descending order.
 
-### Examples 
+#### Example
 
 The following examples illustrate various segment replication responses.
 
diff --git a/_api-reference/cat/cat-segments.md b/_api-reference/cat/cat-segments.md
index 876a9502cb..2a2977c0ba 100644
--- a/_api-reference/cat/cat-segments.md
+++ b/_api-reference/cat/cat-segments.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The cat segments operation lists Lucene segment-level information for each index.
 
-**Example**
+#### Example
 
 ```
 GET _cat/segments?v
diff --git a/_api-reference/cat/cat-shards.md b/_api-reference/cat/cat-shards.md
index 92b69ed964..7fdf58e659 100644
--- a/_api-reference/cat/cat-shards.md
+++ b/_api-reference/cat/cat-shards.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT shards operation lists the state of all primary and replica shards and how they are distributed.
 
-**Example**
+#### Example
 
 ```
 GET _cat/shards?v
diff --git a/_api-reference/cat/cat-snapshots.md b/_api-reference/cat/cat-snapshots.md
index 974735d349..1774753f89 100644
--- a/_api-reference/cat/cat-snapshots.md
+++ b/_api-reference/cat/cat-snapshots.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT snapshots operation lists all snapshots for a repository.
 
-**Example**
+#### Example
 
 ```
 GET _cat/snapshots?v
diff --git a/_api-reference/cat/cat-tasks.md b/_api-reference/cat/cat-tasks.md
index 4d5faa5de4..b98a5d3a80 100644
--- a/_api-reference/cat/cat-tasks.md
+++ b/_api-reference/cat/cat-tasks.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT tasks operation lists the progress of all tasks currently running on your cluster.
 
-**Example**
+#### Example
 
 ```
 GET _cat/tasks?v
diff --git a/_api-reference/cat/cat-templates.md b/_api-reference/cat/cat-templates.md
index 0884cda639..91333b9503 100644
--- a/_api-reference/cat/cat-templates.md
+++ b/_api-reference/cat/cat-templates.md
@@ -10,12 +10,12 @@ redirect_from:
 ---
 
 # CAT templates
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT templates operation lists the names, patterns, order numbers, and version numbers of index templates.
 
-## Example
+#### Example
 
 ```
 GET _cat/templates?v
diff --git a/_api-reference/cat/cat-thread-pool.md b/_api-reference/cat/cat-thread-pool.md
index 6fc110bb9b..d7d145277d 100644
--- a/_api-reference/cat/cat-thread-pool.md
+++ b/_api-reference/cat/cat-thread-pool.md
@@ -9,12 +9,12 @@ redirect_from:
 ---
 
 # CAT thread pool
-Introduced 1.0
+**Introduced 1.0**
 {: .label .label-purple }
 
 The CAT thread pool operation lists the active, queued, and rejected threads of different thread pools on each node.
 
-## Example
+#### Example
 
 ```
 GET _cat/thread_pool?v
diff --git a/_api-reference/cat/index.md b/_api-reference/cat/index.md
index 7f4396f450..2407156323 100644
--- a/_api-reference/cat/index.md
+++ b/_api-reference/cat/index.md
@@ -9,12 +9,13 @@ redirect_from:
 ---
 
 # CAT API
-
+**Introduced 1.0**
+{: .label .label-purple }
 You can get essential statistics about your cluster in an easy-to-understand, tabular format using the compact and aligned text (CAT) API. The CAT API is a human-readable interface that returns plain text instead of traditional JSON.
 
 Using the CAT API, you can answer questions like which node is the elected master, what state is the cluster in, how many documents are in each index, and so on.
 
-## Example
+#### Example
 
 To see the available operations in the CAT API, use the following command:
 
diff --git a/_api-reference/cluster-api/cluster-allocation.md b/_api-reference/cluster-api/cluster-allocation.md
index 84184eecaa..b68d49f138 100644
--- a/_api-reference/cluster-api/cluster-allocation.md
+++ b/_api-reference/cluster-api/cluster-allocation.md
@@ -17,7 +17,7 @@ The most basic cluster allocation explain request finds an unassigned shard and
 If you add some options, you can instead get information on a specific shard, including why OpenSearch assigned it to its current node.
 
 
-**Example**
+#### Example
 
 ```json
 GET _cluster/allocation/explain?include_yes_decisions=true
diff --git a/_api-reference/cluster-api/cluster-health.md b/_api-reference/cluster-api/cluster-health.md
index 570216f602..0ef534c60c 100644
--- a/_api-reference/cluster-api/cluster-health.md
+++ b/_api-reference/cluster-api/cluster-health.md
@@ -17,7 +17,7 @@ The most basic cluster health request returns a simple status of the health of y
 
 To get the status of a specific index, provide the index name.
 
-**Example**
+#### Example
 
 This request waits 50 seconds for the cluster to reach the yellow status or better:
 
diff --git a/_api-reference/cluster-api/cluster-stats.md b/_api-reference/cluster-api/cluster-stats.md
index 9da37b3b57..de598bb90f 100644
--- a/_api-reference/cluster-api/cluster-stats.md
+++ b/_api-reference/cluster-api/cluster-stats.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The cluster stats API operation returns statistics about your cluster.
 
-**Examples**
+#### Example
 
 ```json
 GET _cluster/stats/nodes/_cluster_manager
diff --git a/_api-reference/count.md b/_api-reference/count.md
index a95b948e8d..f91c9f6bc7 100644
--- a/_api-reference/count.md
+++ b/_api-reference/count.md
@@ -13,7 +13,7 @@ redirect_from:
 The count API gives you quick access to the number of documents that match a query.
 You can also use it to check the document count of an index, data stream, or cluster.
 
-**Example**
+#### Example
 
 To see the number of documents that match a query:
 
diff --git a/_api-reference/document-apis/bulk.md b/_api-reference/document-apis/bulk.md
index 83a0754301..32f0fb6b46 100644
--- a/_api-reference/document-apis/bulk.md
+++ b/_api-reference/document-apis/bulk.md
@@ -17,7 +17,7 @@ The bulk operation lets you add, update, or delete multiple documents in a singl
 Beginning in OpenSearch 2.9, when indexing documents using the bulk operation, the document `_id` must be 512 bytes or less in size.
 {: .note}
 
-**Example**
+#### Example
 
 ```json
 POST _bulk
diff --git a/_api-reference/document-apis/delete-by-query.md b/_api-reference/document-apis/delete-by-query.md
index d42656b0cc..c57f85035d 100644
--- a/_api-reference/document-apis/delete-by-query.md
+++ b/_api-reference/document-apis/delete-by-query.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can include a query as part of your delete request so OpenSearch deletes all documents that match that query.
 
-**Example**
+#### Example
 
 ```json
 POST sample-index1/_delete_by_query
diff --git a/_api-reference/document-apis/delete-document.md b/_api-reference/document-apis/delete-document.md
index 237a7fcb50..beee9c4697 100644
--- a/_api-reference/document-apis/delete-document.md
+++ b/_api-reference/document-apis/delete-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you no longer need a document in your index, you can use the delete document API operation to delete it.
 
-**Example**
+#### Example
 
 ```
 DELETE /sample-index1/_doc/1
diff --git a/_api-reference/document-apis/get-documents.md b/_api-reference/document-apis/get-documents.md
index aba1f0849d..876c62a128 100644
--- a/_api-reference/document-apis/get-documents.md
+++ b/_api-reference/document-apis/get-documents.md
@@ -13,7 +13,7 @@ redirect_from:
 
 After adding a JSON document to your index, you can use the get document API operation to retrieve the document's information and data.
 
-**Example**
+#### Example
 
 ```json
 GET sample-index1/_doc/1
diff --git a/_api-reference/document-apis/index-document.md b/_api-reference/document-apis/index-document.md
index bff8dcbe5c..7922f715c6 100644
--- a/_api-reference/document-apis/index-document.md
+++ b/_api-reference/document-apis/index-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 Before you can search for data, you must first add documents. This operation adds a single document to your index.
 
-**Example**
+#### Example
 
 ```json
 PUT sample-index/_doc/1
diff --git a/_api-reference/document-apis/reindex.md b/_api-reference/document-apis/reindex.md
index 3bb3c69e9f..539e116d69 100644
--- a/_api-reference/document-apis/reindex.md
+++ b/_api-reference/document-apis/reindex.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The reindex document API operation lets you copy all or a subset of your data from a source index into a destination index.
 
-**Example**
+#### Example
 
 ```json
 POST /_reindex
diff --git a/_api-reference/document-apis/update-by-query.md b/_api-reference/document-apis/update-by-query.md
index c6bef9f733..5f411b5d2d 100644
--- a/_api-reference/document-apis/update-by-query.md
+++ b/_api-reference/document-apis/update-by-query.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can include a query and a script as part of your update request so OpenSearch can run the script to update all of the documents that match the query.
 
-**Example**
+#### Example
 
 ```json
 POST test-index1/_update_by_query
diff --git a/_api-reference/document-apis/update-document.md b/_api-reference/document-apis/update-document.md
index fad761af37..cb3fa082c3 100644
--- a/_api-reference/document-apis/update-document.md
+++ b/_api-reference/document-apis/update-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you need to update a document's fields in your index, you can use the update document API operation. You can do so by specifying the new data you want in your index or by including a script in your request body, which OpenSearch runs to update the document.
 
-**Example**
+#### Example
 
 ```json
 POST /sample-index1/_update/1
diff --git a/_api-reference/explain.md b/_api-reference/explain.md
index 179a08c9de..96dd380254 100644
--- a/_api-reference/explain.md
+++ b/_api-reference/explain.md
@@ -18,7 +18,7 @@ The explain API is an expensive operation in terms of both resources and time. O
 {: .warning }
 
 
-**Example**
+#### Example
 
 To see the explain output for all results, set the `explain` flag to `true` either in the URL or in the body of the request:
 
diff --git a/_api-reference/index-apis/alias.md b/_api-reference/index-apis/alias.md
index 2007fd9ea5..09379f309b 100644
--- a/_api-reference/index-apis/alias.md
+++ b/_api-reference/index-apis/alias.md
@@ -15,7 +15,7 @@ redirect_from:
 An alias is a virtual pointer that you can use to reference one or more indexes. Creating and updating aliases are atomic operations, so you can reindex your data and point an alias at it without any downtime.
 
 
-**Example**
+#### Example
 
 ```json
 POST _aliases
diff --git a/_api-reference/index-apis/clone.md b/_api-reference/index-apis/clone.md
index fc39ca1df3..dfe2e5f6c3 100644
--- a/_api-reference/index-apis/clone.md
+++ b/_api-reference/index-apis/clone.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The clone index API operation clones all data in an existing read-only index into a new index. The new index cannot already exist.
 
-**Example**
+#### Example
 
 ```json
 PUT /sample-index1/_clone/cloned-index1
diff --git a/_api-reference/index-apis/close-index.md b/_api-reference/index-apis/close-index.md
index 6f6868a764..e8d2e3e1e2 100644
--- a/_api-reference/index-apis/close-index.md
+++ b/_api-reference/index-apis/close-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The close index API operation closes an index. Once an index is closed, you cannot add data to it or search for any data within the index.
 
-**Example**
+#### Example
 
 ```json
 POST /sample-index/_close
diff --git a/_api-reference/index-apis/delete-index.md b/_api-reference/index-apis/delete-index.md
index fa1014429d..015cb29783 100644
--- a/_api-reference/index-apis/delete-index.md
+++ b/_api-reference/index-apis/delete-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you no longer need an index, you can use the delete index API operation to delete it.
 
-**Example**
+#### Example
 
 ```json
 DELETE /sample-index
diff --git a/_api-reference/index-apis/exists.md b/_api-reference/index-apis/exists.md
index e95dcb7b06..8bb8f80893 100644
--- a/_api-reference/index-apis/exists.md
+++ b/_api-reference/index-apis/exists.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The index exists API operation returns whether or not an index already exists.
 
-**Example**
+#### Example
 
 ```json
 HEAD /sample-index
diff --git a/_api-reference/index-apis/get-index.md b/_api-reference/index-apis/get-index.md
index 8f2ff44162..29052e6455 100644
--- a/_api-reference/index-apis/get-index.md
+++ b/_api-reference/index-apis/get-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can use the get index API operation to return information about an index.
 
-**Example**
+#### Example
 
 ```json
 GET /sample-index
diff --git a/_api-reference/index-apis/get-settings.md b/_api-reference/index-apis/get-settings.md
index 3ace352875..6b727a78e5 100644
--- a/_api-reference/index-apis/get-settings.md
+++ b/_api-reference/index-apis/get-settings.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The get settings API operation returns all the settings in your index.
 
-**Example**
+#### Example
 
 ```json
 GET /sample-index1/_settings
diff --git a/_api-reference/index-apis/open-index.md b/_api-reference/index-apis/open-index.md
index 25e6f1aaac..cf0af67742 100644
--- a/_api-reference/index-apis/open-index.md
+++ b/_api-reference/index-apis/open-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The open index API operation opens a closed index, letting you add or search for data within the index.
 
-**Example**
+#### Example
 
 ```json
 POST /sample-index/_open
diff --git a/_api-reference/index-apis/shrink-index.md b/_api-reference/index-apis/shrink-index.md
index 13c803def0..d17dee0650 100644
--- a/_api-reference/index-apis/shrink-index.md
+++ b/_api-reference/index-apis/shrink-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The shrink index API operation moves all of your data in an existing index into a new index with fewer primary shards.
 
-**Example**
+#### Example
 
 ```json
 POST /my-old-index/_shrink/my-new-index
diff --git a/_api-reference/index-apis/split.md b/_api-reference/index-apis/split.md
index 66025253a4..51f4958d10 100644
--- a/_api-reference/index-apis/split.md
+++ b/_api-reference/index-apis/split.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The split index API operation splits an existing read-only index into a new index, cutting each primary shard into some amount of primary shards in the new index.
 
-**Example**
+#### Example
 
 ```json
 PUT /sample-index1/_split/split-index1
diff --git a/_api-reference/index-apis/update-settings.md b/_api-reference/index-apis/update-settings.md
index c742e1c291..bcaed91eda 100644
--- a/_api-reference/index-apis/update-settings.md
+++ b/_api-reference/index-apis/update-settings.md
@@ -15,7 +15,7 @@ You can use the update settings API operation to update index-level settings. Yo
 
 Aside from the static and dynamic index settings, you can also update individual plugins' settings. To get the full list of updatable settings, run `GET <target-index>/_settings?include_defaults=true`.
 
-**Example**
+#### Example
 
 ```json
 PUT /sample-index1/_settings
diff --git a/_api-reference/ingest-apis/processors/append.md b/_api-reference/ingest-apis/processors/append.md
index 24973275e9..f35b96b408 100644
--- a/_api-reference/ingest-apis/processors/append.md
+++ b/_api-reference/ingest-apis/processors/append.md
@@ -15,6 +15,7 @@ The `append` processor is used to add values to a field:
 - If the field is a scalar field, the `append` processor converts it to an array and appends the specified values to that array.
 - If the field does not exist, the `append` processor creates an array with the specified values.
 
+#### Example
 The following is the syntax for the `append` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/bytes.md b/_api-reference/ingest-apis/processors/bytes.md
index 29b2550875..717e4fac64 100644
--- a/_api-reference/ingest-apis/processors/bytes.md
+++ b/_api-reference/ingest-apis/processors/bytes.md
@@ -12,6 +12,7 @@ nav_order: 20
 
 The `bytes` processor converts a human-readable byte value to its equivalent value in bytes. The field can be a scalar or an array. If the field is a scalar, the value is converted and stored in the field. If the field is an array, all values of the array are converted.
 
+#### Example
 The following is the syntax for the `bytes` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/convert.md b/_api-reference/ingest-apis/processors/convert.md
index 197eb9c588..cdd7d0c7be 100644
--- a/_api-reference/ingest-apis/processors/convert.md
+++ b/_api-reference/ingest-apis/processors/convert.md
@@ -10,7 +10,10 @@ nav_order: 30
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `convert` processor converts a field in a document to a different type, for example, a string to an integer or an integer to a string. For an array field, all values in the array are converted. The following is the syntax for the `convert` processor: 
+The `convert` processor converts a field in a document to a different type, for example, a string to an integer or an integer to a string. For an array field, all values in the array are converted. 
+
+#### Example
+The following is the syntax for the `convert` processor: 
 
 ```json
 {
diff --git a/_api-reference/ingest-apis/processors/csv.md b/_api-reference/ingest-apis/processors/csv.md
index b8a20f9384..1f4e44ddac 100644
--- a/_api-reference/ingest-apis/processors/csv.md
+++ b/_api-reference/ingest-apis/processors/csv.md
@@ -10,7 +10,10 @@ nav_order: 40
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `csv` processor is used to parse CSVs and store them as individual fields in a document. The processor ignores empty fields. The following is the syntax for the `csv` processor: 
+The `csv` processor is used to parse CSVs and store them as individual fields in a document. The processor ignores empty fields. 
+
+#### Example
+The following is the syntax for the `csv` processor: 
 
 ```json
 {
diff --git a/_api-reference/ingest-apis/processors/date.md b/_api-reference/ingest-apis/processors/date.md
index 326e637c6c..41bf971dc1 100644
--- a/_api-reference/ingest-apis/processors/date.md
+++ b/_api-reference/ingest-apis/processors/date.md
@@ -10,7 +10,10 @@ nav_order: 50
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `date` processor is used to parse dates from document fields and to add the parsed data to a new field. By default, the parsed data is stored in the `@timestamp` field. The following is the syntax for the `date` processor:
+The `date` processor is used to parse dates from document fields and to add the parsed data to a new field. By default, the parsed data is stored in the `@timestamp` field. 
+
+#### Example
+The following is the syntax for the `date` processor:
 
 ```json
 {
diff --git a/_api-reference/ingest-apis/processors/lowercase.md b/_api-reference/ingest-apis/processors/lowercase.md
index 16bc389b8b..bbe1a82b01 100644
--- a/_api-reference/ingest-apis/processors/lowercase.md
+++ b/_api-reference/ingest-apis/processors/lowercase.md
@@ -10,7 +10,10 @@ nav_order: 210
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `lowercase` processor converts all the text in a specific field to lowercase letters. The following is the syntax for the `lowercase` processor: 
+The `lowercase` processor converts all the text in a specific field to lowercase letters. 
+
+#### Example
+The following is the syntax for the `lowercase` processor: 
 
 ```json
 {
diff --git a/_api-reference/ingest-apis/processors/remove.md b/_api-reference/ingest-apis/processors/remove.md
index 61d34f282e..64ff4a7411 100644
--- a/_api-reference/ingest-apis/processors/remove.md
+++ b/_api-reference/ingest-apis/processors/remove.md
@@ -10,7 +10,10 @@ nav_order: 230
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `remove` processor is used to remove a field from a document. The following is the syntax for the `remove` processor: 
+The `remove` processor is used to remove a field from a document. 
+
+#### Example
+The following is the syntax for the `remove` processor: 
 
 ```json
 {
diff --git a/_api-reference/ingest-apis/processors/uppercase.md b/_api-reference/ingest-apis/processors/uppercase.md
index 49feaeedf9..4f29cc5a55 100644
--- a/_api-reference/ingest-apis/processors/uppercase.md
+++ b/_api-reference/ingest-apis/processors/uppercase.md
@@ -10,7 +10,10 @@ nav_order: 310
 **Introduced 1.0**
 {: .label .label-purple }
 
-The `uppercase` processor converts all the text in a specific field to uppercase letters. The following is the syntax for the `uppercase` processor: 
+The `uppercase` processor converts all the text in a specific field to uppercase letters. 
+
+#### Example
+The following is the syntax for the `uppercase` processor: 
 
 ```json
 {
diff --git a/_api-reference/multi-search.md b/_api-reference/multi-search.md
index 5457ef92fd..72fe5edef2 100644
--- a/_api-reference/multi-search.md
+++ b/_api-reference/multi-search.md
@@ -12,7 +12,7 @@ redirect_from:
 
 As the name suggests, the multi-search operation lets you bundle multiple search requests into a single request. OpenSearch then executes the searches in parallel, so you get back the response more quickly compared to sending one request per search. OpenSearch executes each search independently, so the failure of one doesn't affect the others.
 
-**Example**
+#### Example
 
 ```json
 GET _msearch
diff --git a/_api-reference/nodes-apis/nodes-hot-threads.md b/_api-reference/nodes-apis/nodes-hot-threads.md
index 6c9e3bd07c..3fb6ff65ea 100644
--- a/_api-reference/nodes-apis/nodes-hot-threads.md
+++ b/_api-reference/nodes-apis/nodes-hot-threads.md
@@ -11,7 +11,7 @@ nav_order: 30
 
 The nodes hot threads endpoint provides information about busy JVM threads for selected cluster nodes. It provides a unique view of the of activity each node.
 
-**Example**
+#### Example
 
 ```json
 GET /_nodes/hot_threads
diff --git a/_api-reference/nodes-apis/nodes-info.md b/_api-reference/nodes-apis/nodes-info.md
index a1f1a63810..cc7812c224 100644
--- a/_api-reference/nodes-apis/nodes-info.md
+++ b/_api-reference/nodes-apis/nodes-info.md
@@ -18,7 +18,7 @@ The nodes info API represents mostly static information about your cluster's nod
 - Thread pools settings 
 - Installed plugins
 
-**Example**
+#### Example
 
 To get information about all nodes in a cluster, use the following query:
 
diff --git a/_api-reference/scroll.md b/_api-reference/scroll.md
index 8999e3ecf8..701c7d8ca2 100644
--- a/_api-reference/scroll.md
+++ b/_api-reference/scroll.md
@@ -17,7 +17,7 @@ To use the `scroll` operation, add a `scroll` parameter to the request header wi
 Because search contexts consume a lot of memory, we suggest you don't use the `scroll` operation for frequent user queries. Instead, use the `sort` parameter with the `search_after` parameter to scroll responses for user queries.
 {: .note }
 
-**Example**
+#### Example
 
 To set the number of results that you want returned for each batch, use the `size` parameter:
 
diff --git a/_api-reference/search.md b/_api-reference/search.md
index cd8c523000..bb9d9744e4 100644
--- a/_api-reference/search.md
+++ b/_api-reference/search.md
@@ -12,7 +12,7 @@ redirect_from:
 
 The Search API operation lets you execute a search request to search your cluster for data.
 
-**Example**
+#### Example
 
 ```json
 GET /movies/_search

From 502fb2567dc2dd38c6f2b4f6a991d854b88571f9 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Date: Mon, 16 Oct 2023 09:39:33 -0500
Subject: [PATCH 03/14] Update exec-stored-script.md

Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
---
 _api-reference/script-apis/exec-stored-script.md | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/_api-reference/script-apis/exec-stored-script.md b/_api-reference/script-apis/exec-stored-script.md
index 0483f92ccd..7525ec81a4 100644
--- a/_api-reference/script-apis/exec-stored-script.md
+++ b/_api-reference/script-apis/exec-stored-script.md
@@ -146,7 +146,7 @@ The following request runs the stored script that was created in [Create or upda
 
 * `"multiplier": 2` in the `params` field is a variable passed to the stored script `multiplier-script`:
 
-````json
+```json
 GET books/_search
 {
    "query": {
@@ -163,11 +163,12 @@ GET books/_search
     }
   }
 }
-````
+```
 {% include copy-curl.html %}
 
 #### Example response
-````json
+
+```json
 {
   "took" : 12,
   "timed_out" : false,
@@ -227,7 +228,7 @@ You can use painless stored script to sort results.**
 
 #### Sample request
 
-````json
+```json
 GET books/_search
 {
    "query": {
@@ -260,7 +261,7 @@ GET books/_search
 
 #### Sample response
 
-````json
+```json
 {
   "took" : 90,
   "timed_out" : false,
@@ -322,4 +323,4 @@ GET books/_search
     ]
   }
 }
-```
\ No newline at end of file
+```

From d394a06f90bbf50e131d1ab96210321764e2c8a0 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:14:38 +0500
Subject: [PATCH 04/14] Update cat-aliases.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-aliases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-aliases.md b/_api-reference/cat/cat-aliases.md
index 984f76cd8c..6dcf3ddcf9 100644
--- a/_api-reference/cat/cat-aliases.md
+++ b/_api-reference/cat/cat-aliases.md
@@ -15,7 +15,7 @@ has_children: false
 
 The CAT aliases operation lists the mapping of aliases to indexes, plus routing and filtering information.
 
-#### Example
+## Example
 
 ```json
 GET _cat/aliases?v

From 6bb61fa935d206aeec3e6d4436e5f760e1348769 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:14:57 +0500
Subject: [PATCH 05/14] Update cat-allocation.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-allocation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-allocation.md b/_api-reference/cat/cat-allocation.md
index 3385e25d0d..9598c8f3b5 100644
--- a/_api-reference/cat/cat-allocation.md
+++ b/_api-reference/cat/cat-allocation.md
@@ -14,7 +14,7 @@ has_children: false
 
 The CAT allocation operation lists the allocation of disk space for indexes and the number of shards on each node.
 
-#### Example
+## Example
 
 ```json
 GET _cat/allocation?v

From 4b4675df58ca0c18df99f00706d7a55afe5bb677 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:15:12 +0500
Subject: [PATCH 06/14] Update cat-cluster_manager.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-cluster_manager.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-cluster_manager.md b/_api-reference/cat/cat-cluster_manager.md
index 29eb313da9..abf204ce16 100644
--- a/_api-reference/cat/cat-cluster_manager.md
+++ b/_api-reference/cat/cat-cluster_manager.md
@@ -14,7 +14,7 @@ has_children: false
 
 The CAT cluster manager operation lists information that helps identify the elected cluster manager node.
 
-#### Example
+## Example
 
 ```
 GET _cat/cluster_manager?v

From fc8a276b8fedeffc85d00e57c7853da024cc50a6 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:15:23 +0500
Subject: [PATCH 07/14] Update cat-count.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-count.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-count.md b/_api-reference/cat/cat-count.md
index 83ce3bc3f2..34baa04dd4 100644
--- a/_api-reference/cat/cat-count.md
+++ b/_api-reference/cat/cat-count.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT count operation lists the number of documents in your cluster.
 
-#### Example
+## Example
 
 ```json
 GET _cat/count?v

From 2cfa11b37c0b59c4708360c27263eb430a1c812a Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:15:35 +0500
Subject: [PATCH 08/14] Update cat-field-data.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-field-data.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-field-data.md b/_api-reference/cat/cat-field-data.md
index 6ab5123cc3..6481e5cea1 100644
--- a/_api-reference/cat/cat-field-data.md
+++ b/_api-reference/cat/cat-field-data.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT fielddata operation lists the memory size used by each field per node.
 
-#### Example
+## Example
 
 ```json
 GET _cat/fielddata?v

From d5be4dd76b4de4d3893c4a74781be18bb7596f83 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 00:15:48 +0500
Subject: [PATCH 09/14] Update cat-health.md

Signed-off-by: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
---
 _api-reference/cat/cat-health.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_api-reference/cat/cat-health.md b/_api-reference/cat/cat-health.md
index c8e2679ff6..6077c77e43 100644
--- a/_api-reference/cat/cat-health.md
+++ b/_api-reference/cat/cat-health.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT health operation lists the status of the cluster, how long the cluster has been up, the number of nodes, and other useful information that helps you analyze the health of your cluster.
 
-#### Example
+## Example
 
 ```json
 GET _cat/health?v

From 73f6fe8722978068d7ea4b5a41eea936c7dd5431 Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 15:43:14 +0000
Subject: [PATCH 10/14] updated

---
 _api-reference/cat/cat-indices.md             | 2 +-
 _api-reference/cat/cat-nodeattrs.md           | 2 +-
 _api-reference/cat/cat-nodes.md               | 2 +-
 _api-reference/cat/cat-pending-tasks.md       | 2 +-
 _api-reference/cat/cat-plugins.md             | 2 +-
 _api-reference/cat/cat-recovery.md            | 2 +-
 _api-reference/cat/cat-repositories.md        | 2 +-
 _api-reference/cat/cat-segment-replication.md | 2 +-
 _api-reference/cat/cat-segments.md            | 2 +-
 _api-reference/cat/cat-shards.md              | 2 +-
 _api-reference/cat/cat-snapshots.md           | 2 +-
 _api-reference/cat/cat-tasks.md               | 2 +-
 _api-reference/cat/cat-templates.md           | 2 +-
 _api-reference/cat/cat-thread-pool.md         | 2 +-
 _api-reference/cat/index.md                   | 2 +-
 15 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/_api-reference/cat/cat-indices.md b/_api-reference/cat/cat-indices.md
index d469838749..daab13938c 100644
--- a/_api-reference/cat/cat-indices.md
+++ b/_api-reference/cat/cat-indices.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT indices operation lists information related to indexes, that is, how much disk space they are using, how many shards they have, their health status, and so on.
 
-#### Example
+## Example
 
 ```
 GET _cat/indices?v
diff --git a/_api-reference/cat/cat-nodeattrs.md b/_api-reference/cat/cat-nodeattrs.md
index 69e6bf786e..95c1e50afc 100644
--- a/_api-reference/cat/cat-nodeattrs.md
+++ b/_api-reference/cat/cat-nodeattrs.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT nodeattrs operation lists the attributes of custom nodes.
 
-#### Example
+## Example
 
 ```
 GET _cat/nodeattrs?v
diff --git a/_api-reference/cat/cat-nodes.md b/_api-reference/cat/cat-nodes.md
index 1f5a0206b9..fa0261a4ed 100644
--- a/_api-reference/cat/cat-nodes.md
+++ b/_api-reference/cat/cat-nodes.md
@@ -17,7 +17,7 @@ The CAT nodes operation lists node-level information, including node roles and l
 
 A few important node metrics are `pid`, `name`, `cluster_manager`, `ip`, `port`, `version`, `build`, `jdk`, along with `disk`, `heap`, `ram`, and `file_desc`.
 
-#### Example
+## Example
 
 ```
 GET _cat/nodes?v
diff --git a/_api-reference/cat/cat-pending-tasks.md b/_api-reference/cat/cat-pending-tasks.md
index e7d18cd546..c8e1b744e8 100644
--- a/_api-reference/cat/cat-pending-tasks.md
+++ b/_api-reference/cat/cat-pending-tasks.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT pending tasks operation lists the progress of all pending tasks, including task priority and time in queue.
 
-#### Example
+## Example
 
 ```
 GET _cat/pending_tasks?v
diff --git a/_api-reference/cat/cat-plugins.md b/_api-reference/cat/cat-plugins.md
index 24281926b6..3498462236 100644
--- a/_api-reference/cat/cat-plugins.md
+++ b/_api-reference/cat/cat-plugins.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT plugins operation lists the names, components, and versions of the installed plugins.
 
-#### Example
+## Example
 
 ```
 GET _cat/plugins?v
diff --git a/_api-reference/cat/cat-recovery.md b/_api-reference/cat/cat-recovery.md
index 712d115a67..54abac6d99 100644
--- a/_api-reference/cat/cat-recovery.md
+++ b/_api-reference/cat/cat-recovery.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT recovery operation lists all completed and ongoing index and shard recoveries.
 
-#### Example
+## Example
 
 ```
 GET _cat/recovery?v
diff --git a/_api-reference/cat/cat-repositories.md b/_api-reference/cat/cat-repositories.md
index 4bbfdb9e87..06d754438f 100644
--- a/_api-reference/cat/cat-repositories.md
+++ b/_api-reference/cat/cat-repositories.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT repositories operation lists all completed and ongoing index and shard recoveries.
 
-#### Example
+## Example
 
 ```
 GET _cat/repositories?v
diff --git a/_api-reference/cat/cat-segment-replication.md b/_api-reference/cat/cat-segment-replication.md
index d93f063905..e22012ea66 100644
--- a/_api-reference/cat/cat-segment-replication.md
+++ b/_api-reference/cat/cat-segment-replication.md
@@ -47,7 +47,7 @@ Parameter | Data type  | Description
 `v` | Boolean    | If `true`, the response includes column headings. Defaults to `false`.
 `s` | String     | Specifies to sort the results. For example, `s=shardId:desc` sorts by shardId in descending order.
 
-#### Example
+## Example
 
 The following examples illustrate various segment replication responses.
 
diff --git a/_api-reference/cat/cat-segments.md b/_api-reference/cat/cat-segments.md
index 2a2977c0ba..b860486692 100644
--- a/_api-reference/cat/cat-segments.md
+++ b/_api-reference/cat/cat-segments.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The cat segments operation lists Lucene segment-level information for each index.
 
-#### Example
+## Example
 
 ```
 GET _cat/segments?v
diff --git a/_api-reference/cat/cat-shards.md b/_api-reference/cat/cat-shards.md
index 7fdf58e659..e74667b5ac 100644
--- a/_api-reference/cat/cat-shards.md
+++ b/_api-reference/cat/cat-shards.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT shards operation lists the state of all primary and replica shards and how they are distributed.
 
-#### Example
+## Example
 
 ```
 GET _cat/shards?v
diff --git a/_api-reference/cat/cat-snapshots.md b/_api-reference/cat/cat-snapshots.md
index 1774753f89..82cb5c1b1f 100644
--- a/_api-reference/cat/cat-snapshots.md
+++ b/_api-reference/cat/cat-snapshots.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT snapshots operation lists all snapshots for a repository.
 
-#### Example
+## Example
 
 ```
 GET _cat/snapshots?v
diff --git a/_api-reference/cat/cat-tasks.md b/_api-reference/cat/cat-tasks.md
index b98a5d3a80..4d2a06cced 100644
--- a/_api-reference/cat/cat-tasks.md
+++ b/_api-reference/cat/cat-tasks.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT tasks operation lists the progress of all tasks currently running on your cluster.
 
-#### Example
+## Example
 
 ```
 GET _cat/tasks?v
diff --git a/_api-reference/cat/cat-templates.md b/_api-reference/cat/cat-templates.md
index 91333b9503..d2aed7b0b8 100644
--- a/_api-reference/cat/cat-templates.md
+++ b/_api-reference/cat/cat-templates.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The CAT templates operation lists the names, patterns, order numbers, and version numbers of index templates.
 
-#### Example
+## Example
 
 ```
 GET _cat/templates?v
diff --git a/_api-reference/cat/cat-thread-pool.md b/_api-reference/cat/cat-thread-pool.md
index d7d145277d..5d3e341b74 100644
--- a/_api-reference/cat/cat-thread-pool.md
+++ b/_api-reference/cat/cat-thread-pool.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The CAT thread pool operation lists the active, queued, and rejected threads of different thread pools on each node.
 
-#### Example
+## Example
 
 ```
 GET _cat/thread_pool?v
diff --git a/_api-reference/cat/index.md b/_api-reference/cat/index.md
index 2407156323..0ddaf1e0a7 100644
--- a/_api-reference/cat/index.md
+++ b/_api-reference/cat/index.md
@@ -15,7 +15,7 @@ You can get essential statistics about your cluster in an easy-to-understand, ta
 
 Using the CAT API, you can answer questions like which node is the elected master, what state is the cluster in, how many documents are in each index, and so on.
 
-#### Example
+## Example
 
 To see the available operations in the CAT API, use the following command:
 

From c931acd591556d10786ab58ce0e21cdb107a023d Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Wed, 18 Oct 2023 16:03:18 +0000
Subject: [PATCH 11/14] updated

---
 _api-reference/cluster-api/cluster-allocation.md   | 2 +-
 _api-reference/cluster-api/cluster-awareness.md    | 6 +++---
 _api-reference/cluster-api/cluster-decommission.md | 4 ++--
 _api-reference/cluster-api/cluster-health.md       | 2 +-
 _api-reference/cluster-api/cluster-stats.md        | 2 +-
 5 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/_api-reference/cluster-api/cluster-allocation.md b/_api-reference/cluster-api/cluster-allocation.md
index b68d49f138..da6e3aab05 100644
--- a/_api-reference/cluster-api/cluster-allocation.md
+++ b/_api-reference/cluster-api/cluster-allocation.md
@@ -17,7 +17,7 @@ The most basic cluster allocation explain request finds an unassigned shard and
 If you add some options, you can instead get information on a specific shard, including why OpenSearch assigned it to its current node.
 
 
-#### Example
+## Example
 
 ```json
 GET _cluster/allocation/explain?include_yes_decisions=true
diff --git a/_api-reference/cluster-api/cluster-awareness.md b/_api-reference/cluster-api/cluster-awareness.md
index 74129fae06..18259b9a98 100644
--- a/_api-reference/cluster-api/cluster-awareness.md
+++ b/_api-reference/cluster-api/cluster-awareness.md
@@ -51,7 +51,7 @@ In the following example request body, `zone_1` and `zone_2` receive 50 requests
 }
 ```
 
-#### Example: Weighted round robin search
+## Example: Weighted round robin search
 
 The following example request creates a round robin shard allocation for search traffic by using an undefined ratio:
 
@@ -80,7 +80,7 @@ PUT /_cluster/routing/awareness/zone/weights
 ```
 
 
-#### Example: Getting weights for all zones
+## Example: Getting weights for all zones
 
 The following example request gets weights for all zones.
 
@@ -108,7 +108,7 @@ OpenSearch responds with the weight of each zone:
 }
 ```
 
-#### Example: Deleting weights
+## Example: Deleting weights
 
 You can remove your weight ratio for each zone using the `DELETE` method.
 
diff --git a/_api-reference/cluster-api/cluster-decommission.md b/_api-reference/cluster-api/cluster-decommission.md
index 221e551f83..867f58eda0 100644
--- a/_api-reference/cluster-api/cluster-decommission.md
+++ b/_api-reference/cluster-api/cluster-decommission.md
@@ -34,7 +34,7 @@ awareness_attribute_name | String | The name of awareness attribute, usually `zo
 awareness_attribute_value | String | The value of the awareness attribute. For example, if you have shards allocated in two different zones, you can give each zone a value of `zone-a` or `zoneb`. The cluster decommission operation decommissions the zone listed in the method.
 
 
-#### Example: Decommissioning and recommissioning a zone
+## Example: Decommissioning and recommissioning a zone
 
 You can use the following example requests to decommission and recommission a zone:
 
@@ -63,7 +63,7 @@ DELETE /_cluster/decommission/awareness
 }
 ```
 
-#### Example: Getting zone decommission status
+## Example: Getting zone decommission status
 
 The following example requests returns the decommission status of all zones.
 
diff --git a/_api-reference/cluster-api/cluster-health.md b/_api-reference/cluster-api/cluster-health.md
index 0ef534c60c..e9e2bb0e47 100644
--- a/_api-reference/cluster-api/cluster-health.md
+++ b/_api-reference/cluster-api/cluster-health.md
@@ -17,7 +17,7 @@ The most basic cluster health request returns a simple status of the health of y
 
 To get the status of a specific index, provide the index name.
 
-#### Example
+## Example
 
 This request waits 50 seconds for the cluster to reach the yellow status or better:
 
diff --git a/_api-reference/cluster-api/cluster-stats.md b/_api-reference/cluster-api/cluster-stats.md
index de598bb90f..bbfaacc284 100644
--- a/_api-reference/cluster-api/cluster-stats.md
+++ b/_api-reference/cluster-api/cluster-stats.md
@@ -15,7 +15,7 @@ redirect_from:
 
 The cluster stats API operation returns statistics about your cluster.
 
-#### Example
+## Example
 
 ```json
 GET _cluster/stats/nodes/_cluster_manager

From adc08368c1bf07caac1b7175f39f778712e5287c Mon Sep 17 00:00:00 2001
From: MUHAMMAD SAMIULLAH <samipak458@gmail.com>
Date: Thu, 19 Oct 2023 08:27:04 +0000
Subject: [PATCH 12/14] updated

---
 _api-reference/count.md                            | 2 +-
 _api-reference/document-apis/bulk.md               | 2 +-
 _api-reference/document-apis/delete-by-query.md    | 2 +-
 _api-reference/document-apis/delete-document.md    | 2 +-
 _api-reference/document-apis/get-documents.md      | 2 +-
 _api-reference/document-apis/index-document.md     | 2 +-
 _api-reference/document-apis/reindex.md            | 2 +-
 _api-reference/document-apis/update-by-query.md    | 2 +-
 _api-reference/document-apis/update-document.md    | 2 +-
 _api-reference/explain.md                          | 2 +-
 _api-reference/index-apis/alias.md                 | 2 +-
 _api-reference/index-apis/clone.md                 | 2 +-
 _api-reference/index-apis/dangling-index.md        | 2 +-
 _api-reference/index-apis/delete-index.md          | 2 +-
 _api-reference/index-apis/exists.md                | 2 +-
 _api-reference/index-apis/get-index.md             | 2 +-
 _api-reference/index-apis/get-settings.md          | 2 +-
 _api-reference/index-apis/open-index.md            | 2 +-
 _api-reference/index-apis/put-mapping.md           | 6 +++---
 _api-reference/index-apis/shrink-index.md          | 6 +++---
 _api-reference/index-apis/split.md                 | 4 ++--
 _api-reference/index-apis/update-settings.md       | 2 +-
 _api-reference/ingest-apis/processors/append.md    | 2 +-
 _api-reference/ingest-apis/processors/bytes.md     | 2 +-
 _api-reference/ingest-apis/processors/convert.md   | 2 +-
 _api-reference/ingest-apis/processors/csv.md       | 2 +-
 _api-reference/ingest-apis/processors/date.md      | 2 +-
 _api-reference/ingest-apis/processors/lowercase.md | 2 +-
 _api-reference/ingest-apis/processors/remove.md    | 2 +-
 _api-reference/ingest-apis/processors/uppercase.md | 2 +-
 _api-reference/multi-search.md                     | 2 +-
 _api-reference/nodes-apis/index.md                 | 2 +-
 _api-reference/nodes-apis/nodes-info.md            | 2 +-
 _api-reference/scroll.md                           | 2 +-
 _api-reference/search.md                           | 2 +-
 _api-reference/snapshots/create-repository.md      | 2 +-
 36 files changed, 41 insertions(+), 41 deletions(-)

diff --git a/_api-reference/count.md b/_api-reference/count.md
index f91c9f6bc7..6a61a93866 100644
--- a/_api-reference/count.md
+++ b/_api-reference/count.md
@@ -13,7 +13,7 @@ redirect_from:
 The count API gives you quick access to the number of documents that match a query.
 You can also use it to check the document count of an index, data stream, or cluster.
 
-#### Example
+## Example
 
 To see the number of documents that match a query:
 
diff --git a/_api-reference/document-apis/bulk.md b/_api-reference/document-apis/bulk.md
index 32f0fb6b46..1ea163f6fe 100644
--- a/_api-reference/document-apis/bulk.md
+++ b/_api-reference/document-apis/bulk.md
@@ -17,7 +17,7 @@ The bulk operation lets you add, update, or delete multiple documents in a singl
 Beginning in OpenSearch 2.9, when indexing documents using the bulk operation, the document `_id` must be 512 bytes or less in size.
 {: .note}
 
-#### Example
+## Example
 
 ```json
 POST _bulk
diff --git a/_api-reference/document-apis/delete-by-query.md b/_api-reference/document-apis/delete-by-query.md
index c57f85035d..eedf79f9f6 100644
--- a/_api-reference/document-apis/delete-by-query.md
+++ b/_api-reference/document-apis/delete-by-query.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can include a query as part of your delete request so OpenSearch deletes all documents that match that query.
 
-#### Example
+## Example
 
 ```json
 POST sample-index1/_delete_by_query
diff --git a/_api-reference/document-apis/delete-document.md b/_api-reference/document-apis/delete-document.md
index beee9c4697..c3dea2f7e1 100644
--- a/_api-reference/document-apis/delete-document.md
+++ b/_api-reference/document-apis/delete-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you no longer need a document in your index, you can use the delete document API operation to delete it.
 
-#### Example
+## Example
 
 ```
 DELETE /sample-index1/_doc/1
diff --git a/_api-reference/document-apis/get-documents.md b/_api-reference/document-apis/get-documents.md
index 876c62a128..d5c2e52d93 100644
--- a/_api-reference/document-apis/get-documents.md
+++ b/_api-reference/document-apis/get-documents.md
@@ -13,7 +13,7 @@ redirect_from:
 
 After adding a JSON document to your index, you can use the get document API operation to retrieve the document's information and data.
 
-#### Example
+## Example
 
 ```json
 GET sample-index1/_doc/1
diff --git a/_api-reference/document-apis/index-document.md b/_api-reference/document-apis/index-document.md
index 7922f715c6..44f0e5e0b7 100644
--- a/_api-reference/document-apis/index-document.md
+++ b/_api-reference/document-apis/index-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 Before you can search for data, you must first add documents. This operation adds a single document to your index.
 
-#### Example
+## Example
 
 ```json
 PUT sample-index/_doc/1
diff --git a/_api-reference/document-apis/reindex.md b/_api-reference/document-apis/reindex.md
index 539e116d69..766f5b2872 100644
--- a/_api-reference/document-apis/reindex.md
+++ b/_api-reference/document-apis/reindex.md
@@ -14,7 +14,7 @@ redirect_from:
 
 The reindex document API operation lets you copy all or a subset of your data from a source index into a destination index.
 
-#### Example
+## Example
 
 ```json
 POST /_reindex
diff --git a/_api-reference/document-apis/update-by-query.md b/_api-reference/document-apis/update-by-query.md
index 5f411b5d2d..b53c31933f 100644
--- a/_api-reference/document-apis/update-by-query.md
+++ b/_api-reference/document-apis/update-by-query.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can include a query and a script as part of your update request so OpenSearch can run the script to update all of the documents that match the query.
 
-#### Example
+## Example
 
 ```json
 POST test-index1/_update_by_query
diff --git a/_api-reference/document-apis/update-document.md b/_api-reference/document-apis/update-document.md
index cb3fa082c3..d233605a3b 100644
--- a/_api-reference/document-apis/update-document.md
+++ b/_api-reference/document-apis/update-document.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you need to update a document's fields in your index, you can use the update document API operation. You can do so by specifying the new data you want in your index or by including a script in your request body, which OpenSearch runs to update the document.
 
-#### Example
+## Example
 
 ```json
 POST /sample-index1/_update/1
diff --git a/_api-reference/explain.md b/_api-reference/explain.md
index 96dd380254..57b7d9fada 100644
--- a/_api-reference/explain.md
+++ b/_api-reference/explain.md
@@ -18,7 +18,7 @@ The explain API is an expensive operation in terms of both resources and time. O
 {: .warning }
 
 
-#### Example
+## Example
 
 To see the explain output for all results, set the `explain` flag to `true` either in the URL or in the body of the request:
 
diff --git a/_api-reference/index-apis/alias.md b/_api-reference/index-apis/alias.md
index 09379f309b..a38a3798a4 100644
--- a/_api-reference/index-apis/alias.md
+++ b/_api-reference/index-apis/alias.md
@@ -15,7 +15,7 @@ redirect_from:
 An alias is a virtual pointer that you can use to reference one or more indexes. Creating and updating aliases are atomic operations, so you can reindex your data and point an alias at it without any downtime.
 
 
-#### Example
+## Example
 
 ```json
 POST _aliases
diff --git a/_api-reference/index-apis/clone.md b/_api-reference/index-apis/clone.md
index dfe2e5f6c3..60228b5894 100644
--- a/_api-reference/index-apis/clone.md
+++ b/_api-reference/index-apis/clone.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The clone index API operation clones all data in an existing read-only index into a new index. The new index cannot already exist.
 
-#### Example
+## Example
 
 ```json
 PUT /sample-index1/_clone/cloned-index1
diff --git a/_api-reference/index-apis/dangling-index.md b/_api-reference/index-apis/dangling-index.md
index e05a588b53..facd8b0c25 100644
--- a/_api-reference/index-apis/dangling-index.md
+++ b/_api-reference/index-apis/dangling-index.md
@@ -49,7 +49,7 @@ accept_data_loss | Boolean | Must be set to `true` for an `import` or `delete` b
 timeout | Time units | The amount of time to wait for a response. If no response is received in the defined time period, an error is returned. Default is `30` seconds.
 cluster_manager_timeout | Time units | The amount of time to wait for a connection to the cluster manager. If no response is received in the defined time period, an error is returned. Default is `30` seconds.
 
-#### Examples
+## Examples
 
 The following are example requests and a example response.
 
diff --git a/_api-reference/index-apis/delete-index.md b/_api-reference/index-apis/delete-index.md
index 015cb29783..5973a8cfdf 100644
--- a/_api-reference/index-apis/delete-index.md
+++ b/_api-reference/index-apis/delete-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 If you no longer need an index, you can use the delete index API operation to delete it.
 
-#### Example
+## Example
 
 ```json
 DELETE /sample-index
diff --git a/_api-reference/index-apis/exists.md b/_api-reference/index-apis/exists.md
index 8bb8f80893..6d439a96cf 100644
--- a/_api-reference/index-apis/exists.md
+++ b/_api-reference/index-apis/exists.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The index exists API operation returns whether or not an index already exists.
 
-#### Example
+## Example
 
 ```json
 HEAD /sample-index
diff --git a/_api-reference/index-apis/get-index.md b/_api-reference/index-apis/get-index.md
index 29052e6455..899e82e901 100644
--- a/_api-reference/index-apis/get-index.md
+++ b/_api-reference/index-apis/get-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 You can use the get index API operation to return information about an index.
 
-#### Example
+## Example
 
 ```json
 GET /sample-index
diff --git a/_api-reference/index-apis/get-settings.md b/_api-reference/index-apis/get-settings.md
index 6b727a78e5..37ac291a77 100644
--- a/_api-reference/index-apis/get-settings.md
+++ b/_api-reference/index-apis/get-settings.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The get settings API operation returns all the settings in your index.
 
-#### Example
+## Example
 
 ```json
 GET /sample-index1/_settings
diff --git a/_api-reference/index-apis/open-index.md b/_api-reference/index-apis/open-index.md
index cf0af67742..6ca0348695 100644
--- a/_api-reference/index-apis/open-index.md
+++ b/_api-reference/index-apis/open-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The open index API operation opens a closed index, letting you add or search for data within the index.
 
-#### Example
+## Example
 
 ```json
 POST /sample-index/_open
diff --git a/_api-reference/index-apis/put-mapping.md b/_api-reference/index-apis/put-mapping.md
index 59c7bd6b00..5f6be9f138 100644
--- a/_api-reference/index-apis/put-mapping.md
+++ b/_api-reference/index-apis/put-mapping.md
@@ -43,9 +43,9 @@ The request body must contain `properties`, which has all of the mappings that y
 }
 ```
 
-#### Optional request body fields
+## Optional request body fields
 
-#### dynamic
+### dynamic
 
 You can make the document structure match the structure of the index mapping by setting the `dynamic` request body field to `strict`, as seen in the following example:
 
@@ -60,7 +60,7 @@ You can make the document structure match the structure of the index mapping by
 }
 ```
 
-#### Optional query parameters
+## Optional query parameters
 
 Optionally, you can add query parameters to make a more specific request. For example, to skip any missing or closed indexes in the response, you can add the `ignore_unavailable` query parameter to your request as follows:
 
diff --git a/_api-reference/index-apis/shrink-index.md b/_api-reference/index-apis/shrink-index.md
index d17dee0650..17b7c4dff6 100644
--- a/_api-reference/index-apis/shrink-index.md
+++ b/_api-reference/index-apis/shrink-index.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The shrink index API operation moves all of your data in an existing index into a new index with fewer primary shards.
 
-#### Example
+## Example
 
 ```json
 POST /my-old-index/_shrink/my-new-index
@@ -68,7 +68,7 @@ alias | Object | Sets an alias for the target index. Can have the fields `filter
 settings | Object | Index settings you can apply to your target index. See [Index Settings]({{site.url}}{{site.baseurl}}/im-plugin/index-settings/).
 [max_shard_size](#the-max_shard_size-parameter) | Bytes | Specifies the maximum size of a primary shard in the target index. Because `max_shard_size` conflicts with the `index.number_of_shards` setting, you cannot set both of them at the same time. 
 
-#### The `max_shard_size` parameter
+### The `max_shard_size` parameter
 
 The `max_shard_size` parameter specifies the maximum size of a primary shard in the target index. OpenSearch uses `max_shard_size` and the total storage for all primary shards in the source index to calculate the number of primary shards and their size for the target index. 
 
@@ -82,6 +82,6 @@ The maximum number of primary shards for the target index is equal to the number
 The minimum number of primary shards for the target index is 1.
 {: .note}
 
-#### Index codec considerations
+## Index codec considerations
 
 For index codec considerations, see [Index codecs]({{site.url}}{{site.baseurl}}/im-plugin/index-codecs/#splits-and-shrinks).
\ No newline at end of file
diff --git a/_api-reference/index-apis/split.md b/_api-reference/index-apis/split.md
index 51f4958d10..03b2f742d1 100644
--- a/_api-reference/index-apis/split.md
+++ b/_api-reference/index-apis/split.md
@@ -13,7 +13,7 @@ redirect_from:
 
 The split index API operation splits an existing read-only index into a new index, cutting each primary shard into some amount of primary shards in the new index.
 
-#### Example
+## Example
 
 ```json
 PUT /sample-index1/_split/split-index1
@@ -76,6 +76,6 @@ The split index API operation creates a new target index, so you can specify any
 }
 ```
 
-#### Index codec considerations
+## Index codec considerations
 
 For index codec considerations, see [Index codecs]({{site.url}}{{site.baseurl}}/im-plugin/index-codecs/#splits-and-shrinks).
\ No newline at end of file
diff --git a/_api-reference/index-apis/update-settings.md b/_api-reference/index-apis/update-settings.md
index bcaed91eda..20a33f24ea 100644
--- a/_api-reference/index-apis/update-settings.md
+++ b/_api-reference/index-apis/update-settings.md
@@ -15,7 +15,7 @@ You can use the update settings API operation to update index-level settings. Yo
 
 Aside from the static and dynamic index settings, you can also update individual plugins' settings. To get the full list of updatable settings, run `GET <target-index>/_settings?include_defaults=true`.
 
-#### Example
+## Example
 
 ```json
 PUT /sample-index1/_settings
diff --git a/_api-reference/ingest-apis/processors/append.md b/_api-reference/ingest-apis/processors/append.md
index f35b96b408..7ed7b276e6 100644
--- a/_api-reference/ingest-apis/processors/append.md
+++ b/_api-reference/ingest-apis/processors/append.md
@@ -15,7 +15,7 @@ The `append` processor is used to add values to a field:
 - If the field is a scalar field, the `append` processor converts it to an array and appends the specified values to that array.
 - If the field does not exist, the `append` processor creates an array with the specified values.
 
-#### Example
+### Example
 The following is the syntax for the `append` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/bytes.md b/_api-reference/ingest-apis/processors/bytes.md
index 717e4fac64..0cc681a692 100644
--- a/_api-reference/ingest-apis/processors/bytes.md
+++ b/_api-reference/ingest-apis/processors/bytes.md
@@ -12,7 +12,7 @@ nav_order: 20
 
 The `bytes` processor converts a human-readable byte value to its equivalent value in bytes. The field can be a scalar or an array. If the field is a scalar, the value is converted and stored in the field. If the field is an array, all values of the array are converted.
 
-#### Example
+### Example
 The following is the syntax for the `bytes` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/convert.md b/_api-reference/ingest-apis/processors/convert.md
index cdd7d0c7be..2bfd331c99 100644
--- a/_api-reference/ingest-apis/processors/convert.md
+++ b/_api-reference/ingest-apis/processors/convert.md
@@ -12,7 +12,7 @@ nav_order: 30
 
 The `convert` processor converts a field in a document to a different type, for example, a string to an integer or an integer to a string. For an array field, all values in the array are converted. 
 
-#### Example
+## Example
 The following is the syntax for the `convert` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/csv.md b/_api-reference/ingest-apis/processors/csv.md
index 1f4e44ddac..8ee045ce93 100644
--- a/_api-reference/ingest-apis/processors/csv.md
+++ b/_api-reference/ingest-apis/processors/csv.md
@@ -12,7 +12,7 @@ nav_order: 40
 
 The `csv` processor is used to parse CSVs and store them as individual fields in a document. The processor ignores empty fields. 
 
-#### Example
+## Example
 The following is the syntax for the `csv` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/date.md b/_api-reference/ingest-apis/processors/date.md
index 41bf971dc1..612347f881 100644
--- a/_api-reference/ingest-apis/processors/date.md
+++ b/_api-reference/ingest-apis/processors/date.md
@@ -12,7 +12,7 @@ nav_order: 50
 
 The `date` processor is used to parse dates from document fields and to add the parsed data to a new field. By default, the parsed data is stored in the `@timestamp` field. 
 
-#### Example
+## Example
 The following is the syntax for the `date` processor:
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/lowercase.md b/_api-reference/ingest-apis/processors/lowercase.md
index bbe1a82b01..63d6cddb21 100644
--- a/_api-reference/ingest-apis/processors/lowercase.md
+++ b/_api-reference/ingest-apis/processors/lowercase.md
@@ -12,7 +12,7 @@ nav_order: 210
 
 The `lowercase` processor converts all the text in a specific field to lowercase letters. 
 
-#### Example
+## Example
 The following is the syntax for the `lowercase` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/remove.md b/_api-reference/ingest-apis/processors/remove.md
index 64ff4a7411..c79023ba53 100644
--- a/_api-reference/ingest-apis/processors/remove.md
+++ b/_api-reference/ingest-apis/processors/remove.md
@@ -12,7 +12,7 @@ nav_order: 230
 
 The `remove` processor is used to remove a field from a document. 
 
-#### Example
+## Example
 The following is the syntax for the `remove` processor: 
 
 ```json
diff --git a/_api-reference/ingest-apis/processors/uppercase.md b/_api-reference/ingest-apis/processors/uppercase.md
index 4f29cc5a55..b586325dc5 100644
--- a/_api-reference/ingest-apis/processors/uppercase.md
+++ b/_api-reference/ingest-apis/processors/uppercase.md
@@ -12,7 +12,7 @@ nav_order: 310
 
 The `uppercase` processor converts all the text in a specific field to uppercase letters. 
 
-#### Example
+## Example
 The following is the syntax for the `uppercase` processor: 
 
 ```json
diff --git a/_api-reference/multi-search.md b/_api-reference/multi-search.md
index 72fe5edef2..25f28c5e7c 100644
--- a/_api-reference/multi-search.md
+++ b/_api-reference/multi-search.md
@@ -12,7 +12,7 @@ redirect_from:
 
 As the name suggests, the multi-search operation lets you bundle multiple search requests into a single request. OpenSearch then executes the searches in parallel, so you get back the response more quickly compared to sending one request per search. OpenSearch executes each search independently, so the failure of one doesn't affect the others.
 
-#### Example
+## Example
 
 ```json
 GET _msearch
diff --git a/_api-reference/nodes-apis/index.md b/_api-reference/nodes-apis/index.md
index ab6867ca9a..ac5e767e33 100644
--- a/_api-reference/nodes-apis/index.md
+++ b/_api-reference/nodes-apis/index.md
@@ -61,7 +61,7 @@ GET /_nodes/data:true/stats
 ```
 {% include copy-curl.html %}
 
-#### Order of resolution mechanisms
+### Order of resolution mechanisms
 
 The order of resolution mechanisms is applied sequentially, and each can add or remove nodes. The following examples yield different results.
 
diff --git a/_api-reference/nodes-apis/nodes-info.md b/_api-reference/nodes-apis/nodes-info.md
index cc7812c224..f8dfd1f136 100644
--- a/_api-reference/nodes-apis/nodes-info.md
+++ b/_api-reference/nodes-apis/nodes-info.md
@@ -18,7 +18,7 @@ The nodes info API represents mostly static information about your cluster's nod
 - Thread pools settings 
 - Installed plugins
 
-#### Example
+## Example
 
 To get information about all nodes in a cluster, use the following query:
 
diff --git a/_api-reference/scroll.md b/_api-reference/scroll.md
index 701c7d8ca2..cee599902d 100644
--- a/_api-reference/scroll.md
+++ b/_api-reference/scroll.md
@@ -17,7 +17,7 @@ To use the `scroll` operation, add a `scroll` parameter to the request header wi
 Because search contexts consume a lot of memory, we suggest you don't use the `scroll` operation for frequent user queries. Instead, use the `sort` parameter with the `search_after` parameter to scroll responses for user queries.
 {: .note }
 
-#### Example
+## Example
 
 To set the number of results that you want returned for each batch, use the `size` parameter:
 
diff --git a/_api-reference/search.md b/_api-reference/search.md
index cba99348cc..b23929afc5 100644
--- a/_api-reference/search.md
+++ b/_api-reference/search.md
@@ -12,7 +12,7 @@ redirect_from:
 
 The Search API operation lets you execute a search request to search your cluster for data.
 
-#### Example
+## Example
 
 ```json
 GET /movies/_search
diff --git a/_api-reference/snapshots/create-repository.md b/_api-reference/snapshots/create-repository.md
index 0452894058..856332b793 100644
--- a/_api-reference/snapshots/create-repository.md
+++ b/_api-reference/snapshots/create-repository.md
@@ -36,7 +36,7 @@ repository | String | Repository name |
 
 Request parameters depend on the type of repository: `fs` or `s3`.
 
-#### fs repository
+### fs repository
 
 Request field | Description
 :--- | :---

From e673d49f7c18148b5e8047255791fa759e3dfa35 Mon Sep 17 00:00:00 2001
From: samipak458 <samipak458@gmail.com>
Date: Sun, 29 Oct 2023 00:36:54 +0500
Subject: [PATCH 13/14] data prepper update

Signed-off-by: samipak458 <samipak458@gmail.com>
---
 .../common-use-cases/trace-analytics.md       | 28 +++++++++----------
 .../managing-data-prepper/core-apis.md        |  2 +-
 .../managing-data-prepper/peer-forwarder.md   |  4 +--
 3 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/_data-prepper/common-use-cases/trace-analytics.md b/_data-prepper/common-use-cases/trace-analytics.md
index f9c67500bb..9067ce49b7 100644
--- a/_data-prepper/common-use-cases/trace-analytics.md
+++ b/_data-prepper/common-use-cases/trace-analytics.md
@@ -38,8 +38,8 @@ The [OpenTelemetry source]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/c
 
 There are three processors for the trace analytics feature:
 
-* *otel_trace_raw* - The *otel_trace_raw* processor receives a collection of [span](https://github.com/opensearch-project/data-prepper/blob/fa65e9efb3f8d6a404a1ab1875f21ce85e5c5a6d/data-prepper-api/src/main/java/org/opensearch/dataprepper/model/trace/Span.java) records from [*otel-trace-source*]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/otel-trace/), and performs stateful processing, extraction, and completion of trace-group-related fields.
-* *otel_trace_group* - The *otel_trace_group* processor fills in the missing trace-group-related fields in the collection of [span](https://github.com/opensearch-project/data-prepper/blob/298e7931aa3b26130048ac3bde260e066857df54/data-prepper-api/src/main/java/org/opensearch/dataprepper/model/trace/Span.java) records by looking up the OpenSearch backend.
+* *otel_traces_raw* - The *otel_traces_raw* processor receives a collection of [span](https://github.com/opensearch-project/data-prepper/blob/fa65e9efb3f8d6a404a1ab1875f21ce85e5c5a6d/data-prepper-api/src/main/java/org/opensearch/dataprepper/model/trace/Span.java) records from [*otel-trace-source*]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/sources/otel-trace/), and performs stateful processing, extraction, and completion of trace-group-related fields.
+* *otel_traces_group* - The *otel_traces_group* processor fills in the missing trace-group-related fields in the collection of [span](https://github.com/opensearch-project/data-prepper/blob/298e7931aa3b26130048ac3bde260e066857df54/data-prepper-api/src/main/java/org/opensearch/dataprepper/model/trace/Span.java) records by looking up the OpenSearch backend.
 * *service_map_stateful* – The *service_map_stateful* processor performs the required preprocessing for trace data and builds metadata to display the `service-map` dashboards.
 
 
@@ -49,7 +49,7 @@ OpenSearch provides a generic sink that writes data to OpenSearch as the destina
 
 The sink provides specific configurations for the trace analytics feature. These configurations allow the sink to use indexes and index templates specific to trace analytics. The following OpenSearch indexes are specific to trace analytics:
 
-* *otel-v1-apm-span* – The *otel-v1-apm-span* index stores the output from the [otel_trace_raw]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel-trace-raw/) processor.
+* *otel-v1-apm-span* – The *otel-v1-apm-span* index stores the output from the [otel_traces_raw]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/otel-trace-raw/) processor.
 * *otel-v1-apm-service-map* – The *otel-v1-apm-service-map* index stores the output from the [service_map_stateful]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/service-map-stateful/) processor.
 
 ## Trace tuning
@@ -114,13 +114,13 @@ The following sections provide examples of different types of pipelines and how
 
 The following example demonstrates how to build a pipeline that supports the [OpenSearch Dashboards Observability plugin]({{site.url}}{{site.baseurl}}/observability-plugin/trace/ta-dashboards/). This pipeline takes data from the OpenTelemetry Collector and uses two other pipelines as sinks. These two separate pipelines serve two different purposes and write to different OpenSearch indexes. The first pipeline prepares trace data for OpenSearch and enriches and ingests the span documents into a span index within OpenSearch. The second pipeline aggregates traces into a service map and writes service map documents into a service map index within OpenSearch.
 
-Starting with Data Prepper version 2.0, Data Prepper no longer supports the `otel_trace_raw_prepper` processor. The `otel_trace_raw` processor replaces the `otel_trace_raw_prepper` processor and supports some of Data Prepper's recent data model changes. Instead, you should use the `otel_trace_raw` processor. See the following YAML file example:
+Starting with Data Prepper version 2.0, Data Prepper no longer supports the `otel_traces_raw_prepper` processor. The `otel_traces_raw` processor replaces the `otel_traces_raw_prepper` processor and supports some of Data Prepper's recent data model changes. Instead, you should use the `otel_traces_raw` processor. See the following YAML file example:
 
 ```yml
 entry-pipeline:
   delay: "100"
   source:
-    otel_trace_source:
+    otel_traces_source:
       ssl: false
   buffer:
     bounded_blocking:
@@ -140,7 +140,7 @@ raw-pipeline:
       buffer_size: 10240
       batch_size: 160
   processor:
-    - otel_trace_raw:
+    - otel_traces_raw:
   sink:
     - opensearch:
         hosts: ["https://localhost:9200"]
@@ -176,7 +176,7 @@ The following is an example `otel-trace-source` .yaml file with SSL and basic au
 
 ```yaml
 source:
-  otel_trace_source:
+  otel_traces_source:
     #record_type: event  # Add this when using Data Prepper 1.x. This option is removed in 2.0
     ssl: true
     sslKeyCertChainFile: "/full/path/to/certfile.crt"
@@ -202,7 +202,7 @@ otel-trace-pipeline:
   # default value is 3_000 ms
   delay: "100" 
   source:
-    otel_trace_source:
+    otel_traces_source:
       #record_type: event  # Add this when using Data Prepper 1.x. This option is removed in 2.0
       ssl: false # Change this to enable encryption in transit
       authentication:
@@ -242,8 +242,8 @@ raw-pipeline:
          # With 64 as batch size each worker thread could process upto 3200 spans (64 * 50)
          batch_size: 64
   processor:
-    - otel_trace_raw:
-    - otel_trace_group:
+    - otel_traces_raw:
+    - otel_traces_group:
         hosts: [ "https://localhost:9200" ]
         # Change to your credentials
         username: "admin"
@@ -369,9 +369,9 @@ For more information about how to tune and scale Data Prepper for trace analytic
 
 Starting with Data Prepper version 1.4, trace processing uses Data Prepper's event model. This allows pipeline authors to configure other processors to modify spans or traces. To provide a migration path, Data Prepper version 1.4 introduced the following changes:
 
-* `otel_trace_source` has an optional `record_type` parameter that can be set to `event`. When configured, it will output event objects.
-* `otel_trace_raw` replaces `otel_trace_raw_prepper` for event-based spans.
-* `otel_trace_group` replaces `otel_trace_group_prepper` for event-based spans.
+* `otel_traces_source` has an optional `record_type` parameter that can be set to `event`. When configured, it will output event objects.
+* `otel_traces_raw` replaces `otel_traces_raw_prepper` for event-based spans.
+* `otel_traces_group` replaces `otel_traces_group_prepper` for event-based spans.
 
-In Data Prepper version 2.0, `otel_trace_source` will only output events. Data Prepper version 2.0 also removes `otel_trace_raw_prepper` and `otel_trace_group_prepper` entirely. To migrate to Data Prepper version 2.0, you can configure your trace pipeline using the event model.
+In Data Prepper version 2.0, `otel_traces_source` will only output events. Data Prepper version 2.0 also removes `otel_traces_raw_prepper` and `otel_traces_group_prepper` entirely. To migrate to Data Prepper version 2.0, you can configure your trace pipeline using the event model.
  
\ No newline at end of file
diff --git a/_data-prepper/managing-data-prepper/core-apis.md b/_data-prepper/managing-data-prepper/core-apis.md
index c2c88ab531..33fd493d78 100644
--- a/_data-prepper/managing-data-prepper/core-apis.md
+++ b/_data-prepper/managing-data-prepper/core-apis.md
@@ -72,7 +72,7 @@ authentication:
 
 ### Peer Forwarder
 
-Peer Forwarder can be configured to enable stateful aggregation across multiple Data Prepper nodes. For more information about configuring Peer Forwarder, see [Peer forwarder]({{site.url}}{{site.baseurl}}/data-prepper/managing-data-prepper/peer-forwarder/). It is supported by the `service_map_stateful`, `otel_trace_raw`, and `aggregate` processors.
+Peer Forwarder can be configured to enable stateful aggregation across multiple Data Prepper nodes. For more information about configuring Peer Forwarder, see [Peer forwarder]({{site.url}}{{site.baseurl}}/data-prepper/managing-data-prepper/peer-forwarder/). It is supported by the `service_map_stateful`, `otel_traces_raw`, and `aggregate` processors.
 
 ### Shutdown timeouts
 
diff --git a/_data-prepper/managing-data-prepper/peer-forwarder.md b/_data-prepper/managing-data-prepper/peer-forwarder.md
index c5888b6d90..28c7453eef 100644
--- a/_data-prepper/managing-data-prepper/peer-forwarder.md
+++ b/_data-prepper/managing-data-prepper/peer-forwarder.md
@@ -7,9 +7,9 @@ parent: Managing Data Prepper
 
 # Peer forwarder
 
-Peer forwarder is an HTTP service that performs peer forwarding of an `event` between Data Prepper nodes for aggregation. This HTTP service uses a hash-ring approach to aggregate events and determine which Data Prepper node it should handle on a given trace before rerouting it to that node. Currently, peer forwarder is supported by the `aggregate`, `service_map_stateful`, and `otel_trace_raw` [processors]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/processors/).
+Peer forwarder is an HTTP service that performs peer forwarding of an `event` between Data Prepper nodes for aggregation. This HTTP service uses a hash-ring approach to aggregate events and determine which Data Prepper node it should handle on a given trace before rerouting it to that node. Currently, peer forwarder is supported by the `aggregate`, `service_map_stateful`, and `otel_traces_raw` [processors]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/processors/).
 
-Peer forwarder groups events based on the identification keys provided by the supported processors. For `service_map_stateful` and `otel_trace_raw`, the identification key is `traceId` by default and cannot be configured. The `aggregate` processor is configured using the `identification_keys` configuration option. From here, you can specify which keys to use for peer forwarder. See [Aggregate Processor page](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/aggregate-processor#identification_keys) for more information about identification keys.
+Peer forwarder groups events based on the identification keys provided by the supported processors. For `service_map_stateful` and `otel_traces_raw`, the identification key is `traceId` by default and cannot be configured. The `aggregate` processor is configured using the `identification_keys` configuration option. From here, you can specify which keys to use for peer forwarder. See [Aggregate Processor page](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/aggregate-processor#identification_keys) for more information about identification keys.
 
 Peer discovery allows Data Prepper to find other nodes that it will communicate with. Currently, peer discovery is provided by a static list, a DNS record lookup, or AWS Cloud Map.  
 

From 2c51182dd7223e82b016bfdba81ff1f60c41dec2 Mon Sep 17 00:00:00 2001
From: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
Date: Tue, 7 Nov 2023 14:12:17 -0600
Subject: [PATCH 14/14] Update
 _data-prepper/managing-data-prepper/peer-forwarder.md

Signed-off-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com>
---
 _data-prepper/managing-data-prepper/peer-forwarder.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_data-prepper/managing-data-prepper/peer-forwarder.md b/_data-prepper/managing-data-prepper/peer-forwarder.md
index 28c7453eef..f6a0f9890a 100644
--- a/_data-prepper/managing-data-prepper/peer-forwarder.md
+++ b/_data-prepper/managing-data-prepper/peer-forwarder.md
@@ -9,7 +9,7 @@ parent: Managing Data Prepper
 
 Peer forwarder is an HTTP service that performs peer forwarding of an `event` between Data Prepper nodes for aggregation. This HTTP service uses a hash-ring approach to aggregate events and determine which Data Prepper node it should handle on a given trace before rerouting it to that node. Currently, peer forwarder is supported by the `aggregate`, `service_map_stateful`, and `otel_traces_raw` [processors]({{site.url}}{{site.baseurl}}/data-prepper/pipelines/configuration/processors/processors/).
 
-Peer forwarder groups events based on the identification keys provided by the supported processors. For `service_map_stateful` and `otel_traces_raw`, the identification key is `traceId` by default and cannot be configured. The `aggregate` processor is configured using the `identification_keys` configuration option. From here, you can specify which keys to use for peer forwarder. See [Aggregate Processor page](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/aggregate-processor#identification_keys) for more information about identification keys.
+Peer Forwarder groups events based on the identification keys provided by the supported processors. For `service_map_stateful` and `otel_traces_raw`, the identification key is `traceId` by default and cannot be configured. The `aggregate` processor is configured using the `identification_keys` configuration option. From here, you can specify which keys to use for Peer Forwarder. See [Aggregate Processor page](https://github.com/opensearch-project/data-prepper/tree/main/data-prepper-plugins/aggregate-processor#identification_keys) for more information about identification keys.
 
 Peer discovery allows Data Prepper to find other nodes that it will communicate with. Currently, peer discovery is provided by a static list, a DNS record lookup, or AWS Cloud Map.