Remove broken URLs to other docs

docs/reference-ml-delete_expired_data.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.deleteExpiredData]]
 === client.ml.deleteExpiredData
 
-Delete expired ML data. Deletes all job results, model snapshots and forecast data that have exceeded their retention days period. Machine learning state documents that are not associated with any job are also deleted. You can limit the request to a single or set of anomaly detection jobs by using a job identifier, a group name, a comma-separated list of jobs, or a wildcard expression. You can delete expired data for all anomaly detection jobs by using _all, by specifying * as the <job_id>, or by omitting the <job_id>.
+Delete expired ML data. Deletes all job results, model snapshots and forecast data that have exceeded their retention days period. Machine learning state documents that are not associated with any job are also deleted. You can limit the request to a single or set of anomaly detection jobs by using a job identifier, a group name, a list of jobs, or a wildcard expression. You can delete expired data for all anomaly detection jobs by using _all, by specifying * as the <job_id>, or by omitting the <job_id>.
 
 {ref}/ml-delete-expired-data.html[{es} documentation]
 

docs/reference-ml-get_data_frame_analytics.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.getDataFrameAnalytics]]
 === client.ml.getDataFrameAnalytics
 
-Get data frame analytics job configuration info. You can get information for multiple data frame analytics jobs in a single API request by using a comma-separated list of data frame analytics jobs or a wildcard expression.
+Get data frame analytics job configuration info. You can get information for multiple data frame analytics jobs in a single API request by using a list of data frame analytics jobs or a wildcard expression.
 
 {ref}/get-dfanalytics.html[{es} documentation]
 

docs/reference-ml-get_datafeed_stats.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.getDatafeedStats]]
 === client.ml.getDatafeedStats
 
-Get datafeeds usage info. You can get statistics for multiple datafeeds in a single API request by using a comma-separated list of datafeeds or a wildcard expression. You can get statistics for all datafeeds by using `_all`, by specifying `*` as the `<feed_id>`, or by omitting the `<feed_id>`. If the datafeed is stopped, the only information you receive is the `datafeed_id` and the `state`. This API returns a maximum of 10,000 datafeeds.
+Get datafeeds usage info. You can get statistics for multiple datafeeds in a single API request by using a list of datafeeds or a wildcard expression. You can get statistics for all datafeeds by using `_all`, by specifying `*` as the `<feed_id>`, or by omitting the `<feed_id>`. If the datafeed is stopped, the only information you receive is the `datafeed_id` and the `state`. This API returns a maximum of 10,000 datafeeds.
 
 {ref}/ml-get-datafeed-stats.html[{es} documentation]
 

docs/reference-ml-get_datafeeds.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.getDatafeeds]]
 === client.ml.getDatafeeds
 
-Get datafeeds configuration info. You can get information for multiple datafeeds in a single API request by using a comma-separated list of datafeeds or a wildcard expression. You can get information for all datafeeds by using `_all`, by specifying `*` as the `<feed_id>`, or by omitting the `<feed_id>`. This API returns a maximum of 10,000 datafeeds.
+Get datafeeds configuration info. You can get information for multiple datafeeds in a single API request by using a list of datafeeds or a wildcard expression. You can get information for all datafeeds by using `_all`, by specifying `*` as the `<feed_id>`, or by omitting the `<feed_id>`. This API returns a maximum of 10,000 datafeeds.
 
 {ref}/ml-get-datafeed.html[{es} documentation]
 

docs/reference-ml-get_jobs.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.getJobs]]
 === client.ml.getJobs
 
-Get anomaly detection jobs configuration info. You can get information for multiple anomaly detection jobs in a single API request by using a group name, a comma-separated list of jobs, or a wildcard expression. You can get information for all anomaly detection jobs by using `_all`, by specifying `*` as the `<job_id>`, or by omitting the `<job_id>`.
+Get anomaly detection jobs configuration info. You can get information for multiple anomaly detection jobs in a single API request by using a group name, a list of jobs, or a wildcard expression. You can get information for all anomaly detection jobs by using `_all`, by specifying `*` as the `<job_id>`, or by omitting the `<job_id>`.
 
 {ref}/ml-get-job.html[{es} documentation]
 

docs/reference-ml-get_trained_models_stats.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.getTrainedModelsStats]]
 === client.ml.getTrainedModelsStats
 
-Get trained models usage info. You can get usage information for multiple trained models in a single API request by using a comma-separated list of model IDs or a wildcard expression.
+Get trained models usage info. You can get usage information for multiple trained models in a single API request by using a list of model IDs or a wildcard expression.
 
 {ref}/get-trained-models-stats.html[{es} documentation]
 

docs/reference-ml-post_data.asciidoc

@@ -29,7 +29,7 @@
 [[client.ml.postData]]
 === client.ml.postData
 
-Send data to an anomaly detection job for analysis. IMPORTANT: For each job, data can be accepted from only a single connection at a time. It is not currently possible to post data to multiple jobs using wildcards or a comma-separated list.
+Send data to an anomaly detection job for analysis. IMPORTANT: For each job, data can be accepted from only a single connection at a time. It is not currently possible to post data to multiple jobs using wildcards or a list.
 
 {ref}/ml-post-data.html[{es} documentation]
 

docs/reference-shared-types-synonyms-types.asciidoc

@@ -41,7 +41,7 @@
 interface SynonymsSynonymRule {
   pass:[/**] @property id Synonym Rule identifier */
   id?: <<Id>>
-  pass:[/**] @property synonyms Synonyms, in Solr format, that conform the synonym rule. See https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-synonym-graph-tokenfilter.html#_solr_synonyms_2 */
+  pass:[/**] @property synonyms Synonyms, in Solr format, that conform the synonym rule. See  */
   synonyms: <<SynonymsSynonymString>>
 }
 [pass]
@@ -60,7 +60,7 @@ interface SynonymsSynonymRule {
 interface SynonymsSynonymRuleRead {
   pass:[/**] @property id Synonym Rule identifier */
   id: <<Id>>
-  pass:[/**] @property synonyms Synonyms, in Solr format, that conform the synonym rule. See https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-synonym-graph-tokenfilter.html#_solr_synonyms_2 */
+  pass:[/**] @property synonyms Synonyms, in Solr format, that conform the synonym rule. See  */
   synonyms: <<SynonymsSynonymString>>
 }
 [pass]