From 61b79f71ad550c399f4f82bc46ace90f433236ed Mon Sep 17 00:00:00 2001
From: Johnathan Martell <286711055+johnmtll@users.noreply.github.com>
Date: Tue, 25 Aug 2026 10:47:57 -0400
Subject: [PATCH 1/2] docs: update release guidelines

---
 etc/notes/releasing.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md
index dbfbfa0026..9ff44ca33e 100644
--- a/etc/notes/releasing.md
+++ b/etc/notes/releasing.md
@@ -80,6 +80,8 @@ The MongoDB driver can now generate a cup of joe.
     - Check the performance metrics to make sure there are no regressions.
 1. On slack notify `#node-driver-docs`, `#nodejs-devtools`, and `#mongoose` that we intend to publish a release.
     - You may skip this step if you are releasing a package other than the driver.
+1. Add the `Team Review` label to the release PR. This is a grace period before release that prompts other
+   engineers to contribute their review, and requires sign-off from another team member before merge.
 1. **If there are new or changed experimental features**, update `EXPERIMENTAL_FEATURES.md`
     - Add descriptions for any new `@experimental` features
     - Remove or update entries for features that are no longer experimental

From 63470d48a8123fc89669e7ee040763e9767b6d1e Mon Sep 17 00:00:00 2001
From: Johnathan Martell <286711055+johnmtll@users.noreply.github.com>
Date: Tue, 25 Aug 2026 10:57:36 -0400
Subject: [PATCH 2/2] docs: verbiage

---
 etc/notes/releasing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/etc/notes/releasing.md b/etc/notes/releasing.md
index 9ff44ca33e..d600660102 100644
--- a/etc/notes/releasing.md
+++ b/etc/notes/releasing.md
@@ -80,7 +80,7 @@ The MongoDB driver can now generate a cup of joe.
     - Check the performance metrics to make sure there are no regressions.
 1. On slack notify `#node-driver-docs`, `#nodejs-devtools`, and `#mongoose` that we intend to publish a release.
     - You may skip this step if you are releasing a package other than the driver.
-1. Add the `Team Review` label to the release PR. This is a grace period before release that prompts other
+1. Add the `Team Review` label to the release PR. This encourages a grace period before release that prompts other
    engineers to contribute their review, and requires sign-off from another team member before merge.
 1. **If there are new or changed experimental features**, update `EXPERIMENTAL_FEATURES.md`
     - Add descriptions for any new `@experimental` features