spot check lift-and-shift pages in the text analysis section

Author: colleenmcginnis

manage-data/data-store/text-analysis/index-search-analysis.md

@@ -11,18 +11,17 @@ Index time
 :   When a document is indexed, any [`text`](https://www.elastic.co/guide/en/elasticsearch/reference/current/text.html) field values are analyzed.
 
 Search time
-:   When running a [full-text search](https://www.elastic.co/guide/en/elasticsearch/reference/current/full-text-queries.html) on a `text` field, the query string (the text the user is searching for) is analyzed.
-
-    Search time is also called *query time*.
+:   When running a [full-text search](https://www.elastic.co/guide/en/elasticsearch/reference/current/full-text-queries.html) on a `text` field, the query string (the text the user is searching for) is analyzed. Search time is also called *query time*.
 
+    For more details on text analysis at search time, refer to [Text analysis during search](/solutions/search/full-text/text-analysis-during-search.md).
 
 The analyzer, or set of analysis rules, used at each time is called the *index analyzer* or *search analyzer* respectively.
 
 ## How the index and search analyzer work together [analysis-same-index-search-analyzer]
 
 In most cases, the same analyzer should be used at index and search time. This ensures the values and query strings for a field are changed into the same form of tokens. In turn, this ensures the tokens match as expected during a search.
 
-::::{dropdown} **Example**
+::::{dropdown} Example
 A document is indexed with the following value in a `text` field:
 
 ```text
@@ -79,7 +78,7 @@ While less common, it sometimes makes sense to use different analyzers at index
 
 Generally, a separate search analyzer should only be specified when using the same form of tokens for field values and query strings would create unexpected or irrelevant search matches.
 
-::::{dropdown} **Example**
+::::{dropdown} Example
 :name: different-analyzer-ex
 
 {{es}} is used to create a search engine that matches only words that start with a provided prefix. For instance, a search for `tr` should return `tram` or `trope`—but never `taxi` or `bat`.

manage-data/data-store/text-analysis/token-graphs.md

@@ -50,7 +50,7 @@ In the following graph, `domain name system` and its synonym, `dns`, both have a
 
 However, queries, such as the [`match`](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query.html) or [`match_phrase`](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query-phrase.html) query, can use these graphs to generate multiple sub-queries from a single query string.
 
-:::::{dropdown} **Example**
+:::::{dropdown} Example
 A user runs a search for the following phrase using the `match_phrase` query:
 
 `domain name system is fragile`