[DOC] Update ingest pipelines content and page navigation

_api-reference/ingest-apis/create-update-ingest.md

@@ -2,21 +2,21 @@
 layout: default
 title: Create or update ingest pipeline
 parent: Ingest APIs
-nav_order: 11
+nav_order: 10
 redirect_from:
   - /opensearch/rest-api/ingest-apis/create-update-ingest/
 ---
 
-# Create and update a pipeline
+# Create or update a pipeline
 
-The create ingest pipeline API operation creates or updates an ingest pipeline. Each pipeline requires an ingest definition defining how each processor transforms your documents. 
+The create ingest pipeline API operation creates or updates an ingest pipeline. Each pipeline requires an ingest definition defining how each processor transforms your data. 
 
-## Example
+The following is an example of a create pipeline API request: 
 
-```
-PUT _ingest/pipeline/12345
+```json
+PUT _ingest/pipeline/my-pipeline-id
 {
-  "description" : "A description for your pipeline",
+  "description" : "Example pipeline",
   "processors" : [
     {
       "set" : {
@@ -29,51 +29,30 @@ PUT _ingest/pipeline/12345
 ```
 {% include copy-curl.html %}
 
-## Path and HTTP methods
-```
-PUT _ingest/pipeline/{id}
-```
-
 ## Request body fields
 
-Field | Required | Type | Description
-:--- | :--- | :--- | :---
-description | Optional | string | Description of your ingest pipeline. 
-processors | Required | Array of processor objects | A processor that transforms documents. Runs in the order specified. Appears in index once ran.
-
-```json
-{
-  "description" : "A description for your pipeline",
-  "processors" : [
-    {
-      "set" : {
-        "field": "field-name",
-        "value": "value"
-      }
-    }
-  ]
-}
-```
+Field | Type | Description
+:--- | :--- | :---
+`description` | String | Description of the ingest pipeline. Optional. 
+`processors` | Array | The processor that performs an ingest action on the data. Processors run sequentially. Required.
 
-## URL parameters
+## Path parameters
 
-All URL parameters are optional.
+Path parameters are required.
 
 Parameter | Type | Description
 :--- | :--- | :---
-master_timeout | time | How long to wait for a connection to the master node.
-timeout | time | How long to wait for the request to return. 
-
-## Response
-
-```json
-{
-  "acknowledged" : true
-}
-```
-
+`pipeline` | String | Pipeline ID or wildcard expression of pipeline IDs used to limit the request. 
 
+## Query parameters
 
+Query parameters are optional.
 
+Parameter | Type | Description
+:--- | :--- | :---
+master_timeout | Time | Period to wait for a connection to the primary node. Defaults to #s.
+timeout | Time | Period to wait for a response. Defaults to #s. 
 
+## Next steps
 
+Once you've created or updated a pipeline, use the [get ingest pipeline]({{site.url}}{{site.baseurl}}//api-reference/ingest-apis/get-ingest/) API operation to return all the information about the pipeline.

_api-reference/ingest-apis/delete-ingest.md

@@ -2,43 +2,59 @@
 layout: default
 title: Delete a pipeline
 parent: Ingest APIs
-nav_order: 14
+nav_order: 25
 redirect_from:
   - /opensearch/rest-api/ingest-apis/delete-ingest/
 ---
 
 # Delete a pipeline
 
-If you no longer want to use an ingest pipeline, use the delete ingest pipeline API operation.
+The delete ingest pipeline API deletes a pipeline. 
 
-## Example
+#### Request
 
-```
-DELETE _ingest/pipeline/12345
+```json
+DELETE _ingest/pipeline/<pipeline>
 ```
 {% include copy-curl.html %}
 
-## Path and HTTP methods
+## Path parameters
 
-Delete an ingest pipeline based on that pipeline's ID.
+Path parameters are required.
 
-```
-DELETE _ingest/pipeline/
-```
+Parameter | Type | Description
+:--- | :--- | :---
+`pipeline` | String | Pipeline ID or wildcard expression of pipeline IDs used to limit the request. 
+
+To delete all ingest pipelines in a cluster, use a value of *.
 
-## URL parameters
+## Query parameters
 
-All URL parameters are optional.
+Query parameters are optional.
 
 Parameter | Type | Description
 :--- | :--- | :---
-master_timeout | time | How long to wait for a connection to the master node.
-timeout | time | How long to wait for the request to return.
+`master_timeout` | Time | Period to wait for a connection to the primary node. Defaults to #s.
+`timeout` | Time | Period to wait for a response. Defaults to #s.
+
+## Examples
+
+The following are delete pipeline examples.
+
+### Delete a specific pipeline
+
+```json
+DELETE /_ingest/pipeline/pipeline-specific
+```
+
+### Delete pipelines using a wildcard expression
+
+```json
+DELETE /_ingest/pipeline/pipeline-*
+```
 
-## Response
+### Delete all pipelines
 
 ```json
-{
-  "acknowledged" : true
-}
+DELETE /_ingest/pipeline/*
 ```

_api-reference/ingest-apis/get-ingest.md

@@ -2,50 +2,39 @@
 layout: default
 title: Get ingest pipeline
 parent: Ingest APIs
-nav_order: 10
+nav_order: 15
 redirect_from:
   - /opensearch/rest-api/ingest-apis/get-ingest/
 ---
 
-## Get ingest pipeline
+# Get ingest pipeline
 
-After you create a pipeline, use the get ingest pipeline API operation to return all the information about a specific ingest pipeline.
+After creating a pipeline, use the get ingest pipeline API operation to return all the information about the pipeline.
 
-## Example
+## Examples
 
-```
-GET _ingest/pipeline/12345
-```
-{% include copy-curl.html %}
+The following examples return a specific pipeline or all pipelines.
 
-## Path and HTTP methods
-
-Return all ingest pipelines.
+### Return a specific pipeline
 
 ```
-GET _ingest/pipeline
+GET _ingest/pipeline/pipeline-id
 ```
+{% include copy-curl.html %}
 
-Returns a single ingest pipeline based on the pipeline's ID.
+### Return all ingest pipelines
 
 ```
-GET _ingest/pipeline/{id}
+GET _ingest/pipeline
 ```
+{% include copy-curl.html %}
 
-## URL parameters
-
-All parameters are optional.
-
-Parameter | Type | Description
-:--- | :--- | :---
-master_timeout | time | How long to wait for a connection to the master node.
-
-## Response
+#### Example response
 
 ```json
 {
   "pipeline-id" : {
-    "description" : "A description for your pipeline",
+    "description" : "Example description",
     "processors" : [
       {
         "set" : {
@@ -56,4 +45,12 @@ master_timeout | time | How long to wait for a connection to the master node.
     ]
   }
 }
-```
+```
+
+## Query parameters
+
+Query parameters are optional.
+
+Parameter | Type | Description
+:--- | :--- | :---
+master_timeout | Time | Period to wait for a connection to the primary node. Defaults to #s.

_api-reference/ingest-apis/index.md

@@ -9,6 +9,21 @@ redirect_from:
 
 # Ingest APIs
 
-Before you index your data, OpenSearch's ingest APIs help transform your data by creating and managing ingest pipelines. Pipelines consist of **processors**, customizable tasks that run in the order they appear in the request body. The transformed data appears in your index after each of the processor completes.
+Ingest pipelines in OpenSearch can only be managed using ingest API operations. When using ingest in production environments, your cluster should contain at least one node with the node roles permission set to `ingest`. For more information about setting up node roles within a cluster, see [Cluster formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/).
+{: .note}
 
-Ingest pipelines in OpenSearch can only be managed using ingest API operations. When using ingest in production environments, your cluster should contain at least one node with the node roles permission set to `ingest`. For more information on setting up node roles within a cluster, see [Cluster Formation]({{site.url}}{{site.baseurl}}/opensearch/cluster/).
+The OpenSearch ingest APIs simplify the data integration process with a standard and structured way to process large volumes of data, and ingest pipelines pre-process and transform data before it's indexed in OpenSearch. Pipelines consist of processors, customizable tasks that run in the order they appear in the request body. The transformed data appears in your index after each processor completes.
+
+The key fields typically used in a pipeline are `description` and `processors`. The `description` is an optional field that provides a description of the pipeline's purpose or funcationality. The `processors` field is an array that defines the sequence of processing stages within in the pipeline. The output of one processor becomes the input for the next.
+
+```json
+{
+  "description" : "...",
+  "processors" : [ ... ]
+}
+```
+
+## Next steps
+
+- Start first with [creating a pipeline]({{site.url}}{{site.baseurl}}/api-reference/ingest-apis/create-update-ingest/).
+- Learn more about OpenSearch [ingest processors]({{site.url}}{{site.baseurl}}/<index-page-in-progess>).