centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Docs: Typo fix (#3210)

Browse source 
# 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)
This commit is contained in:
Isabel 2023-11-10 15:40:38 -05:00 • committed by GitHub
parent 6fe741b516
commit c9846130f4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/sources/escalation-chains-and-routes/_index.md
View file

@ -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.