Alerting docs: adds notification policy update (#88515)

* Alerting docs: adds notiification policy update

* Adds insert below or above

* ran prettier

* few grammar adds

* Changes to child policy terminology

* adds sibling terminology

* ran prettier

* updates with new terminology

* updates child policy info

* corrects typo

* ran prettier

* changes description for child policy

docs/sources/alerting/configure-notifications/create-notification-policy.md

@@ -31,17 +31,17 @@ refs:
 
 Notification policies determine how alerts are routed to contact points.
 
-Policies have a tree structure, where each policy can have one or more nested policies. Each policy, except for the default policy, can also match specific alert labels.
+Policies have a tree structure and each policy can have one or more child policies. Each policy, except for the default policy, can also match specific alert labels.
 
-Each alert is evaluated by the default policy and subsequently by each nested policy.
+Each alert is evaluated by the default policy and subsequently by each child policy.
 
-If the **Continue matching subsequent sibling nodes** option is enabled for a nested policy, then evaluation continues even after one or more matches. A parent policy’s configuration settings and contact point information govern the behavior of an alert that does not match any of the nested policies. A default policy governs any alert that does not match a nested policy.
+If the **Continue matching subsequent sibling nodes** option is enabled for a child policy, evaluation continues even after one or more matches. A parent policy’s configuration settings and contact point information govern the behavior of an alert that does not match any of the child policies. A default policy governs any alert that does not match a child policy.
 
 You can configure Grafana-managed notification policies as well as notification policies for an external Alertmanager data source.
 
 For more information on notification policies, refer to [fundamentals of Notification Policies](ref:notification-policies).
 
-## Edit default notification policy
+## Edit the default notification policy
 
 1. In the left-side menu, click **Alerts & IRM** and then **Alerting**.
 1. Click **Notification policies**.
@@ -55,38 +55,35 @@ For more information on notification policies, refer to [fundamentals of Notific
    - **Repeat interval** Minimum time interval for re-sending a notification if no new alerts were added to the group. Default is 4 hours.
 1. Click **Save** to save your changes.
 
-## Add new nested policy
+## Add a child policy
 
-To create a new notification policy, you need to follow its tree structure. New policies created on the trunk of the tree (default policy), are the tree branches. And, subsequently, each branch can bear their own child policies. This is why you always add a new **nested** policy under either the default policy, or under a already nested policy.
+You can create a child policy under a default policy or under an existing child policy.
+
+If you want to choose where to position your policy, see the section on **Add a sibling policy**.
 
 1. In the left-side menu, click **Alerts & IRM** and then **Alerting**.
 2. Click **Notification policies**.
 3. From the **Choose Alertmanager** dropdown, select an Alertmanager. By default, the **Grafana Alertmanager** is selected.
-4. To add a top level specific policy, go to the Specific routing section (either to the default policy, or to another existing policy in which you would like to add a new nested policy) and click **+New nested policy**.
+4. Click **+New child policy** from the default policy.
 5. In the Matching labels section, add one or more rules for matching alert labels.
-6. In the **Contact point** dropdown, select the contact point to send notification to if alert matches only this specific policy and not any of the nested policies.
+6. In the **Contact point** dropdown, select the contact point to send notification to if alert matches only this specific policy and not any of the child policies.
 7. Optionally, enable **Continue matching subsequent sibling nodes** to continue matching sibling policies even after the alert matched the current policy. When this option is enabled, you can get more than one notification for one alert.
 8. Optionally, enable **Override grouping** to specify the same grouping as the default policy. If this option is not enabled, the default policy grouping is used.
 9. Optionally, enable **Override general timings** to override the timing options configured in the group notification policy.
 10. Click **Save policy** to save your changes.
 
-## Add nested policy
+## Add a sibling policy
 
 1. In the left-side menu, click **Alerts & IRM** and then **Alerting**.
 1. Click **Notification policies**.
-1. Expand the specific policy you want to update.
-1. Click **+ Add nested policy**, then add the details using information in [Add new specific policy](#add-new-nested-policy).
-1. Click **Save policy** to save your changes.
+1. Find the child policy you want to create a sibling for.
+1. Click **Add new policy** -> **New sibling above** or **New sibling below**.
 
-## Edit notification policies
+   Notification policies are evaluated from top to bottom, so it is key to be able to choose which notification policy receives alerts first. Adding sibling notification policies instead of always inserting a child policy as well as being able to choose where to insert is key to managing where your alerts go.
 
-1. In the left-side menu, click **Alerts & IRM**, and then **Alerting**.
-1. Click **Notification policies**.
-1. Find the policy you want to edit, then click **...** -> **Edit**.
-1. Make any changes using instructions in [Add new specific policy](#add-new-nested-policy).
-1. Save your changes.
+1. Click **Save policy** to save your changes.
 
-## Searching for policies
+## Search for policies
 
 Grafana allows you to search within the tree of policies by the following:
 
@@ -97,15 +94,11 @@ To search by contact point simply select a contact point from the **Search by co
 
 To search by label matchers simply enter a valid matcher in the **Search by matchers** input field. Multiple matchers can be combined with a comma (`,`).
 
-An example of a valid matchers search input is:
-
-`severity=high, region=~EMEA|NASA`
-
-> All matched policies are **exact** matches. Regex-style or partial matching is currently not supported.
+It is important to note that all matched policies are **exact** matches. Grafana supports regular expressions for creating label matchers. It does not support regular expression or partial matching in the search for policies.
 
-## Caveat
+## Mute timings
 
-Mute timings are not inherited from a parent notification policy, they have to be configured in full on each level.
+Mute timings are not inherited from a parent notification policy. They have to be configured in full on each level.
 
 ## Example