Clean spelling and ignore generated scripts (#11)

Signed-off-by: Josh Minor <[email protected]>

Signed-off-by: Josh Minor <[email protected]>

Author: jishminor

.gitignore

@@ -0,0 +1,4 @@
+.vscode
+scripts/*
+!scripts/k3s-cloud-start.sh
+!scripts/k3s-start.sh

README.md

@@ -39,7 +39,7 @@ In the case you wish to deploy the demo we assume you have done the following:
    ```bash
    helm install --namespace smarter --create-namespace smarter-edge chart
    ```
-- Use the helm chart on each of hte modules. Remember to use the namespace and the correct labels. The individual charts do not install on devices automatically, they require labels.
+- Use the helm chart on each of the modules. Remember to use the namespace and the correct labels. The individual charts do not install on devices automatically, they require labels.
 
 ## To setup your registered edge node from your development machine
 Plugin USB camera. You should be able to see the camera at `/dev/video0`.

charts/smarter-edge/README.md

@@ -1,7 +1,7 @@
 # smarter-edge
 
 This chart deploys all the edge components and infrastructure for SMARTER including
-cni, dns and smarter-device-manager and creates a single lable that installs a pod for each in a node, smarter-edge=enabled.
+cni, dns and smarter-device-manager and creates a single label that installs a pod for each in a node, smarter-edge=enabled.
 
 
 For more information on smarter go to https://getsmarter.io

k3s-cloud-master.md

@@ -47,7 +47,7 @@ The script will create another local script that can be used to restart k3s if n
 The files token.\<instance name\> and kube.\<instance name\>.config contains the credentials to be use to authenticate a node (token file) or kubectl (kube.config file).
 *NOTE*: Is is important K3S_VERSION on client matches the server otherwise things are likely not to work
 The k3s-start.sh downloads a compatible k3s executable (that can replace kubectl) with the server and also creates a kubectl-\<instance name\>.sh script that emulates a kubectl with the correct credentials.
-The file env-<instance name>.sh create an alias for kubectl and adds the KUBECONFIG enviroment variable. 
+The file env-\<instance name\>.sh create an alias for kubectl and adds the KUBECONFIG enviroment variable. 
 
 # Joining a k3s node
 To join an node which does not use our yocto build. Copy the kube_cloud_install-\<instance name\>.sh to the node and execute it. The script is already configured to connect to the server \<instance name\>.  

k3s-edge-master.md

@@ -51,7 +51,7 @@ The script will create another local script that can be used to restart k3s if n
 The files token.\<instance name\> and kube.\<instance name\>.config contains the credentials to be use to authenticate a node (token file) or kubectl (kube.config file).
 *NOTE*: Is is important K3S_VERSION on client matches the server otherwise things are likely not to work
 The k3s-start.sh downloads a compatible k3s executable (that can replace kubectl) with the server and also creates a kubectl-\<instance name\>.sh script that emulates a kubectl with the correct credentials.
-The file env-<instance name>.sh create an alias for kubectl and adds the KUBECONFIG enviroment variable. 
+The file env-\<instance name\>.sh create an alias for kubectl and adds the KUBECONFIG enviroment variable. 
 
 # Joining a non-yocto k3s node
 To join an node which does not use our yocto build. Copy the kube_edge_install-\<instance name\>.sh to the node and execute it. The script is already configured to connect to the server \<instance name\>.  

scripts/k3s-cloud-start.sh

@@ -3,7 +3,7 @@
 
 # Identification of the server, used for directories names and disambiguate tokens and KUBECONFIG files
 SERVERNAME=${SERVERNAME:-default_cloud_smarter}
-# Especific port to be used at the server
+# Specific port to be used at the server
 HOSTPORT=${HOSTPORT:-6443}
 # IP that the clients will be used to connect (If on the cloud it will probably be the external IP of the server)
 # HOSTIP
@@ -118,7 +118,7 @@ then
 		exit 1
 	fi
 fi
-echo "k3s_${SERVERNAME} is running, access thois instance using the credentials at this directory"
+echo "k3s_${SERVERNAME} is running, access this instance using the credentials at this directory"
 
 exit 0
 EOF
@@ -193,6 +193,6 @@ EOF
 	chmod u+x "${KUBECTL_CLOUD_INSTALL_FILE}"
 fi
 
-echo "an useful trick is to create an alias for shell like: alias kubectl='$(pwd)/${KUBECTL_FILE}', if that is your only k3s running"
+echo "A useful trick is to create an alias for shell like: alias kubectl='$(pwd)/${KUBECTL_FILE}', if that is your only k3s running"
 
 exit 0

scripts/k3s-start.sh

@@ -3,7 +3,7 @@
 
 # Identification of the server, used for directories names and disambiguate tokens and KUBECONFIG files
 SERVERNAME=${SERVERNAME:-default_smarter}
-# Especific port to be used at the server
+# Specific port to be used at the server
 HOSTPORT=${HOSTPORT:-6443}
 # IP that the clients will be used to connect (If on the cloud it will probably be the external IP of the server)
 # HOSTIP
@@ -121,7 +121,7 @@ then
 		exit 1
 	fi
 fi
-echo "k3s_${SERVERNAME} is running, access thois instance using the credentials at this directory"
+echo "k3s_${SERVERNAME} is running, access this instance using the credentials at this directory"
 
 exit 0
 EOF
@@ -202,6 +202,6 @@ EOF
 	chmod u+x "${KUBECTL_EDGE_INSTALL_FILE}"
 fi
 
-echo "an useful trick is to create an alias for shell like: alias kubectl='$(pwd)/${KUBECTL_FILE}', if that is your only k3s running"
+echo "A useful trick is to create an alias for shell like: alias kubectl='$(pwd)/${KUBECTL_FILE}', if that is your only k3s running"
 
 exit 0