Merge pull request #2874 from sunlintong/feature-2

small mistakes

Author: k8s-ci-robot

exec-healthz/README.md

@@ -4,7 +4,7 @@ The exec healthz server is a sidecar container meant to serve as a liveness-exec
 
 ## How to release:
 
-The `exechealthz` Makefile supports multiple architecures, which means it may cross-compile and build an docker image easily.
+The `exechealthz` Makefile supports multiple architectures, which means it may cross-compile and build an docker image easily.
 If you are releasing a new version, please bump the `TAG` value in the `Makefile` before building the images.
 
 How to build and push all images:

service-loadbalancer/README.md

@@ -236,7 +236,7 @@ nginxsvc     app=nginx                                 app=nginx   10.0.79.131
                                                                                  443/TCP
 mysql        app=mysql                                 app=mysql   10.0.63.72    3306/TCP
 
-$ mysql -u root -ppassword --host 104.197.63.17 --port 3306 -e 'show databases;'
+$ mysql -u root -p password --host 104.197.63.17 --port 3306 -e 'show databases;'
 +--------------------+
 | Database           |
 +--------------------+

statefulsets/kafka/README.md

@@ -263,7 +263,7 @@ and a Pod Anti-Affinity rule.
 
 The Pod Anti-Affinity rule ensures that two Kafka Broker's will never be 
 launched on the same Node. This isn't strictly necessary, but it helps provide 
-stronger availability garauntees in the presence of Node failure, and it helps 
+stronger availability guarantees in the presence of Node failure, and it helps 
 alleviate [disk throughput](#disk) bottlenecks.
 The Pod Affinity rule attempts to collocate Kafka and ZooKeeper on the same 
 Nodes. You will likely have more Kafka brokers than ZooKeeper servers, but the