diff --git a/docs/monitoring-other-namespaces.md b/docs/monitoring-other-namespaces.md
index 8327ed024b31b2da6afbcdf0ab0fb84738232404..51f21201b58f3d2353a6ef6fca78a9a3973a2a18 100644
--- a/docs/monitoring-other-namespaces.md
+++ b/docs/monitoring-other-namespaces.md
@@ -5,14 +5,14 @@ This guide will help you monitor applications in other Namespaces. By default th
 You have to give the list of the Namespaces that you want to be able to monitor.
 This is done in the variable `prometheus.roleSpecificNamespaces`. You usually set this in your `.jsonnet` file when building the manifests.
 
-Example to create the needed `Role` and `Rolebindig` for the Namespace `foo` : 
+Example to create the needed `Role` and `RoleBinding` for the Namespace `foo` : 
 ```
 local kp = (import 'kube-prometheus/kube-prometheus.libsonnet') + {
   _config+:: {
     namespace: 'monitoring',
 
     prometheus+:: {
-      namespaces: ["default", "kube-system","foo"],
+      namespaces: ["default", "kube-system", "foo"],
     },
   },
 };