k8s: minor typos and style changes

Co-authored-by: Juan Manuel Perez <jperezflorez@newrelic.com>
newrelic · Feb 1, 2022 · 418f16c · 418f16c
1 parent b8a72ad
commit 418f16c
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/...netes-integration/advanced-configuration/configure-control-plane-monitoring.mdx b/...netes-integration/advanced-configuration/configure-control-plane-monitoring.mdx
@@ -19,7 +19,7 @@ redirects:
 
 We monitor and collect [metrics](http://docs.newrelic.com/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#metrics) from the following control plane components:
 
-* **ETCD**: leader information, resident memory size, number of OS threads, consensus proposals data, etc. For a list of supported metrics, see [ETCD data](/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#etcd-data).
+* **etcd**: leader information, resident memory size, number of OS threads, consensus proposals data, etc. For a list of supported metrics, see [ETCD data](/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#etcd-data).
 * **API server**: rate of `apiserver` requests, breakdown of `apiserver` requests by HTTP method and response code, etc. For the complete list of supported metrics, see [API server data](/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#api-server-data).
 * **Scheduler**: requested CPU/memory vs available on the node, tolerations to taints, any set affinity or anti-affinity, etc. For the complete list of supported metrics, see [Scheduler data](/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#scheduler-data).
 * **Controller manager**: resident memory size, number of OS threads created, goroutines currently existing, etc. For the complete list of supported metrics, see [Controller manager data](/docs/integrations/kubernetes-integration/understand-use-data/understand-use-data#controller-manager-data).
@@ -477,7 +477,7 @@ Follow these instructions to set up mutual TLS authentication for ETCD in [OpenS
 1. Export the ETCD client certificates from the cluster to an opaque secret. In a default managed OpenShift cluster, the secret is named `kube-etcd-client-certs` and it is stored in the `openshift-monitoring` namespace.
 
    ```shell
-   kubectl get secret/kube-etcd-client-certs -n openshift-monitoring -o yaml > etcd-secret.yaml
+   kubectl get secret kube-etcd-client-certs -n openshift-monitoring -o yaml > etcd-secret.yaml
    ```
 
 2. Open the secret file and change the keys:

diff --git a/...ixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx b/...ixie/kubernetes-integration/advanced-configuration/newrelic-metrics-adapter.mdx
@@ -136,7 +136,7 @@ Notice that a `clusterName` filter has been automatically added to the query to
 
     1. Enable verbose logging:
       ```shell
-      helm upgrade -n newerlic --reuse-values newrelic-bundle --set newrelic-k8s-metrics-adapter.verboseLog=true newrelic/nri-bundle
+      helm upgrade -n newrelic --reuse-values newrelic-bundle --set newrelic-k8s-metrics-adapter.verboseLog=true newrelic/nri-bundle
       ```
     2. Leave on verbose mode for a few minutes, or until enough activity has occurred.
     3. When you have the information you need, disable verbose logging: