fix toc

Author: mdbirnstiehl

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

@@ -38,12 +38,22 @@ The previous pattern can then be used in the processor.
 ```
 
 ## Generate patterns [streams-grok-patterns]
+:::{note}
 Requires an LLM Connector to be configured.
+:::
+
 Instead of writing the Grok patterns by hand, you can use the **Generate Patterns** button to generate the patterns for you.
 
+Generated patterns work best on semi-structured data. For very custom logs with a lot of text, creating manual patterns general creates more accurate results.
+
 ![generated patterns](<../../../../images/logs-streams-patterns.png>)
 
-Select **Accept** to add a generated pattern to the list of patterns used by the grok processor.
+To add a generated grok pattern:
+
+1. Select **Create** → **Create processor**.
+1. Select **Grok** from the **Processor** menu.
+1. Select **Generate pattern**.
+1. Select **Accept** to add a generated pattern to the list of patterns used by the grok processor.
 
 ### How does **Generate patterns** work? [streams-grok-pattern-generation]
 % need to check to make sure this is still accurate.

solutions/observability/streams/management/schema.md

@@ -5,4 +5,8 @@ applies_to:
   stack: preview 9.1, ga 9.2
 ---
 
-# Manage field mapping using the Schema tab [streams-data-retention]
+# Manage field mapping using the Schema tab [streams-schema]
+
+## Permissions to edit and add fields [streams-schema-permissions]
+
+## Field statuses [streams-schema-statuses]

solutions/toc.yml

@@ -467,6 +467,8 @@ toc:
             - file: observability/streams/management/extract/append.md
             - file: observability/streams/management/extract/manual-pipeline-configuration.md
         - file: observability/streams/management/retention.md
+        - file: observability/streams/management/schema.md
+        - file: observability/streams/management/data-quality.md
         - file: observability/streams/management/advanced.md
       - file: observability/incident-management.md
         children: