[DOCS] Replace put with create or update in API names (#70330) (#70421)

Co-authored-by: debadair <[email protected]>
Co-authored-by: Lisa Cawley <[email protected]>

Author: 3 people

docs/java-rest/high-level/ccr/put_follow.asciidoc

@@ -5,29 +5,28 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put Follow API
+=== Create follower API
 
 
 [id="{upid}-{api}-request"]
 ==== Request
 
-The Put Follow API allows creates a follower index and make that index follow a leader index.
+Creates a follower index and makes that index follow a leader index.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
 include-tagged::{doc-tests-file}[{api}-request]
 --------------------------------------------------
 <1> The name of the remote cluster alias.
 <2> The name of the leader in the remote cluster.
-<3> The name of the follower index that gets created as part of the put follow API call.
-<4> The number of active shard copies to wait for before the put follow API returns a
-response, as an `ActiveShardCount`
+<3> The name of the follower index to create.
+<4> The number of shard copies that must be active before the call returns.
 <5> The settings overrides for the follower index.
 
 [id="{upid}-{api}-response"]
 ==== Response
 
-The returned +{response}+ indicates if the put follow request was received.
+The +{response}+ indicates if the request was received.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
@@ -38,5 +37,3 @@ include-tagged::{doc-tests-file}[{api}-response]
 <3> Whether the follower index started following the leader index.
 
 include::../execution.asciidoc[]
-
-

docs/java-rest/high-level/cluster/put_component_template.asciidoc

@@ -5,12 +5,12 @@
 --
 
 [id="{upid}-{api}"]
-=== Put Component Template API
+=== Create or update component template API
 
-The Put Component Template API allows to create or change a component template.
+Creates or updates a component template.
 
 [id="{upid}-{api}-request"]
-==== Put Component Template Request
+==== Request
 
 A +{request}+ specifies the name of the component template and the template definition,
 which can consist of the settings, mappings or aliases, together with a version (which
@@ -52,7 +52,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
 include::../execution.asciidoc[]
 
 [id="{upid}-{api}-response"]
-==== Put Component Templates Response
+==== Response
 
 The returned +{response}+ allows to retrieve information about the
 executed operation as follows:

docs/java-rest/high-level/enrich/put_policy.asciidoc

@@ -5,12 +5,12 @@
 --
 
 [id="{upid}-{api}"]
-=== Put Policy API
+=== Create or update enrich policy API
 
 [id="{upid}-{api}-request"]
 ==== Request
 
-The Put Policy API stores an enrich policy in Elasticsearch.
+Creates or updates an enrich policy.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
@@ -20,12 +20,12 @@ include-tagged::{doc-tests-file}[{api}-request]
 [id="{upid}-{api}-response"]
 ==== Response
 
-The returned +{response}+ indicates if the put policy request was acknowledged.
+The +{response}+ indicates if the request was acknowledged.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
 include-tagged::{doc-tests-file}[{api}-response]
 --------------------------------------------------
-<1> Whether put policy request was acknowledged.
+<1> Whether the request was acknowledged.
 
 include::../execution.asciidoc[]

docs/java-rest/high-level/ilm/put_lifecycle_policy.asciidoc

@@ -5,14 +5,13 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put Lifecycle Policy API
+=== Create or update lifecycle policy API
 
 
 [id="{upid}-{api}-request"]
 ==== Request
 
-The Put Lifecycle Policy API allows you to add an Index Lifecycle Management
-Policy to the cluster.
+Creates or updates an index lifecycle management policy.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
@@ -25,14 +24,13 @@ include-tagged::{doc-tests-file}[{api}-request]
 [id="{upid}-{api}-response"]
 ==== Response
 
-The returned +{response}+ indicates if the put lifecycle policy request was received.
+The +{response}+ indicates if the request was received.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
 include-tagged::{doc-tests-file}[{api}-response]
 --------------------------------------------------
-<1> Whether or not the put lifecycle policy was acknowledged.
+<1> Whether or not the request was acknowledged.
 
 include::../execution.asciidoc[]
 
-

docs/java-rest/high-level/ilm/put_snapshot_lifecycle_policy.asciidoc

@@ -5,14 +5,13 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put Snapshot Lifecycle Policy API
+=== Create or update snapshot lifecycle policy API
 
 
 [id="{upid}-{api}-request"]
 ==== Request
 
-The Put Snapshot Lifecycle Policy API allows you to add of update the definition of a Snapshot
-Lifecycle Management Policy in the cluster.
+Creates or updates a snapshot lifecycle management policy.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
@@ -22,14 +21,13 @@ include-tagged::{doc-tests-file}[{api}-request]
 [id="{upid}-{api}-response"]
 ==== Response
 
-The returned +{response}+ indicates if the put snapshot lifecycle policy request was received.
+The +{response}+ indicates if the request was received.
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
 include-tagged::{doc-tests-file}[{api}-response]
 --------------------------------------------------
-<1> Whether or not the put snapshot lifecycle policy was acknowledged.
+<1> Whether or not the request was acknowledged.
 
 include::../execution.asciidoc[]
 
-

docs/java-rest/high-level/indices/put_index_template.asciidoc

@@ -5,10 +5,10 @@
 --
 
 [id="{upid}-{api}"]
-=== Put Composable Index Template API
+=== Create or update composable index template API
 
 [id="{upid}-{api}-request"]
-==== Put Composable Index Template Request
+==== Request
 
 A +{request}+ specifies the `name` of a template and the index template configuration
 which consists of the `patterns` that control whether the template should be applied
@@ -108,7 +108,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
 include::../execution.asciidoc[]
 
 [id="{upid}-{api}-response"]
-==== Put Composable Index Template Response
+==== Response
 
 The returned +{response}+ allows to retrieve information about the
 executed operation as follows:

docs/java-rest/high-level/indices/put_mapping.asciidoc

@@ -5,10 +5,13 @@
 --
 
 [id="{upid}-{api}"]
-=== Put Mapping API
+=== Update mapping API
+
+Adds new fields to an existing data stream or index. You can also use the API to
+change the search settings of existing fields.
 
 [id="{upid}-{api}-request"]
-==== Put Mapping Request
+==== Request
 
 A +{request}+ requires an `index` argument:
 
@@ -63,7 +66,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
 include::../execution.asciidoc[]
 
 [id="{upid}-{api}-response"]
-==== Put Mapping Response
+==== Response
 
 The returned +{response}+ allows to retrieve information about the executed
  operation as follows:

docs/java-rest/high-level/indices/put_template.asciidoc

@@ -5,10 +5,10 @@
 --
 
 [id="{upid}-{api}"]
-=== Put Template API
+=== Create or update index template API
 
 [id="{upid}-{api}-request"]
-==== Put Index Template Request
+==== Request
 
 A +{request}+ specifies the `name` of a template and `patterns`
 which controls whether the template should be applied to the new index.
@@ -120,7 +120,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
 include::../execution.asciidoc[]
 
 [id="{upid}-{api}-response"]
-==== Put Index Template Response
+==== Response
 
 The returned +{response}+ allows to retrieve information about the
 executed operation as follows:

docs/java-rest/high-level/ingest/put_pipeline.asciidoc

@@ -1,8 +1,8 @@
 [[java-rest-high-ingest-put-pipeline]]
-=== Put Pipeline API
+=== Create or update pipeline API
 
 [[java-rest-high-ingest-put-pipeline-request]]
-==== Put Pipeline Request
+==== Request
 
 A `PutPipelineRequest` requires an `id` argument, a source and a `XContentType`. The source consists
 of a description and a list of `Processor` objects.
@@ -44,9 +44,9 @@ include-tagged::{doc-tests}/IngestClientDocumentationIT.java[put-pipeline-execut
 [[java-rest-high-ingest-put-pipeline-async]]
 ==== Asynchronous Execution
 
-The asynchronous execution of a put pipeline request requires both the `PutPipelineRequest`
-instance and an `ActionListener` instance to be passed to the asynchronous
-method:
+The asynchronous execution of a create or update pipeline request requires both
+the `PutPipelineRequest` instance and an `ActionListener` instance to be passed
+to the asynchronous method:
 
 ["source","java",subs="attributes,callouts,macros"]
 --------------------------------------------------
@@ -71,7 +71,7 @@ provided as an argument
 <2> Called in case of failure. The raised exception is provided as an argument
 
 [[java-rest-high-ingest-put-pipeline-response]]
-==== Put Pipeline Response
+==== Response
 
 The returned `WritePipelineResponse` allows to retrieve information about the executed
  operation as follows:

docs/java-rest/high-level/ml/put-calendar-job.asciidoc

@@ -5,14 +5,14 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put {anomaly-jobs} in calendar API
+=== Add {anomaly-jobs} to calendar API
 
 Adds {anomaly-jobs} jobs to an existing {ml} calendar.
 The API accepts a +{request}+ and responds
 with a +{response}+ object.
 
 [id="{upid}-{api}-request"]
-==== Put {anomaly-jobs} in calendar request
+==== Request
 
 A +{request}+ is constructed referencing a non-null
 calendar ID, and JobIDs to which to add to the calendar
@@ -25,7 +25,7 @@ include-tagged::{doc-tests-file}[{api}-request]
 <2> The JobIds to add to the calendar
 
 [id="{upid}-{api}-response"]
-==== Put {anomaly-jobs} in calendar response
+==== Response
 
 The returned +{response}+ contains the updated calendar:
 

docs/java-rest/high-level/ml/put-calendar.asciidoc

@@ -5,14 +5,14 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put calendars API
+=== Create calendars API
 
 Creates a new {ml} calendar.
 The API accepts a +{request}+ and responds
 with a +{response}+ object.
 
 [id="{upid}-{api}-request"]
-==== Put calendars request
+==== Request
 
 A +{request}+ is constructed with a calendar object
 
@@ -24,7 +24,7 @@ include-tagged::{doc-tests-file}[{api}-request]
 
 
 [id="{upid}-{api}-response"]
-==== Put calendars response
+==== Response
 
 The returned +{response}+ contains the created calendar:
 

docs/java-rest/high-level/ml/put-data-frame-analytics.asciidoc

@@ -5,15 +5,15 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put {dfanalytics-jobs} API
+=== Create {dfanalytics-jobs} API
 
 beta::[]
 
 Creates a new {dfanalytics-job}.
 The API accepts a +{request}+ object as a request and returns a +{response}+.
 
 [id="{upid}-{api}-request"]
-==== Put {dfanalytics-jobs} request
+==== Request
 
 A +{request}+ requires the following argument:
 

docs/java-rest/high-level/ml/put-datafeed.asciidoc

@@ -5,13 +5,13 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put datafeeds API
+=== Create datafeeds API
 
 Creates a new {ml} datafeed in the cluster. The API accepts a +{request}+ object
 as a request and returns a +{response}+.
 
 [id="{upid}-{api}-request"]
-==== Put datafeeds request
+==== Request
 
 A +{request}+ requires the following argument:
 

docs/java-rest/high-level/ml/put-filter.asciidoc

@@ -5,13 +5,13 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put filters API
+=== Create filters API
 
 Creates a new {ml} filter in the cluster. The API accepts a +{request}+ object
 as a request and returns a +{response}+.
 
 [id="{upid}-{api}-request"]
-==== Put filters request
+==== Request
 
 A +{request}+ requires the following argument:
 

docs/java-rest/high-level/ml/put-job.asciidoc

@@ -5,13 +5,13 @@
 --
 [role="xpack"]
 [id="{upid}-{api}"]
-=== Put {anomaly-jobs} API
+=== Create {anomaly-jobs} API
 
 Creates a new {anomaly-job} in the cluster. The API accepts a +{request}+ object
 as a request and returns a +{response}+.
 
 [id="{upid}-{api}-request"]
-==== Put {anomaly-jobs} request
+==== Request
 
 A +{request}+ requires the following argument: