- link bulk request to refresh disable docs

- link analyze settings to analyzer update docs
- use markdown links in put settings to avoid duplicates
- add contextual verbiage pointing to linked docs

Author: leemthompo

specification/_global/bulk/BulkRequest.ts

@@ -140,10 +140,14 @@ import { OperationContainer, UpdateAction } from './types'
  * Imagine a `_bulk?refresh=wait_for` request with three documents in it that happen to be routed to different shards in an index with five shards.
  * The request will only wait for those three shards to refresh.
  * The other two shards that make up the index do not participate in the `_bulk` request at all.
+ * 
+ * You might want to disable the refresh interval temporarily to improve indexing throughput for large bulk requests.
+ * Refer to the linked documentation for step-by-step instructions using the index settings API.
  * @rest_spec_name bulk
  * @availability stack stability=stable
  * @availability serverless stability=stable visibility=public
  * @doc_id docs-bulk
+ * @ext_doc_id indices-refresh-disable
  * @doc_tag document
  *
  */

specification/indices/_types/IndexSettings.ts

@@ -70,7 +70,6 @@ export class RetentionLease {
 /**
  * @doc_id index-modules-settings
  * @ext_doc_id index-settings
- * @ext_doc_id analyzer-update-existing
  * @behavior_meta AdditionalProperties fieldname=other_settings description="Additional settings not covered in this type."
  */
 export class IndexSettings
@@ -126,6 +125,8 @@ export class IndexSettings
   max_refresh_listeners?: integer
   /**
    * Settings to define analyzers, tokenizers, token filters and character filters.
+   * Refer to the linked documentation for step-by-step examples of updating analyzers on existing indices.
+   * @ext_doc_id analyzer-update-existing
    */
   analyze?: SettingsAnalyze
   highlight?: SettingsHighlight

specification/indices/put_settings/IndicesPutSettingsRequest.ts

@@ -32,7 +32,7 @@ import { IndexSettings } from '@indices/_types/IndexSettings'
  * To preserve existing settings from being updated, set the `preserve_existing` parameter to `true`.
  *
  * For performance optimization during bulk indexing, you can disable the refresh interval.
- * Refer to the linked documentation for an example.
+ * Refer to [disable refresh interval](https://www.elastic.co/docs/deploy-manage/production-guidance/optimize-performance/indexing-speed#disable-refresh-interval) for an example.
  *  There are multiple valid ways to represent index settings in the request body. You can specify only the setting, for example:
  *
  * ```
@@ -77,15 +77,13 @@ import { IndexSettings } from '@indices/_types/IndexSettings'
  * This affects searches and any new data added to the stream after the rollover.
  * However, it does not affect the data stream's backing indices or their existing data.
  * To change the analyzer for existing backing indices, you must create a new data stream and reindex your data into it.
- * Refer to the linked documentation for step-by-step examples of updating analyzers on existing indices.
+ * Refer to [updating analyzers on existing indices](https://www.elastic.co/docs/manage-data/data-store/text-analysis/specify-an-analyzer#update-analyzers-on-existing-indices) for step-by-step examples.
  * @rest_spec_name indices.put_settings
  * @availability stack stability=stable
  * @availability serverless stability=stable visibility=public
  * @index_privileges manage
  * @doc_id indices-update-settings
  * @ext_doc_id index-settings
- * @ext_doc_id indices-refresh-disable
- * @ext_doc_id analyzer-update-existing
  */
 export interface Request extends RequestBase {
   urls: [