[DOCS] Changes level offset for anomaly detection APIs (#59920) (#59930)

Author: lcawl

docs/reference/ml/anomaly-detection/apis/close-job.asciidoc

@@ -1,7 +1,7 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-close-job]]
-=== Close {anomaly-jobs} API
+= Close {anomaly-jobs} API
 ++++
 <titleabbrev>Close jobs</titleabbrev>
 ++++
@@ -13,7 +13,7 @@ A closed job cannot receive data or perform analysis
 operations, but you can still explore and navigate results.
 
 [[ml-close-job-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `POST _ml/anomaly_detectors/<job_id>/_close` +
 
@@ -22,7 +22,7 @@ operations, but you can still explore and navigate results.
 `POST _ml/anomaly_detectors/_all/_close` +
 
 [[ml-close-job-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
@@ -31,7 +31,7 @@ operations, but you can still explore and navigate results.
 <<ml-stop-datafeed>>.
 
 [[ml-close-job-desc]]
-==== {api-description-title}
+== {api-description-title}
 
 You can close multiple {anomaly-jobs} in a single API request by using a group
 name, a comma-separated list of jobs, or a wildcard expression. You can close
@@ -57,14 +57,14 @@ situations where the job has already failed, or where you are not interested in
 results the job might have recently produced or might produce in the future.
 
 [[ml-close-job-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<job_id>`::
 (Required, string)
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-wildcard]
 
 [[ml-close-job-query-parms]]
-==== {api-query-parms-title}
+== {api-query-parms-title}
 
 `allow_no_jobs`::
 (Optional, boolean)
@@ -79,14 +79,14 @@ which has not responded to its initial close request.
 has closed. The default value is 30 minutes.
 
 [[ml-close-job-response-codes]]
-==== {api-response-codes-title}
+== {api-response-codes-title}
 
 `404` (Missing resources)::
   If `allow_no_jobs` is `false`, this code indicates that there are no 
   resources that match the request or only partial matches for the request.
 
 [[ml-close-job-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------

docs/reference/ml/anomaly-detection/apis/delete-calendar-event.asciidoc

@@ -1,34 +1,34 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-calendar-event]]
-=== Delete events from calendar API
+= Delete events from calendar API
 ++++
 <titleabbrev>Delete events from calendar</titleabbrev>
 ++++
 
 Deletes scheduled events from a calendar.
 
 [[ml-delete-calendar-event-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/calendars/<calendar_id>/events/<event_id>`
 
 [[ml-delete-calendar-event-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
 <<security-privileges>>.
 
 [[ml-delete-calendar-event-desc]]
-==== {api-description-title}
+== {api-description-title}
 
 This API removes individual events from a calendar. To remove all scheduled
 events and delete the calendar, see the
 <<ml-delete-calendar,delete calendar API>>.
 
 [[ml-delete-calendar-event-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<calendar_id>`::
 (Required, string)
@@ -39,7 +39,7 @@ include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
 identifier by using the <<ml-get-calendar-event,get calendar events API>>.
 
 [[ml-delete-calendar-event-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------

docs/reference/ml/anomaly-detection/apis/delete-calendar-job.asciidoc

@@ -1,27 +1,27 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-calendar-job]]
-=== Delete {anomaly-jobs} from calendar API
+= Delete {anomaly-jobs} from calendar API
 ++++
 <titleabbrev>Delete jobs from calendar</titleabbrev>
 ++++
 
 Deletes {anomaly-jobs} from a calendar.
 
 [[ml-delete-calendar-job-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/calendars/<calendar_id>/jobs/<job_id>`
 
 [[ml-delete-calendar-job-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
 <<security-privileges>>.
 
 [[ml-delete-calendar-job-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<calendar_id>`::
 (Required, string)
@@ -32,7 +32,7 @@ include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection-list]
 
 [[ml-delete-calendar-job-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------

docs/reference/ml/anomaly-detection/apis/delete-calendar.asciidoc

@@ -1,40 +1,40 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-calendar]]
-=== Delete calendar API
+= Delete calendar API
 ++++
 <titleabbrev>Delete calendar</titleabbrev>
 ++++
 
 Deletes a calendar.
 
 [[ml-delete-calendar-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/calendars/<calendar_id>`
 
 [[ml-delete-calendar-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
 <<security-privileges>>.
 
 [[ml-delete-calendar-desc]]
-==== {api-description-title}
+== {api-description-title}
 
 This API removes all scheduled events from the calendar then deletes the
 calendar.
 
 [[ml-delete-calendar-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<calendar_id>`::
 (Required, string)
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=calendar-id]
 
 [[ml-delete-calendar-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------

docs/reference/ml/anomaly-detection/apis/delete-datafeed.asciidoc

@@ -1,7 +1,7 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-datafeed]]
-=== Delete {dfeeds} API
+= Delete {dfeeds} API
 
 [subs="attributes"]
 ++++
@@ -11,12 +11,12 @@
 Deletes an existing {dfeed}.
 
 [[ml-delete-datafeed-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/datafeeds/<feed_id>`
 
 [[ml-delete-datafeed-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * Unless you use the `force` parameter, you must stop the {dfeed} before you
 can delete it.
@@ -25,21 +25,21 @@ can delete it.
 <<security-privileges>>.
 
 [[ml-delete-datafeed-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<feed_id>`::
 (Required, string)
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=datafeed-id]
 
 [[ml-delete-datafeed-query-parms]]
-==== {api-query-parms-title}
+== {api-query-parms-title}
 
 `force`::
   (Optional, boolean) Use to forcefully delete a started {dfeed}; this method is
   quicker than stopping and deleting the {dfeed}.
 
 [[ml-delete-datafeed-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------

docs/reference/ml/anomaly-detection/apis/delete-expired-data.asciidoc

@@ -1,34 +1,34 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-expired-data]]
-=== Delete expired data API
+= Delete expired data API
 ++++
 <titleabbrev>Delete expired data</titleabbrev>
 ++++
 
 Deletes expired and unused machine learning data.
 
 [[ml-delete-expired-data-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/_delete_expired_data`
 
 [[ml-delete-expired-data-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
 <<security-privileges>>.
 
 [[ml-delete-expired-data-desc]]
-==== {api-description-title}
+== {api-description-title}
 
 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.
 
 [[ml-delete-expired-data-request-body]]
-==== {api-request-body-title}
+== {api-request-body-title}
 
 `requests_per_second`::
 (Optional, float) The desired requests per second for the deletion processes.
@@ -39,7 +39,7 @@ The default behavior is no throttling.
 The default value is `8h` (8 hours).
 
 [[ml-delete-expired-data-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 The endpoint takes no arguments:
 

docs/reference/ml/anomaly-detection/apis/delete-filter.asciidoc

@@ -1,41 +1,41 @@
 [role="xpack"]
 [testenv="platinum"]
 [[ml-delete-filter]]
-=== Delete filter API
+= Delete filter API
 ++++
 <titleabbrev>Delete filter</titleabbrev>
 ++++
 
 Deletes a filter.
 
 [[ml-delete-filter-request]]
-==== {api-request-title}
+== {api-request-title}
 
 `DELETE _ml/filters/<filter_id>`
 
 [[ml-delete-filter-prereqs]]
-==== {api-prereq-title}
+== {api-prereq-title}
 
 * If the {es} {security-features} are enabled, you must have `manage_ml` or
 `manage` cluster privileges to use this API. See
 <<security-privileges>>.
 
 [[ml-delete-filter-desc]]
-==== {api-description-title}
+== {api-description-title}
 
 This API deletes a {ml-docs}/ml-rules.html[filter]. 
 If a {ml} job references the filter, you cannot delete the filter. You must 
 update or delete the job before you can delete the filter.
 
 [[ml-delete-filter-path-parms]]
-==== {api-path-parms-title}
+== {api-path-parms-title}
 
 `<filter_id>`::
 (Required, string)
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=filter-id]
 
 [[ml-delete-filter-example]]
-==== {api-examples-title}
+== {api-examples-title}
 
 [source,console]
 --------------------------------------------------