diff --git a/handbook/community.md b/handbook/community.md
index 3dd96ce01a..12c8917458 100644
--- a/handbook/community.md
+++ b/handbook/community.md
@@ -116,9 +116,9 @@ resolution (close/merge) as soon as possible (may take longer than 1 business da
 3. Any Fleet team member may merge a community PR after reviewing it and addressing any necessary
    changes. Before merging, double-check that the CI is passing, documentation is updated, and
    changes file is created. Please use your best judgement.
-4. Thank and congratulate the contributor! Consider sharing with the team in the `#g-growth` channel
-   of Fleet Slack so that it can be publicized by social media. Folks who contribute to Fleet and
-   are recognized for their contributions often become great champions for the project.
+4. Once a PR has been approved and merged, thank and congratulate the contributor, then share with the team in the `#help-promote` channel of Fleet Slack to be publicized on social media. Folks who contribute to Fleet and are recognized for their contributions often become great champions for the project.
+
+Please refer to our [PRs from the community](https://docs.google.com/document/d/13r0vEhs9LOBdxWQWdZ8n5Ff9cyB3hQkTjI5OhcrHjVo/edit?usp=sharing) guide for more detailed information.
 
 #### What is acceptable?