Add note on auto-resolve for escalation policies

[Dalje-et]

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[Ayc0]

Suggested change

	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. *(This only applies if no one acknowledges; once acknowledged, escalation stops and the page won’t auto-resolve.)*
	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. *(This only applies if no one acknowledges; once acknowledged, escalation stops and the page won’t auto-escalate nor auto-resolve.)*

[joepeeples]

Italics feels unnecessary, since the parentheses already set off the statement and call attention to it. Also "or" is more conversational than "nor":

Suggested change

	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. *(This only applies if no one acknowledges; once acknowledged, escalation stops and the page won’t auto-resolve.)*
	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. (This only applies if no one acknowledges; once acknowledged, escalation stops and the page won't auto-escalate or auto-resolve.)

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/daljeet/oncall-autoresolve-unacknowledged-pages/service_management/on-call/escalation_policies

[joepeeples]

Approved with a minor edit suggestion, thanks!

[joepeeples]

Italics feels unnecessary, since the parentheses already set off the statement and call attention to it. Also "or" is more conversational than "nor":

Suggested change

	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. *(This only applies if no one acknowledges; once acknowledged, escalation stops and the page won’t auto-resolve.)*
	1. Select whether Datadog should automatically update the page status to **Resolved** after executing all rules and repeats. (This only applies if no one acknowledges; once acknowledged, escalation stops and the page won't auto-escalate or auto-resolve.)