Comment out troublesome URLs

Author: leemthompo

solutions/search/retrievers-examples.md

@@ -392,7 +392,9 @@ Which would return the following results:
 
 ## Example: Grouping results by year with `collapse` [retrievers-examples-collapsing-retriever-results]
 
-In our result set, we have many documents with the same `year` value. We can clean this up using the `collapse` parameter with our retriever. This, as with the standard [collapse](/raw-migrated-files/elasticsearch/elasticsearch-reference/collapse-search-results.md) feature, enables grouping results by any field and returns only the highest-scoring document from each group. In this example we’ll collapse our results based on the `year` field.
+In our result set, we have many documents with the same `year` value. We can clean this up using the `collapse` parameter with our retriever. This, as with the standard 
+% [collapse](/raw-migrated-files/elasticsearch/elasticsearch-reference/collapse-search-results.md) feature,
+enables grouping results by any field and returns only the highest-scoring document from each group. In this example we’ll collapse our results based on the `year` field.
 
 ```console
 GET /retrievers_example/_search
@@ -541,7 +543,9 @@ This returns the following response with collapsed results.
 
 ## Example: Highlighting results based on nested sub-retrievers [retrievers-examples-highlighting-retriever-results]
 
-Highlighting is now also available for nested sub-retrievers matches. For example, consider the same `rrf` retriever as above, with a `knn` and `standard` retriever as its sub-retrievers. We can specify a `highlight` section, as defined in [highlighting](/raw-migrated-files/elasticsearch/elasticsearch-reference/highlighting.md) documentation, and compute highlights for the top results.
+Highlighting is now also available for nested sub-retrievers matches. For example, consider the same `rrf` retriever as above, with a `knn` and `standard` retriever as its sub-retrievers. We can specify a `highlight` section,
+% TODO URL as defined in the [highlighting](/raw-migrated-files/elasticsearch/elasticsearch-reference/highlighting.md) documentation, 
+and compute highlights for the top results.
 
 ```console
 GET /retrievers_example/_search
@@ -738,7 +742,9 @@ POST /retrievers_example_nested/_doc/3
 POST /retrievers_example_nested/_refresh
 ```
 
-Now we can run an `rrf` retriever query and also compute [inner hits](/raw-migrated-files/elasticsearch/elasticsearch-reference/inner-hits.md) for the `nested_field.nested_vector` field, based on the `knn` query specified.
+Now we can run an `rrf` retriever query and also compute inner hits
+% TODO URL [inner hits](/raw-migrated-files/elasticsearch/elasticsearch-reference/inner-hits.md)
+for the `nested_field.nested_vector` field, based on the `knn` query specified.
 
 ```console
 GET /retrievers_example_nested/_search
@@ -1261,7 +1267,10 @@ The output of which, albeit a bit verbose, will provide all the necessary info t
 
 ## Example: Rerank results of an RRF retriever [retrievers-examples-text-similarity-reranker-on-top-of-rrf]
 
-To demonstrate the full functionality of retrievers, the following examples also require access to a [semantic reranking model](/raw-migrated-files/elasticsearch/elasticsearch-reference/semantic-reranking.md#semantic-reranking-models) set up using the [Elastic inference APIs](/raw-migrated-files/elasticsearch/elasticsearch-reference/inference-apis.md).
+To demonstrate the full functionality of retrievers, the following examples also require access to a semantic reranking model
+% TODO URL  [semantic reranking model](/raw-migrated-files/elasticsearch/elasticsearch-reference/semantic-reranking.md#semantic-reranking-models)
+set up using the inference APIs.
+% [Elastic inference APIs](/raw-migrated-files/elasticsearch/elasticsearch-reference/inference-apis.md).
 
 In this example we’ll set up a reranking service and use it with the `text_similarity_reranker` retriever to rerank our top results.