update manual config

Author: mdbirnstiehl

solutions/observability/streams/management/extract/append.md

@@ -10,6 +10,8 @@ Use the append processor to add a value to an existing array field, or create th
 
 To use an append processor:
 
+1. Select **Create** → **Create processor**.
+1. Select **Append** from the **Processor** menu.
 1. Set **Source Field** to the field you want append values to.
 1. Set **Target field** to the values you want to append to the **Source Field**.
 

solutions/observability/streams/management/extract/date.md

@@ -10,6 +10,8 @@ The date processor parses dates from fields, and then uses the date or timestamp
 
 To extract a timestamp field using the date processor:
 
+1. Select **Create** → **Create processor**.
+1. Select **Date** from the **Processor** menu.
 1. Set the **Source Field** to the field containing the timestamp.
 1. Set the **Format** field to one of the accepted date formats (ISO8602, UNIX, UNIX_MS, or TAI64N) or use a Java time pattern. Refer to the [example formats](#streams-date-examples) for more information.
 

solutions/observability/streams/management/extract/dissect.md

@@ -10,6 +10,9 @@ The dissect processor parses structured log messages and extracts fields from th
 Dissect is much faster than Grok, and is recommend for log messages that follow a consistent, structured format.
 
 To parse a log message with a dissect processor:
+
+1. Select **Create** → **Create processor**.
+1. Select **Dissect** from the **Processor** menu.
 1. Set the **Source Field** to the field you want to dissect
 1. Set the delimiters you want to use in the **Pattern** field. Refer to the [example pattern](#streams-dissect-example) for more information on setting delimiters.
 

solutions/observability/streams/management/extract/manual-pipeline-configuration.md

@@ -3,4 +3,13 @@ applies_to:
   serverless: ga
   stack: preview 9.1, ga 9.2
 ---
-# Manual pipeline configuration [streams-manual-pipeline-configuration]
+# Manual pipeline configuration [streams-manual-pipeline-configuration]
+
+The **Manual pipeline configuration** lets you create a JSON-encoded array of ingest pipeline processors.
+
+To manually create an array of ingest pipeline processors:
+
+1. Select **Create** → **Create processor**.
+1. Select **Manual pipeline configuration** from the **Processor** menu.
+1. Set the **Source Field** to the field you want to dissect
+1. Set the delimiters you want to use in the **Pattern** field. Refer to the [example pattern](#streams-dissect-example) for more information on setting delimiters.

solutions/observability/streams/management/extract/rename.md

@@ -10,6 +10,8 @@ Use the rename processor to change the name of a field, moving its value to a ne
 
 To use a rename processor:
 
+1. Select **Create** → **Create processor**.
+1. Select **Rename** from the **Processor** menu.
 1. Set **Source Field** to the field you want to rename.
 1. Set **Target field** to the new name you want to use for the **Source Field**.
 

solutions/observability/streams/management/extract/set.md

@@ -10,6 +10,8 @@ Use the set processor to assign a specific value to a field, creating the field
 
 To use a set processor:
 
+1. Select **Create** → **Create processor**.
+1. Select **Set** from the **Processor** menu.
 1. Set **Source Field** to the field you want to insert, upsert, or update
 1. Set **Value** to the value you want the source field to be set to.
 

solutions/observability/streams/management/schema.md

@@ -5,7 +5,7 @@ applies_to:
   stack: preview 9.1, ga 9.2
 ---
 
-# Map fields [streams-schema]
+# Map fields in Streams [streams-schema]
 
 Mappings define how {{es}} stores and indexes your data, balancing storage efficiency against query capability and performance.