From f9ab6975ba42abc403f13e9bcc45a7ce6acda9f6 Mon Sep 17 00:00:00 2001 From: Nitesh Koushik S <39699046+NiteshKoushik@users.noreply.github.com> Date: Fri, 25 Sep 2020 19:52:43 +0530 Subject: [PATCH] Document Update (#27806) * Document Update Capitalizing the words * Document Update Changes made as per the suggestion --- docs/sources/alerting/notifications.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/alerting/notifications.md b/docs/sources/alerting/notifications.md index 22783dcd2a5..bc0270bed9c 100644 --- a/docs/sources/alerting/notifications.md +++ b/docs/sources/alerting/notifications.md @@ -132,7 +132,7 @@ This might break custom event rules in your PagerDuty rules if you rely on the f Move any existing rules using `custom_details.myMetric` to `custom_details.queries.myMetric`. This behavior will become the default in a future version of Grafana. -> Using `dedup_key` tag will override grafana generated `dedup_key` with a custom key. +> Using `dedup_key` tag will override Grafana generated `dedup_key` with a custom key. ### Webhook The webhook notification is a simple way to send information about a state change over HTTP to a custom endpoint. @@ -183,9 +183,9 @@ In DingTalk PC Client: 5. In "Add Robot" panel, input a nickname for the robot and select a "message group" which the robot will join in. click "next". -6. There will be a Webhook URL in the panel, looks like this: https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxx. Copy this URL to the grafana Dingtalk setting page and then click "finish". +6. There will be a Webhook URL in the panel, looks like this: https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxx. Copy this URL to the Grafana DingTalk setting page and then click "finish". -Dingtalk supports the following "message type": `text`, `link` and `markdown`. Only the `link` message type is supported. +DingTalk supports the following "message type": `text`, `link` and `markdown`. Only the `link` message type is supported. ### Kafka