diff --git a/.vscode/settings.json b/.vscode/settings.json
new file mode 100644
index 000000000..a48a5e9b3
--- /dev/null
+++ b/.vscode/settings.json
@@ -0,0 +1,5 @@
+{
+    "restructuredtext.languageServer.disabled": true,
+    "restructuredtext.preview.sphinx.disabled": true,
+    "restructuredtext.linter.disabled": true
+}
\ No newline at end of file
diff --git a/doc/source/security/kubernetes/security-install-kubectl-and-helm-clients-directly-on-a-host.rst b/doc/source/security/kubernetes/security-install-kubectl-and-helm-clients-directly-on-a-host.rst
index 39b266974..dac823ed2 100644
--- a/doc/source/security/kubernetes/security-install-kubectl-and-helm-clients-directly-on-a-host.rst
+++ b/doc/source/security/kubernetes/security-install-kubectl-and-helm-clients-directly-on-a-host.rst
@@ -87,8 +87,8 @@ configuration is required in order to use :command:`helm`.
             In order for your remote host to trust the certificate used by
             the |prod-long| K8S API, you must ensure that the
             ``k8s\_root\_ca\_cert`` specified at install time is a trusted
-            CA certificate by your host. Follow the instructions for adding
-            a trusted CA certificate for the operating system distribution
+            |CA| certificate by your host. Follow the instructions for adding
+            a trusted |CA| certificate for the operating system distribution
             of your particular host.
 
             If you did not specify a ``k8s\_root\_ca\_cert`` at install
@@ -109,7 +109,7 @@ configuration is required in order to use :command:`helm`.
             --user kubernetes-admin@mycluster --namespace=default
             % kubectl config use-context kubernetes-admin@mycluster
 
-        ``$TOKEN\_DATA`` is the token retrieved in step 1.
+        ``$TOKEN_DATA`` is the token retrieved in step 1.
 
     #.  Test remote :command:`kubectl` access.