special character handling

modules/developing/nav.adoc

@@ -1,4 +1,4 @@
-.Develop
+.Development
 * xref:configure-pulsar-env.adoc[]
 * xref:astream-functions.adoc[]
 * xref:astream-kafka.adoc[]

modules/operations/pages/monitoring/index.adoc

@@ -98,8 +98,8 @@ To transform raw metrics into a usable state, {company} recommends the following
 * Aggregate metrics at the parent topic level, at minimum, instead of at the partition level.
 In Pulsar, end user applications only deal with messages at the parent topic level; however, internally, Pulsar handles message processing at the partition level.
 
-* Exclude reported metrics that are associated with {product}'s system namespaces and topics, which are usually prefixed by two underscores (`__`).
-For example, enabling Pulsar's Kafka protocol handler through S4K integration, creates a system namespace called `__kafka` that has one system topic called `\__transaction_producer_state`.
+* Exclude reported metrics that are associated with {product}'s system namespaces and topics, which are usually prefixed by two underscores.
+For example, enabling Pulsar's Kafka protocol handler through S4K integration, creates a system namespace called `\__kafka` that has one system topic called `\__transaction_producer_state`.
 
 === PromQL query patterns
 
@@ -108,13 +108,13 @@ For more information, see the https://prometheus.io/docs/prometheus/latest/query
 
 {company} recommends the following PromQL query patterns for aggregating raw {product} metrics.
 These examples use the `pulsar_msg_backlog` raw metric to demonstrate the patterns.
-Additionally, in accordance with the recommendations in <<aggregate-astra-streaming-metrics>>, these patterns aggregate messages at the parent topic level or higher and they exclude system topics (with the PromQL statement `{topic !~ ".*__.*"}`).
+Additionally, in accordance with the recommendations in <<aggregate-astra-streaming-metrics>>, these patterns aggregate messages at the parent topic level or higher and they exclude system topics (with the PromQL statement `{topic !~ ".\*__.*"}`).
 
 .About the system topics filter
 [%collapsible]
 ====
-The PromQL pattern `{topic !~ ".*__.*"}` filters out messages with topic labels that do not include two consecutive underscores.
-This works because Pulsar system topics and namespaces are usually prefixed by two underscores, such as `persistent://<tenant>/__kafka/__consumer_offsets_partition_0`.
+The PromQL pattern `{topic !~ ".\*_\_.*"}` filters out messages with topic labels that do not include two consecutive underscores.
+This works because Pulsar system topics and namespaces are usually prefixed by two underscores, such as `persistent://**TENANT_NAME**/\__kafka/\__consumer_offsets_partition_0`.
 However, this pattern assumes that your applications' namespace and topic names don't contain double underscores.
 If they do, they are also filtered.
 ====