fix typos

Author: Mathieu Benoit

content/config-controller/create-config-controller.md

@@ -22,7 +22,7 @@ echo "export CONFIG_CONTROLLER_LOCATION=us-east1" >> ~/acm-workshop-variables.sh
 source ~/acm-workshop-variables.sh
 ```
 {{% notice info %}}
-Just `us-east1` or `us-central1` are supported region for Config Controller for now.
+Just `us-east1` or `us-central1` are the supported regions for now for Config Controller.
 {{% /notice %}}
 
 ## Create Config Controller's GCP project

content/config-controller/set-up-config-controller-git-repo.md

@@ -80,8 +80,8 @@ ssh-keygen -t rsa -b 4096 \
     -N '' \
     -f ./tmp/github-org-repo
 kubectl create secret generic git-creds \
-    --namespace=config-management-system \
-    --from-file=ssh=./tmp/github-org-repo
+    -n config-management-system \
+    --from-file ssh=./tmp/github-org-repo
 gh repo deploy-key add ./tmp/github-org-repo.pub
 rm -r tmp
 ```
@@ -107,7 +107,7 @@ spec:
 EOF
 ```
 {{% notice tip %}}
-The GitHub repository is private in order to demonstrate how to allow read access to Config Sync when you use a restricted Git repository. 
+The GitHub repository is private in order to demonstrate how to allow read access to Config Sync when you use a private Git repository. 
 {{% /notice %}}
 
 Since you started this workshop, you just ran 6 `kubectl` commands. For your information, moving forward you won't run any other `kubectl` commands because the design and intent of this workshop is to only deploy any Kubernetes resources via GitOps with Config Sync. You will also use some handy `gcloud` commands when appropriate.