From c9846130f4c3af97edf153af316bc3db20ca91f7 Mon Sep 17 00:00:00 2001
From: Isabel <76437239+imatwawana@users.noreply.github.com>
Date: Fri, 10 Nov 2023 15:40:38 -0500
Subject: [PATCH] Docs: Typo fix (#3210)

# What this PR does
Fixes a typo
## Which issue(s) this PR fixes
N/A
## Checklist

- [ ] Unit, integration, and e2e (if applicable) tests updated
- [ ] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not
required)
---
 docs/sources/escalation-chains-and-routes/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/escalation-chains-and-routes/_index.md b/docs/sources/escalation-chains-and-routes/_index.md
index 036ea6d0..bf45192c 100644
--- a/docs/sources/escalation-chains-and-routes/_index.md
+++ b/docs/sources/escalation-chains-and-routes/_index.md
@@ -42,7 +42,7 @@ chain (e.g. acknowledge, resolve, silence etc), the escalation chain will contin
 execute.
 
 Users can create escalation chains to configure different type of escalation workflows.
-For example, you can create a chain that will notify on-call users with high priopity, and
+For example, you can create a chain that will notify on-call users with high priority, and
 another chain that will only send a message into a Slack channel.
 
 Escalation chains determine Who and When to notify. [How to notify][notify] is set by the user, based on their own preferences.