- Improved spellcheck.yml to ignore code blocks and inline code

- Populated wordlist.txt, the file needs additional review of the words
added
- Corrected a few obvious spelling mistakes in the docs

spellcheck.yml

@@ -14,6 +14,8 @@ matrix:
     encoding: utf-8
   pipeline:
   - pyspelling.filters.markdown:
+      markdown_extensions:
+      - pymdownx.superfences
   - pyspelling.filters.html:
       comments: false
       ignores:

versioned_docs/version-0.3.0/release-notes/release-notes-for-kubeslice-oss-0.2.0.mdx

@@ -14,7 +14,7 @@ These release notes describe the new changes and enhancements in this version.
 Namespaces that are created to run application deployments can be onboarded on a slice to form a micro 
 network segment. Once a namespace is bound to a slice, all the pods that get scheduled in 
 the namespace would get connected to the slice. The configuration is part of the slice YAML file. 
-This feature onboards namespaces and not indivdiual applications.
+This feature onboards namespaces and not individual applications.
 
 ## Breaking Change for Onboarding Applications 
 With the onboarding namespaces feature, onboarding each application is no longer supported. 

versioned_docs/version-0.4.0/kubeslice-cli/getting-started.mdx

@@ -107,7 +107,7 @@ The following are the kubeslice-cli options.
 :::note
 The kubeslice-cli tool must have access to the clusters you want it to manage. To grant it access, set the KUBECONFIG environment variable to 
 a path to the kubeconfig file containing the necessary keys to access those clusters.
-To set the KUBECONFIG environment varible, use these commands:
+To set the KUBECONFIG environment variable, use these commands:
   - On Linux/macOS: `export KUBECONFIG=<path to kubeconfig file>`
   - On Windows: `$env:KUBECONFIG = "kubeslice/kubeconfig.yaml"`
 ::: 

versioned_docs/version-0.4.0/release-notes/release-notes-for-kubeslice-oss-0.2.0.mdx

@@ -14,7 +14,7 @@ These release notes describe the new changes and enhancements in this version.
 Namespaces that are created to run application deployments can be onboarded on a slice to form a micro 
 network segment. Once a namespace is bound to a slice, all the pods that get scheduled in 
 the namespace would get connected to the slice. The configuration is part of the slice YAML file. 
-This feature onboards namespaces and not indivdiual applications.
+This feature onboards namespaces and not individual applications.
 
 ## Breaking Change for Onboarding Applications 
 With the onboarding namespaces feature, onboarding each application is no longer supported. 

versioned_docs/version-0.5.0/kubeslice-cli/getting-started.mdx

@@ -135,7 +135,7 @@ The following are the kubeslice-cli options.
 :::note
 The kubeslice-cli tool must have access to the clusters you want it to manage. To grant it access, set the KUBECONFIG environment variable to 
 a path to the kubeconfig file containing the necessary keys to access those clusters.
-To set the KUBECONFIG environment varible, use these commands:
+To set the KUBECONFIG environment variable, use these commands:
   - On Linux/macOS: `export KUBECONFIG=<path to kubeconfig file>`
   - On Windows: `$env:KUBECONFIG = "kubeslice/kubeconfig.yaml"`
 ::: 

versioned_docs/version-0.5.0/release-notes/release-notes-for-kubeslice-oss-0.2.0.mdx

@@ -14,7 +14,7 @@ These release notes describe the new changes and enhancements in this version.
 Namespaces that are created to run application deployments can be onboarded on a slice to form a micro 
 network segment. Once a namespace is bound to a slice, all the pods that get scheduled in 
 the namespace would get connected to the slice. The configuration is part of the slice YAML file. 
-This feature onboards namespaces and not indivdiual applications.
+This feature onboards namespaces and not individual applications.
 
 ## Breaking Change for Onboarding Applications 
 With the onboarding namespaces feature, onboarding each application is no longer supported. 

versioned_docs/version-0.6.0/kubeslice-cli/getting-started.mdx

@@ -134,7 +134,7 @@ The following are the kubeslice-cli options.
 :::note
 The kubeslice-cli tool must have access to the clusters you want it to manage. To grant it access, set the KUBECONFIG environment variable 
 to a path to the kubeconfig file containing the necessary keys to access those clusters.
-To set the KUBECONFIG environment varible, use these commands:
+To set the KUBECONFIG environment variable, use these commands:
   - On Linux/macOS: `export KUBECONFIG=<path to kubeconfig file>`
   - On Windows: `$env:KUBECONFIG = "kubeslice/kubeconfig.yaml"`
 ::: 

versioned_docs/version-0.6.0/release-notes/release-notes-for-kubeslice-oss-0.2.0.mdx

@@ -14,7 +14,7 @@ These release notes describe the new changes and enhancements in this version.
 Namespaces that are created to run application deployments can be onboarded on a slice to form a micro 
 network segment. Once a namespace is bound to a slice, all the pods that get scheduled in 
 the namespace would get connected to the slice. The configuration is part of the slice YAML file. 
-This feature onboards namespaces and not indivdiual applications.
+This feature onboards namespaces and not individual applications.
 
 ## Breaking Change for Onboarding Applications 
 With the onboarding namespaces feature, onboarding each application is no longer supported. 

versioned_docs/version-0.7.0/kubeslice-cli/getting-started.mdx

@@ -134,7 +134,7 @@ The following are the kubeslice-cli options.
 :::note
 The kubeslice-cli tool must have access to the clusters you want it to manage. To grant it access, set the KUBECONFIG environment variable 
 to a path to the kubeconfig file containing the necessary keys to access those clusters.
-To set the KUBECONFIG environment varible, use these commands:
+To set the KUBECONFIG environment variable, use these commands:
   - On Linux/macOS: `export KUBECONFIG=<path to kubeconfig file>`
   - On Windows: `$env:KUBECONFIG = "kubeslice/kubeconfig.yaml"`
 ::: 

versioned_docs/version-1.0.0/reference/reference-worker-cluster-secrets-script.mdx

@@ -81,7 +81,7 @@ The following information is required to run the script.
 
 2. Open the terminal where you have `kubectl` on PATH and set the context to the cluster for which you want to create the config.
 
-### Retreive Network Interface
+### Retrieve Network Interface
 3. Get the name of the network interface on the gateway nodes that is the egress interface for external traffic.
 :::warning
 The below command does not work for OpenShift clusters.

versioned_docs/version-1.1.0/reference/reference-worker-cluster-secrets-script.mdx

@@ -81,7 +81,7 @@ The following information is required to run the script.
 
 2. Open the terminal where you have `kubectl` on PATH and set the context to the cluster for which you want to create the config.
 
-### Retreive Network Interface
+### Retrieve Network Interface
 3. Get the name of the network interface on the gateway nodes that is the egress interface for external traffic.
 :::warning
 The below command does not work for OpenShift clusters.