Address review comments

Signed-off-by: Furkat Gofurov <[email protected]>

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:

vars.sh

@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+# Copyright 2019 The Kubernetes Authors.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+export GITHUB_TOKEN=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