fix grok processor details

Author: mdbirnstiehl

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

@@ -15,7 +15,7 @@ If a pattern doesn't match, the grok processor will try the next pattern. If no
 To improve pipeline performance, start with the most common patterns first, then add more specific patterns. This reduces the number times the grok processor has to run.
 :::
 
-To parse a log message with a dissect processor:
+To parse a log message with a grok processor:
 
 1. Set the **Source Field** to the field you want to search for grok matches.
 1. Set the patterns you want to use in the **Grok patterns** field. Refer to the [example pattern](#streams-grok-example) for more information on patterns.
@@ -60,6 +60,6 @@ To add a generated grok pattern:
 
 Under the hood, the 100 samples on the right side are grouped into categories of similar messages. For each category, a Grok pattern is generated by sending a few samples to the LLM. Matching patterns are then shown in the UI.
 
-:::{note}
+:::{warning}
 This can incur additional costs, depending on the LLM connector you are using. Typically a single iteration uses between 1000 and 5000 tokens depending on the number of identified categories and the length of the messages.
 :::