[DOCS] Change allows to enables in ML docs (elastic/x-pack-elasticsearch#1230)

Original commit: elastic/x-pack-elasticsearch@a408fd59f6

docs/en/ml/getting-started.asciidoc

@@ -427,7 +427,7 @@ anomalousness of that value compared to previous hours.
 
 The bucket span has two purposes: it dictates over what time span to look for
 anomalous features in data, and also determines how quickly anomalies can be
-detected. Choosing a shorter bucket span allows anomalies to be detected more
+detected. Choosing a shorter bucket span enables anomalies to be detected more
 quickly. However, there is a risk of being too sensitive to natural variations
 or noise in the input data. Choosing too long a bucket span can mean that
 interesting anomalies are averaged away. There is also the possibility that the

docs/en/ml/ml-scenarios.asciidoc

@@ -49,7 +49,7 @@ It is said that 75 percent of troubleshooting time is spent mining data to try
 and identify the root cause of an incident. The {ml} features in {xpack}
 automatically analyze data and boil down the massive volume of information
 to the few metrics or log messages that have changed behavior.
-This allows the subject matter experts (SMEs) to focus on the subset of
+This enables the subject matter experts (SMEs) to focus on the subset of
 information that is relevant to an issue, which greatly reduces triage time.
 
 //In a major credit services provider, within a month of deployment, the company

docs/en/rest-api/ml/delete-datafeed.asciidoc

@@ -2,7 +2,7 @@
 [[ml-delete-datafeed]]
 ==== Delete Data Feeds
 
-The delete data feed API allows you to delete an existing data feed.
+The delete data feed API enables you to delete an existing data feed.
 
 
 ===== Request

docs/en/rest-api/ml/delete-job.asciidoc

@@ -2,7 +2,7 @@
 [[ml-delete-job]]
 ==== Delete Jobs
 
-The delete job API allows you to delete an existing anomaly detection job.
+The delete job API enables you to delete an existing anomaly detection job.
 
 
 ===== Request

docs/en/rest-api/ml/get-job-stats.asciidoc

@@ -2,7 +2,7 @@
 [[ml-get-job-stats]]
 ==== Get Job Statistics
 
-The get jobs API allows you to retrieve usage information for jobs.
+The get jobs API enables you to retrieve usage information for jobs.
 
 
 ===== Request

docs/en/rest-api/ml/post-data.asciidoc

@@ -2,7 +2,7 @@
 [[ml-post-data]]
 ==== Post Data to Jobs
 
-The post data API allows you to send data to an anomaly detection job for analysis.
+The post data API enables you to send data to an anomaly detection job for analysis.
 The job must have been opened prior to sending data.
 
 

docs/en/rest-api/ml/snapshotresource.asciidoc

@@ -11,7 +11,7 @@ behavior by updating the `model_snapshot_retention_days` for the job.
 When choosing a new value, consider the following:
 
 * Persistence enables resilience in the event of a system failure.
-* Persistence allows for snapshots to be reverted.
+* Persistence enables snapshots to be reverted.
 * The time taken to persist a job is proportional to the size of the model in memory.
 //* The smallest allowed value is 3600 (1 hour).
 ////

docs/en/rest-api/ml/start-datafeed.asciidoc

@@ -14,7 +14,7 @@ A data feed can be started and stopped multiple times throughout its lifecycle.
 NOTE: Before you can start a data feed, the job must be open. Otherwise, an error
 occurs.
 
-When you start a data feed, you can specify a start time.  This allows you to
+When you start a data feed, you can specify a start time.  This enables you to
 include a training period, providing you have this data available in {es}.
 If you want to analyze from the beginning of a dataset, you can specify any date
 earlier than that beginning date.

docs/en/rest-api/ml/update-job.asciidoc

@@ -2,7 +2,7 @@
 [[ml-update-job]]
 ==== Update Jobs
 
-The update job API allows you to update certain properties of a job.
+The update job API enables you to update certain properties of a job.
 
 ===== Request