qa devtools

Author: colleenmcginnis

serverless/images/es-badge.svg

@@ -40,7 +40,7 @@ This example walks you through using the **Grok Debugger**.
 [NOTE]
 ====
 The **Admin** role is required to use the Grok Debugger.
-For more information, refer to https://www.elastic.co/docs/current/serverless/general/assign-user-roles[]
+For more information, refer to <<general-assign-user-roles>>
 ====
 
 . From the main menu, click **Developer Tools**, then click **Grok Debugger**.

serverless/images/obs-badge.svg

@@ -163,7 +163,7 @@ GET /my-index-000001/_count
 }
 ----
 
-If the field is aggregatable, you can use https://www.elastic.co/docs/current/serverless/elasticsearch/explore-your-data-aggregations[aggregations]
+If the field is aggregatable, you can use <<elasticsearch-explore-your-data-aggregations,aggregations>>
 to check the field's values. For `keyword` fields, you can use a `terms`
 aggregation to retrieve the field's most common values:
 
@@ -288,7 +288,7 @@ GET /my-index-000001/_settings
 You can update dynamic index settings with the
 https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-put-settings[**Update index settings API**].
 Changing dynamic index settings for a data stream
- requires changing the index template used by the data stream.
+requires changing the index template used by the data stream.
 
 For static settings, you need to create a new index with the correct settings.
 Next, you can reindex the data into that index.

serverless/images/sec-badge.svg

@@ -8,17 +8,24 @@ preview:[]
 
 | <<devtools-run-api-requests-in-the-console,Console>>
 | Interact with Elastic REST APIs.
-| {es-badge}{obs-badge}{sec-badge}
+| {es-badge} +
+{obs-badge} +
+{sec-badge}
 
 | <<devtools-profile-queries-and-aggregations,{searchprofiler}>>
 | Inspect and analyze your search queries.
-| {es-badge}{obs-badge}{sec-badge}
+| {es-badge} +
+{obs-badge} +
+{sec-badge}
 
 | <<devtools-debug-grok-expressions,Grok Debugger>>
 | Build and debug grok patterns before you use them in your data processing pipelines.
-| {es-badge}{obs-badge}{sec-badge}
+| {es-badge} +
+{obs-badge} +
+{sec-badge}
 
 | <<devtools-debug-painless-scripts,Painless Lab>>
 | Use an interactive code editor to test and debug Painless scripts in real time.
-| {obs-badge}{sec-badge}
+| {obs-badge} +
+{sec-badge}
 |===

serverless/pages/devtools/debug-grok-expressions.asciidoc

@@ -142,17 +142,21 @@ components and includes a simple aggregation:
 [role="screenshot"]
 image::images/profiler-gs8.png[Profiling the more complicated query]
 +
+--
 ** The top `BooleanQuery` component corresponds to the `bool` in the query.
 ** The second `BooleanQuery` corresponds to the `terms` query, which is internally
 converted to a `Boolean` of `should` clauses. It has two child queries that correspond
 to "sally" and "sue from the `terms` query.
 ** The `TermQuery` that's labeled with "name:fred" corresponds to `match: fred` in the query.
+--
 +
 In the time columns, the **Self time** and **Total time** are no longer
 identical on all rows:
 +
+--
 ** **Self time** represents how long the query component took to execute.
 ** **Total time** is the time a query component and all its children took to execute.
+--
 +
 Therefore, queries like the Boolean queries often have a larger total time than self time.
 . Select **Aggregation Profile** to view aggregation profiling statistics.