diff --git a/README.md b/README.md
index e7e3643..4963a34 100644
--- a/README.md
+++ b/README.md
@@ -68,7 +68,7 @@ organizational, team, and individual deployment variants of each package.
 Let's create our own organizational variant of the upstream free5gc package,
 using the Web UI.
 
-...results in free5gc-operator package in the `catalog` repo...
+...results in free5gc-operator package in the `catalog` repository...
 
 ### Deploy the free5gc Operator
 We can use a `PackageDeployment` resource to create a multi-cluster deployment
diff --git a/ansible_kind/scripts/multiclusterkind/configure.sh b/ansible_kind/scripts/multiclusterkind/configure.sh
index 63ca219..9a3fdc7 100755
--- a/ansible_kind/scripts/multiclusterkind/configure.sh
+++ b/ansible_kind/scripts/multiclusterkind/configure.sh
@@ -55,7 +55,8 @@ function _get_pkg {
 
 function _install_configsync {
     local kubeconfig="$1"
-    local cluster=$(basename "$kubeconfig" ".config")
+    local cluster
+    cluster=$(basename "$kubeconfig" ".config")
     local path="$base_path/$cluster"
     _get_pkg "$cluster" https://github.com/nephio-project/nephio-packages.git/nephio-configsync
 
diff --git a/demo-setup.md b/demo-setup.md
index fdb7769..4992091 100644
--- a/demo-setup.md
+++ b/demo-setup.md
@@ -29,11 +29,11 @@ repositories separately.
   `./scripts/repos.sh create $PARTICIPANT`
 
 
-# Automation TODO
+## Automation TODO
 
 * The `repos.sh` script and GitHub token are available on the VM; we could run
 `./repos.sh create $(hostname)` to automatically create the repositories. If we
-do this, the script may fail due to repos already existing, or due to GitHub
+do this, the script may fail due to repostories already existing, or due to GitHub
 rate limits. So, we need to be sure it failing does not abort the rest of setup.
 We also need to be prepared to run the script again from the workshop VM to
-provision any repos that failed to be created.
+provision any repositories that failed to be created.