[DOCS] Adds note about data_counts values to Revert snapshot API docs…

…. (#66085) (#66090)

docs/reference/ml/anomaly-detection/apis/revert-snapshot.asciidoc

@@ -21,6 +21,7 @@ Reverts to a specific snapshot.
 `manage` cluster privileges to use this API. See
 <<security-privileges>> and {ml-docs-setup-privileges}.
 
+
 [[ml-revert-snapshot-desc]]
 == {api-description-title}
 
@@ -32,6 +33,10 @@ then it might be appropriate to reset the model state to a time before this
 event. For example, you might consider reverting to a saved snapshot after Black
 Friday or a critical system failure.
 
+NOTE: Reverting to a snapshot does not change the `data_counts` values of the 
+{anomaly-job}, these values are not reverted to the earlier state.
+
+
 [[ml-revert-snapshot-path-parms]]
 == {api-path-parms-title}
 
@@ -43,6 +48,7 @@ include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=job-id-anomaly-detection]
 (Required, string)
 include::{es-repo-dir}/ml/ml-shared.asciidoc[tag=snapshot-id]
 
+
 [[ml-revert-snapshot-request-body]]
 == {api-request-body-title}
 
@@ -55,6 +61,7 @@ NOTE: If you choose not to delete intervening results when reverting a snapshot,
 the job will not accept input data that is older than the current time.
 If you want to resend data, then delete the intervening results.
 
+
 [[ml-revert-snapshot-example]]
 == {api-examples-title}
 
@@ -67,6 +74,7 @@ POST _ml/anomaly_detectors/high_sum_total_sales/model_snapshots/1575402237/_reve
 --------------------------------------------------
 // TEST[skip:Kibana sample data]
 
+
 When the operation is complete, you receive the following results:
 [source,js]
 ----
@@ -106,4 +114,5 @@ When the operation is complete, you receive the following results:
 }
 ----
 
-For a description of these properties, see the <<ml-get-snapshot-results,get model snapshots API>>.
+For a description of these properties, see the 
+<<ml-get-snapshot-results,get model snapshots API>>.