From 8fb4c250a0757ae243698f45cadea965a7d365d9 Mon Sep 17 00:00:00 2001 From: ashwinkumar12345 Date: Mon, 8 Nov 2021 14:08:34 -0800 Subject: [PATCH] minor changes --- _monitoring-plugins/ad/api.md | 2 +- _monitoring-plugins/ad/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_monitoring-plugins/ad/api.md b/_monitoring-plugins/ad/api.md index 4f6fb3e3..08668404 100644 --- a/_monitoring-plugins/ad/api.md +++ b/_monitoring-plugins/ad/api.md @@ -340,7 +340,7 @@ Returns whether the detector configuration has any issues that might prevent Ope You can use the validate API to identify issues in your detector configuration before creating the detector. -The request body consists of the detector configuration and follows the same format as the request body of the [create detector API]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api#create-anomaly-detector). You can pass an additional detector parameter to validate a specific detector. +The request body consists of the detector configuration and follows the same format as the request body of the [create detector API]({{site.url}}{{site.baseurl}}/monitoring-plugins/ad/api#create-anomaly-detector). #### Request diff --git a/_monitoring-plugins/ad/index.md b/_monitoring-plugins/ad/index.md index afc6d0e7..bd219106 100644 --- a/_monitoring-plugins/ad/index.md +++ b/_monitoring-plugins/ad/index.md @@ -110,7 +110,7 @@ We recommend experimenting with historical analysis with different feature sets ## Step 4: Review and create -Review your detector settings and model configurations to make sure that they're valid and then proceed to select **Create detector**. +Review your detector settings and model configurations to make sure that they're valid and then select **Create detector**. ![Anomaly detection results]({{site.url}}{{site.baseurl}}/images/review_ad.png)