From 37f66cb9d8b02bd0d269adca25127f8e35caded1 Mon Sep 17 00:00:00 2001
From: runzhliu <runzhliu@tencent.com>
Date: Mon, 4 Jul 2022 16:47:26 +0800
Subject: [PATCH] improve the comments

---
 build/common.sh                                  | 2 +-
 cmd/kubeadm/app/phases/controlplane/manifests.go | 2 +-
 cmd/kubeadm/app/util/image/image.go              | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/build/common.sh b/build/common.sh
index 6edb7cc6ba6..f7a2fbf4e93 100755
--- a/build/common.sh
+++ b/build/common.sh
@@ -565,7 +565,7 @@ function kube::build::run_build_command_ex() {
 }
 
 function kube::build::rsync_probe {
-  # Wait unil rsync is up and running.
+  # Wait until rsync is up and running.
   local tries=20
   while (( tries > 0 )) ; do
     if rsync "rsync://k8s@${1}:${2}/" \
diff --git a/cmd/kubeadm/app/phases/controlplane/manifests.go b/cmd/kubeadm/app/phases/controlplane/manifests.go
index 8cd0bf577cd..73f4fa56270 100644
--- a/cmd/kubeadm/app/phases/controlplane/manifests.go
+++ b/cmd/kubeadm/app/phases/controlplane/manifests.go
@@ -47,7 +47,7 @@ func CreateInitStaticPodManifestFiles(manifestDir, patchesDir string, cfg *kubea
 }
 
 // GetStaticPodSpecs returns all staticPodSpecs actualized to the context of the current configuration
-// NB. this methods holds the information about how kubeadm creates static pod manifests.
+// NB. this method holds the information about how kubeadm creates static pod manifests.
 func GetStaticPodSpecs(cfg *kubeadmapi.ClusterConfiguration, endpoint *kubeadmapi.APIEndpoint) map[string]v1.Pod {
 	// Get the required hostpath mounts
 	mounts := getHostPathVolumesForTheControlPlane(cfg)
diff --git a/cmd/kubeadm/app/util/image/image.go b/cmd/kubeadm/app/util/image/image.go
index 0a3c2bb6cb7..224a3bc3cd5 100644
--- a/cmd/kubeadm/app/util/image/image.go
+++ b/cmd/kubeadm/app/util/image/image.go
@@ -21,7 +21,7 @@ import "regexp"
 var (
 	// tagMatcher is the regex used to match a tag.
 	// Basically we presume an image can be made of `[domain][:port][path]<name>[:tag][@sha256:digest]`
-	// We are obvously interested only in the tag, but for the purpose of properly matching it, we also match the digest
+	// We are obviously interested only in the tag, but for the purpose of properly matching it, we also match the digest
 	// (if present). All the parts before the tag we match in a single match everything (but not greedy) group.
 	// All matched sub-groups, except the tag one, get thrown away. Hence, in a result of FindStringSubmatch, if a tag
 	// matches, it's going to be the second returned element (after the full match).