diff --git a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md
index d6c8527b..7cd44648 100644
--- a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md
+++ b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md
@@ -31,21 +31,21 @@ metadata:
 
 ## Step-02: Create LimitRange manifest
 - Instead of specifying `resources like cpu and memory` in every container spec of a pod defintion, we can provide the default CPU & Memory for all containers in a namespace using `LimitRange`
-```yaml
+```yaml 
 apiVersion: v1
-kind: ResourceQuota
+kind: LimitRange
 metadata:
-  name: ns-resource-quota
+  name: default-cpu-mem-limit-range
   namespace: dev3
 spec:
   limits:
     - default:
+        cpu: "500m"  # If not specified default limit is 0.5 vCPU per container     
         memory: "512Mi" # If not specified the Container's memory limit is set to 512Mi, which is the default memory limit for the namespace.
-        cpu: "500m"  # If not specified default limit is 1 vCPU per container 
       defaultRequest:
+        cpu: "300m" # If not specified default it will take from whatever specified in limits.default.cpu      
         memory: "256Mi" # If not specified default it will take from whatever specified in limits.default.memory
-        cpu: "300m" # If not specified default it will take from whatever specified in limits.default.cpu
-      type: Container                        
+      type: Container                     
 ```
 
 ## Step-03: Update all k8s manifest with namespace