diff --git a/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md b/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md
index 025277127d..1013800e44 100644
--- a/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md
+++ b/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md
@@ -172,7 +172,7 @@ resources:
 If your namespace has a memory {{< glossary_tooltip text="resource quota" term_id="resource-quota" >}}
 configured,
 it is helpful to have a default value in place for memory limit.
-Here are two of the restrictions that a resource quota imposes on a namespace:
+Here are three of the restrictions that a resource quota imposes on a namespace:
 
 * For every Pod that runs in the namespace, the Pod and each of its containers must have a memory limit.
   (If you specify a memory limit for every container in a Pod, Kubernetes can infer the Pod-level memory
diff --git a/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md b/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
index 82a501e5d4..e1effd8f05 100644
--- a/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
+++ b/content/en/docs/tasks/administer-cluster/reconfigure-kubelet.md
@@ -29,7 +29,7 @@ Please find documentation on this feature in [earlier versions of documentation]
 There is no recommended replacement for this feature that works generically
 across various Kubernetes distributions. If you are using managed Kubernetes
 version, please consult with the vendor hosting Kubernetes for the best
-practices for customizing your Kubernetes. If you are using KubeAdm, refer to
+practices for customizing your Kubernetes. If you are using `kubeadm`, refer to
 [Configuring each kubelet in your cluster using kubeadm](/docs/setup/production-environment/tools/kubeadm/kubelet-integration/).
 
 In order to migrate off the Dynamic Kubelet Configuration feature, the