[DOCS] Fix formatting issue in cardinality-aggregation.asciidoc (#98175) (#98252)

* [DOCS] Fix formatting issue in cardinality-aggregation.asciidoc

Fixes a header not rendering properly because of a missing newline.

* Update docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc

* More issues

* More issues

* Update docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc

Co-authored-by: James Rodewig <[email protected]>

---------

Co-authored-by: James Rodewig <[email protected]>
(cherry picked from commit 962c607)

Author: abdonpijpelink

docs/reference/aggregations/metrics/cardinality-aggregation.asciidoc

@@ -237,9 +237,10 @@ POST /sales/_search?size=0
 --------------------------------------------------
 // TEST[setup:sales]
 <1> Documents without a value in the `tag` field will fall into the same bucket as documents that have the value `N/A`.
-==== Execution Hint
 
-There are different mechanisms by which cardinality aggregations can be executed:
+==== Execution hint
+
+You can run cardinality aggregations using different mechanisms:
 
  - by using field values directly (`direct`)
  - by using global ordinals of the field and resolving those values after
@@ -248,13 +249,14 @@ There are different mechanisms by which cardinality aggregations can be executed
    segment (`segment_ordinals`)
 
 Additionally, there are two "heuristic based" modes.  These modes will cause
-Elasticsearch to use some data about the state of the index to choose an
-appropriate execution method.  The two heuristics are: 
- - `save_time_heuristic` - this is the default in Elasticsearch 8.4 and later.
- - `save_memory_heuristic` - this was the default in Elasticsearch 8.3 and
+{es} to use some data about the state of the index to choose an
+appropriate execution method.  The two heuristics are:
+
+ - `save_time_heuristic` - this is the default in {es} 8.4 and later.
+ - `save_memory_heuristic` - this was the default in {es} 8.3 and
    earlier
 
-When not specified, Elasticsearch will apply a heuristic to chose the
-appropriate mode.  Also note that some data (i.e. non-ordinal fields), `direct`
+When not specified, {es} will apply a heuristic to choose the
+appropriate mode.  Also note that for some data (non-ordinal fields), `direct`
 is the only option, and the hint will be ignored in these cases.  Generally
 speaking, it should not be necessary to set this value.