diff --git a/clr-k8s-examples/README.md b/clr-k8s-examples/README.md
index 335243d..e63fc74 100644
--- a/clr-k8s-examples/README.md
+++ b/clr-k8s-examples/README.md
@@ -1,7 +1,7 @@
 # How to setup the cluster
 
 ## Prerequisite
-This setup currently will work with k8s 1.14 & above. Any version of k8s before that might work, but is not guaranteed.
+This setup currently will work with Kubernetes 1.14 & above. Any version of Kubernetes before that might work, but is not guaranteed.
 
 ## Sample multi-node vagrant setup
 
@@ -26,7 +26,7 @@ cd clr-k8s-examples
 ## Setup the nodes in the cluster
 
 Run [`setup_system.sh`](setup_system.sh) once on each and every node (master and workers)
-to ensure k8s works on it.
+to ensure Kubernetes works on it.
 
 This script ensures the following
 
@@ -82,7 +82,7 @@ kubeadm join <master-ip>:<master-port> --token <token> --discovery-token-ca-cert
 Note: Remember to append `--cri-socket=/run/crio/crio.sock` to the join command generated by the master.
 
 On workers just use the join command that the master spits out. There nothing
-else you need to run on the worker. All the other k8s customizations are pushed
+else you need to run on the worker. All the other Kubernetes customizations are pushed
 in from master via the values setup in the `kubeadm.yaml` file.
 
 So if you want to customize the kubelet on the master or the workers (things
diff --git a/clr-k8s-examples/tests/e2e/run_e2e.sh b/clr-k8s-examples/tests/e2e/run_e2e.sh
index 1a51fbd..8fcbd76 100755
--- a/clr-k8s-examples/tests/e2e/run_e2e.sh
+++ b/clr-k8s-examples/tests/e2e/run_e2e.sh
@@ -39,10 +39,10 @@ cd $GOPATH/src/k8s.io
 if [ -d kubernetes ]
 then
     cd kubernetes
-    echo Checking status of existing k8s repo clone
+    echo Checking status of existing Kubernetes repo clone
     git status kubernetes
 else
-    echo Cloning upstream k8s repo
+    echo Cloning upstream Kubernetes repo
     git clone https://github.com/kubernetes/kubernetes.git
     cd kubernetes
 fi
diff --git a/metrics/README.md b/metrics/README.md
index 4a189bf..e934d05 100644
--- a/metrics/README.md
+++ b/metrics/README.md
@@ -46,8 +46,8 @@ The steps to execute a run of the scaling framework are listed below, which need
    INFO: Initialising
    command: bc: yes
    command: jq: yes
-   INFO: Checking k8s accessible
-   INFO: 1 k8s nodes in 'Ready' state found
+   INFO: Checking Kubernetes accessible
+   INFO: 1 Kubernetes nodes in 'Ready' state found
    starting kubectl proxy
    Starting to serve on 127.0.0.1:8090
    daemonset.apps/stats created
@@ -123,4 +123,4 @@ The steps to generate the result report are listed below:
    ├── scaling-3.png
    └── scaling-4.png
    ```
-More details about result reporting can be reviewed at [`report`](./report) directory.
\ No newline at end of file
+More details about result reporting can be reviewed at [`report`](./report) directory.
diff --git a/metrics/scaling/k8s_parallel.sh b/metrics/scaling/k8s_parallel.sh
index d5772c0..f768070 100755
--- a/metrics/scaling/k8s_parallel.sh
+++ b/metrics/scaling/k8s_parallel.sh
@@ -114,13 +114,13 @@ EOF
 
 init() {
 	info "Initialising"
-	info "Checking k8s accessible"
+	info "Checking Kubernetes accessible"
 	local worked=$( kubectl get nodes > /dev/null 2>&1 && echo $? || echo $? )
 	if [ "$worked" != 0 ]; then
 		die "kubectl failed to get nodes"
 	fi
 
-	info $(get_num_nodes) "k8s nodes found"
+	info $(get_num_nodes) "Kubernetes nodes found"
 	# We could check we have just the one node here - right now this is a single node
 	# test!! - because, our stats gathering is rudimentry, as k8s does not provide
 	# a nice way to do it (unless you want to parse 'descibe nodes')
diff --git a/metrics/scaling/k8s_scale.sh b/metrics/scaling/k8s_scale.sh
index 00eb20a..27f57e4 100755
--- a/metrics/scaling/k8s_scale.sh
+++ b/metrics/scaling/k8s_scale.sh
@@ -194,13 +194,13 @@ init() {
 	local cmds=("bc" "jq")
 	check_cmds "${cmds[@]}"
 
-	info "Checking k8s accessible"
+	info "Checking Kubernetes accessible"
 	local worked=$( kubectl get nodes > /dev/null 2>&1 && echo $? || echo $? )
 	if [ "$worked" != 0 ]; then
 		die "kubectl failed to get nodes"
 	fi
 
-	info $(get_num_nodes) "k8s nodes in 'Ready' state found"
+	info $(get_num_nodes) "Kubernetes nodes in 'Ready' state found"
 	# We could check we have just the one node here - right now this is a single node
 	# test!! - because, our stats gathering is rudimentry, as k8s does not provide
 	# a nice way to do it (unless you want to parse 'descibe nodes')
diff --git a/metrics/scaling/k8s_scale_nc.sh b/metrics/scaling/k8s_scale_nc.sh
index ae77ccb..6549525 100755
--- a/metrics/scaling/k8s_scale_nc.sh
+++ b/metrics/scaling/k8s_scale_nc.sh
@@ -220,13 +220,13 @@ init() {
 	local cmds=("bc" "jq")
 	check_cmds "${cmds[@]}"
 
-	info "Checking k8s accessible"
+	info "Checking Kubernetes accessible"
 	local worked=$( kubectl get nodes > /dev/null 2>&1 && echo $? || echo $? )
 	if [ "$worked" != 0 ]; then
 		die "kubectl failed to get nodes"
 	fi
 
-	info $(get_num_nodes) "k8s nodes in 'Ready' state found"
+	info $(get_num_nodes) "Kubernetes nodes in 'Ready' state found"
 	# We could check we have just the one node here - right now this is a single node
 	# test!! - because, our stats gathering is rudimentry, as k8s does not provide
 	# a nice way to do it (unless you want to parse 'descibe nodes')