minor fixes upon local reviewcloud-silencing-docs

2 files changed, 10 insertions, 9 deletions

diff --git a/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md b/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md
index 3dbba353f2..05220ad829 100644
--- a/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md
+++ b/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md
@@ -23,6 +23,7 @@ To manage your **personal alert notification silencing rule settings**, you will
 1. You will be presented with a table of the configured alert notification silencing rules for:
   * the space (if aren't an **observer**)
   * yourself
+  
   You will be able to:
    1. **Add a new** alert notification silencing rule configuration.
       - Choose if it applies to **All users** or **Myself** (All users is only available for **administrators** and **managers**)
diff --git a/docs/cloud/alerts-notifications/notifications.md b/docs/cloud/alerts-notifications/notifications.md
index a43c70095b..ad115d43f4 100644
--- a/docs/cloud/alerts-notifications/notifications.md
+++ b/docs/cloud/alerts-notifications/notifications.md
@@ -93,23 +93,23 @@ These are: PagerDuty, Slack, Opsgenie
 
 Netdata Cloud provides you a Silencing Rule engine which allows you to mute alert notifications. This muting action is specific to alert state transition notifications, it doesn't include node unreachable state transitions.
 
-The Silencing Rule engine is flexible and allows you to enter silence rules for the two main entities involved on alert notifications and can be set using different attributes. The main entities you can enter are **Nodes** and **Alerts** which can be used in combination or isolation to target specific needs - see some examples [here]((https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md#silencing-rules-examples).
+The Silencing Rule engine is flexible and allows you to enter silence rules for the two main entities involved on alert notifications and can be set using different attributes. The main entities you can enter are **Nodes** and **Alerts** which can be used in combination or isolation to target specific needs - see some examples [here](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md#silencing-rules-examples).
 
 ### Scope definition for Nodes
-* Space: silencing the space, selecting `All Rooms`, silences all alert state transitions from any node claimed to the space.
-* War Room: silencing a specific room will silence all alert state transitions from any node in that room. Please note if the node belongs to 
+* **Space:** silencing the space, selecting `All Rooms`, silences all alert state transitions from any node claimed to the space.
+* **War Room:** silencing a specific room will silence all alert state transitions from any node in that room. Please note if the node belongs to 
 another room which isn't silenced it can trigger alert notifications to the users with membership to that other room.
-* Node: silencing a specific node can be done for the entire space, selecting `All Rooms`, or for specific war room(s). The main difference is
+* **Node:** silencing a specific node can be done for the entire space, selecting `All Rooms`, or for specific war room(s). The main difference is
 if the node should be silenced for the entire space or just for specific rooms (when specific rooms are selected only users with membership to that room won't receive notifications).
 
 ### Scope definition for Alerts
-* Alert name: silencing a specific alert name silences all alert state transitions for that specific alert. 
-* Alert context: silencing a specific alert context will silence all alert state transitions for alerts targeting that chart context, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#alarm-line-on).
-* Alert role: silencing a specific alert role will silence all the alert state transitions for alerts that are configured to be specific role recipients, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#alarm-line-to).
+* **Alert name:** silencing a specific alert name silences all alert state transitions for that specific alert. 
+* **Alert context:** silencing a specific alert context will silence all alert state transitions for alerts targeting that chart context, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#alarm-line-on).
+* **Alert role:** silencing a specific alert role will silence all the alert state transitions for alerts that are configured to be specific role recipients, for more details check [alert configuration docs](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#alarm-line-to).
 
 Beside the above two main entities there are another two important settings that you can define on a silencing rule:
-* Who does the rule affect? All user in the space or just me
-* When does is to apply? Immediately or on a given schedule (when setting immediately you can set duration)
+* Who does the rule affect? **All user** in the space or **Myself**
+* When does is to apply? **Immediately** or on a **Schedule** (when setting immediately you can set duration)
 
 For further help on setting alert notification silencing rules go to [Manage Alert Notification Silencing Rules](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-alert-notification-silencing-rules.md).