diff --git a/docs/release/release-team-onboarding.md b/docs/release/release-team-onboarding.md
index 2397a69998a6..e4a768a39649 100644
--- a/docs/release/release-team-onboarding.md
+++ b/docs/release/release-team-onboarding.md
@@ -44,7 +44,9 @@ Now, let's dive into the specific onboarding notes for each sub-team below.
 ### Comms Lead Shadows Team
 
 - Understand Release Process: 
-    - Familiarize yourself with project's release process and the [tool](https://github.com/kubernetes-sigs/cluster-api/tree/main/hack/tools/release) used for generating release notes.
+    - Get to know how project's release process works.
+    - Walk through the [release note generation process](../release/release-tasks.md#create-pr-for-release-notes) and try to generate notes by yourself. This is the most important process the comms team is in charge of.
+    - Familiarize yourself with the release notes tool [code](https://github.com/kubernetes-sigs/cluster-api/tree/main/hack/tools/release). You'll probably need to update this code during the release cycle to cover new cases or add new features.
 - Documentation familiarity:
     - Explore project's documentation and start learning how to update and maintain it.
 - Communication channels: