Docs: Add explanation for rotation layer

CHANGELOG.md

@@ -5,16 +5,19 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## v1.2.28 (2023-05-24)
+## Unreleased
 
 ### Changed
 
 - Phone provider refactoring [#1713](https://github.com/grafana/oncall/pull/1713)
 
+## v1.2.28 (2023-05-24)
+
 ### Fixed
 
 - Improve plugin authentication by @vadimkerr ([#1995](https://github.com/grafana/oncall/pull/1995))
 - Fix MultipleObjectsReturned error on webhook endpoints by @vadimkerr ([#1996](https://github.com/grafana/oncall/pull/1996))
+- Remove user defined time period from "you're going oncall" mobile push by @iskhakov ([#2001](https://github.com/grafana/oncall/pull/2001))
 
 ## v1.2.27 (2023-05-23)
 
@@ -29,7 +32,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 
 - Fix SQLite permission issue by @vadimkerr ([#1984](https://github.com/grafana/oncall/pull/1984))
-- Remove user defined time period from "you're going oncall" mobile push ([2001](https://github.com/grafana/oncall/pull/2001))
 
 ## v1.2.26 (2023-05-18)
 

docs/sources/escalation-policies/configure-routes/index.md → docs/sources/escalation-chains-and-routes/_index.md

@@ -1,22 +1,40 @@
 ---
 aliases:
-  - /docs/oncall/latest/escalation-policies/configure-routes/
-canonical: https://grafana.com/docs/oncall/latest/escalation-policies/configure-routes/
-keywords:
-  - Grafana Cloud
-  - Alerts
-  - Notifications
-  - on-call
-  - amixr
-  - oncall
-  - integrations
-title: Configure and manage routes
-weight: 300
+  - /docs/oncall/latest/escalation-chains-and-routes/
+canonical: https://grafana.com/docs/oncall/latest/escalation-chains-and-routes/
+title: Escalation Chains and Routes
+weight: 600
 ---
 
-# Configure and manage Routes
+# Escalation Chains and Routes
 
-Set up escalation chains and routes to configure escalation behavior for alert group notifications.
+Escalation chains and routes for Grafana OnCall
+
+Administrators can create escalation policies to automatically send alert group notifications to recipients.
+These policies define how, where, and when to send notifications.
+
+Escalation policies dictate how users and groups are notified when an alert notification is created. They can be very
+simple, or very complex. You can define as many escalation configurations for an integration as you need, and you can
+send notifications for certain alerts to a designated place when certain conditions are met, or not met.
+
+Escalation policies have three main parts:
+
+- User settings, where a user sets up their preferred or required notification method.
+- An **escalation chain**, which can have one or more steps that are followed in order when a notification is triggered.
+- A **route**, that allows administrators to manage notifications by flagging expressions in an alert payload.
+
+## Escalation chains
+
+An escalation chain can have many steps, or only one step. For example, steps can be configured to notify multiple users
+in some order, notify users that are scheduled for on-call shifts, ping groups in Slack, use outgoing webhooks to
+integrate with other services, such as JIRA, and do a number of other automated notification tasks.
+
+## Routes
+
+An escalation workflow can employ **routes** that administrators can configure to filter alerts by regular expressions
+(outdated) or Jinja2 templates
+in their payloads. Notifications for these alerts can be sent to individuals, or they can make use of a new
+or existing escalation chain.
 
 ## Configure escalation chains
 
@@ -59,14 +77,10 @@ specify using a Jinja template that matches content in the payload body of the f
 specify where to send the notification for each route.
 
 For example, you can send notifications for alerts with `{{ payload.severity == "critical" and payload.service ==
-"database" }}` in the payload to an escalation chain called `Bob_OnCall`. You can create a different route for alerts
+"database" }}` [(Check Jinja2 reference)]({{< relref "jinja2-templating" >}}) in the payload to an escalation chain
+called `Bob_OnCall`. You can create a different route for alerts
 with the payload `{{ "synthetic-monitoring-dev-" in payload.namespace }}` and select a escalation chain called
 `NotifySecurity`.
 
-Alternatively you can use regular expressions, e.g. `\"severity\": \"critical\"` or `\"namespace\" *:
-*\"synthetic-monitoring-dev-.*\"`
-
-You can set up escalation steps for each route in a chain.
-
 > **NOTE:** When you modify an escalation chain or a route, it will modify that escalation chain across
 > all integrations that use it.