diff --git a/.gitignore b/.gitignore
index 03cd627777aa..a059460b900b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -6,6 +6,7 @@
 cmd/clusterctl/clusterctl
 bin
 hack/tools/bin
+vars.sh
 
 # Test binary, build with `go test -c`
 *.test
diff --git a/docs/release/release-team.md b/docs/release/release-team.md
index 76480ea095ee..b7b4543d1093 100644
--- a/docs/release/release-team.md
+++ b/docs/release/release-team.md
@@ -103,8 +103,8 @@ Before you volunteer to be part of a CAPI release team, please make certain that
 
 ## Suggestions for Team Leads
 
-  * In the first week of the release cycle, organize an onboarding session with shadows of your team (i.e CI Lead with CI team shadows) to go over the general responsibilities and expectations.
-  * Clearly communicate with the team shadows you are responsible for, that the majority of the work during the release cycle will be a collaborative effort.
+  * In the first week of the release cycle, organize an onboarding session with members of your team (i.e CI Lead with CI team members) to go over the general responsibilities and expectations.
+  * Clearly communicate with the team members you are responsible for, that the majority of the work during the release cycle will be a collaborative effort.
   * Establish an ownership rotation policy in consultation with respective team members.
   * Provide opportunities for team members to take the lead in cutting a release within the cycle, based on feasibility.
   * Define backup ownership and tasks for team members, such as: