diff --git a/docs/reference/elasticsearch/rest-apis/search-profile.md b/docs/reference/elasticsearch/rest-apis/search-profile.md
index c31ee1e7e38ff..55244e8a67da0 100644
--- a/docs/reference/elasticsearch/rest-apis/search-profile.md
+++ b/docs/reference/elasticsearch/rest-apis/search-profile.md
@@ -272,9 +272,9 @@ The overall structure of the profile response is as follows:
 % TESTRESPONSE[s/"id": "\[q2aE02wS1R8qQFnYu6vDVQ\]\[my-index-000001\]\[0\]"/"id": $body.profile.shards.0.id/]
 % TESTRESPONSE[s/"node_id": "q2aE02wS1R8qQFnYu6vDVQ",/"node_id": "$body.profile.shards.0.node_id",/]
 % TESTRESPONSE[s/"query": \[\.\.\.\]/"query": $body.$_path/]
-% TESTRESPONSE[s/"collector": \[\.\.\.​\]/"collector": $body.$_path/]
+% TESTRESPONSE[s/"collector": \[\.\.\.\]/"collector": $body.$_path/]
 % TESTRESPONSE[s/"aggregations": \[\.\.\.\]/"aggregations": []/]
-% TESTRESPONSE[s/"fetch": \{\.\.\.​\}/"fetch": $body.$_path/]
+% TESTRESPONSE[s/"fetch": \{\.\.\.\}/"fetch": $body.$_path/]
 
 1. A profile is returned for each shard that participated in the response, and is identified by a unique ID.
 2. If the query was run on the local cluster, the cluster name is left out of the composite id and is marked "(local)" here. For a profile running on a remote_cluster using cross-cluster search, the "id" value would be something like `[q2aE02wS1R8qQFnYu6vDVQ][remote1:my-index-000001][0]` and the "cluster" value would be `remote1`.
@@ -338,7 +338,7 @@ The `query` section contains detailed timing of the query tree executed by Lucen
 % TESTRESPONSE[s/^/{\n"took": $body.took,\n"timed_out": $body.timed_out,\n"_shards": $body._shards,\n"hits": $body.hits,\n"profile": {\n"shards": [ {\n"id": "$body.profile.shards.0.id",\n"node_id": "$body.profile.shards.0.node_id",\n"shard_id": $body.profile.shards.0.shard_id,\n"index": "$body.profile.shards.0.index",\n"cluster": "(local)",\n"searches": [{\n/]
 % TESTRESPONSE[s/]$/],"rewrite_time": $body.$_path, "collector": $body.$_path}], "aggregations": [], "fetch": $body.$_path}]}}/]
 % TESTRESPONSE[s/(?>=[" ])\d+(\.\d+)?/$body.$_path/]
-% TESTRESPONSE[s/"breakdown": \{\.\.\.​\}/"breakdown": $body.$_path/]
+% TESTRESPONSE[s/"breakdown": \{\.\.\.\}/"breakdown": $body.$_path/]
 
 1. The breakdown timings are omitted for simplicity.
 
diff --git a/docs/reference/elasticsearch/rest-apis/search-suggesters.md b/docs/reference/elasticsearch/rest-apis/search-suggesters.md
index 3f8c9d1913b42..904f0a78bea28 100644
--- a/docs/reference/elasticsearch/rest-apis/search-suggesters.md
+++ b/docs/reference/elasticsearch/rest-apis/search-suggesters.md
@@ -276,7 +276,7 @@ The response contains suggestions scored by the most likely spelling correction
 }
 ```
 % TESTRESPONSE[s/"_shards": \.\.\./"_shards": "$body._shards",/]
-% TESTRESPONSE[s/"hits": \.\.\.​/"hits": "$body.hits",/]
+% TESTRESPONSE[s/"hits": \.\.\./"hits": "$body.hits",/]
 % TESTRESPONSE[s/"took": 3,/"took": "$body.took",/]
 
 $$$_basic_phrase_suggest_api_parameters$$$
@@ -621,7 +621,7 @@ It returns this response:
   }
 }
 ```
-% TESTRESPONSE[s/"hits": \.\.\.​/"hits": "$body.hits",/]
+% TESTRESPONSE[s/"hits": \.\.\./"hits": "$body.hits",/]
 % TESTRESPONSE[s/"took": 2,/"took": "$body.took",/]
 
 ::::{important} 
diff --git a/docs/reference/text-analysis/analysis-keyword-repeat-tokenfilter.md b/docs/reference/text-analysis/analysis-keyword-repeat-tokenfilter.md
index 10dc98e1fa4e5..7bb5ecb84b82b 100644
--- a/docs/reference/text-analysis/analysis-keyword-repeat-tokenfilter.md
+++ b/docs/reference/text-analysis/analysis-keyword-repeat-tokenfilter.md
@@ -342,7 +342,7 @@ The API returns the following response. Note that the duplicate tokens for `fox`
 }
 ```
 % TESTRESPONSE[s/"tokenizer": .../"tokenizer": $body.detail.tokenizer/]
-% TESTRESPONSE[s/"tokens": ...​/"tokens": $body.$_path/]
+% TESTRESPONSE[s/"tokens": .../"tokens": $body.$_path/]
 
 ::::