diff --git a/15-Kubernetes-Requests-Limits/README.md b/15-Kubernetes-Requests-Limits/README.md
index fc632518..235dc136 100644
--- a/15-Kubernetes-Requests-Limits/README.md
+++ b/15-Kubernetes-Requests-Limits/README.md
@@ -1,3 +1,7 @@
+---
+title: Azure AKS Kubernetes Requests & Limits
+description: Understand Kubernetes Resources Requests & Limits on Azure Kubernetes Service AKS Cluster
+---
 # Kubernetes - Requests and Limits
 
 ## Step-01: Introduction
@@ -6,6 +10,10 @@
 - When you specify a resource limit for a Container, the kubelet enforces those `limits` so that the running container is not allowed to use more of that resource than the limit you set. 
 -  The kubelet also reserves at least the `request` amount of that system resource specifically for that container to use.
 
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-resources-requests-limits-1.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-resources-requests-limits-1.png){:target="_blank"}  
+
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-resources-requests-limits-2.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-resources-requests-limits-2.png){:target="_blank"}  
+
 ## Pre-requisite Check (Optional)
 - We should already have our AKS Cluster UP and Running. 
 - We should have configured our AKS Cluster credentials in command line to execute `kubectl` commands
diff --git a/16-Kubernetes-Namespaces/16-01-Namespaces-Imperative/README.md b/16-Kubernetes-Namespaces/16-01-Namespaces-Imperative/README.md
index 7cd8978f..33b2933d 100644
--- a/16-Kubernetes-Namespaces/16-01-Namespaces-Imperative/README.md
+++ b/16-Kubernetes-Namespaces/16-01-Namespaces-Imperative/README.md
@@ -1,3 +1,7 @@
+---
+title: Azure AKS Kubernetes  Namespaces Introduction
+description: Understand Kubernetes Namespace basics on Azure Kubernetes Service AKS Cluster
+---
 # Kubernetes Namespaces - Imperative using kubectl
 
 ## Step-01: Introduction
@@ -6,6 +10,13 @@
 - We can use namespaces to create multiple environments like dev, staging and production etc
 - Kubernetes will always list the resources from `default namespace` unless we provide exclusively from which namespace we need information from.
 
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-1.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-1.png){:target="_blank"}  
+
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-2.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-2.png){:target="_blank"}  
+
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-3.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-3.png){:target="_blank"}  
+
+
 ## Step-02: Namespaces Generic - Deploy in Dev1 and Dev2
 ### Create Namespace
 ```
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 82d1ce6c..b7e7b2de 100644
--- a/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md
+++ b/16-Kubernetes-Namespaces/16-02-Namespaces-LimitRange-default/README.md
@@ -1,4 +1,12 @@
+---
+title: Azure AKS Kubernetes Namespaces Limit Range
+description: Understand Kubernetes Namespaces Limit Range Concept Azure Kubernetes Service 
+---
 # Kubernetes Namespaces - LimitRange - Declarative using YAML
+
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-limit-range.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-limit-range.png){:target="_blank"}  
+
+
 ## Step-01: Create Namespace manifest
 - **Important Note:** File name starts with `00-`  so that when creating k8s objects namespace will get created first so it don't throw an error.
 ```yaml
@@ -82,11 +90,6 @@ kubectl delete -f kube-manifests/
 ```
 
 
-
-
-
-
-
 ## References:
 - https://kubernetes.io/docs/tasks/administer-cluster/namespaces-walkthrough/
 - https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/
diff --git a/16-Kubernetes-Namespaces/16-03-Namespaces-ResourceQuota/README.md b/16-Kubernetes-Namespaces/16-03-Namespaces-ResourceQuota/README.md
index 16f34051..4662f2a8 100644
--- a/16-Kubernetes-Namespaces/16-03-Namespaces-ResourceQuota/README.md
+++ b/16-Kubernetes-Namespaces/16-03-Namespaces-ResourceQuota/README.md
@@ -1,5 +1,12 @@
+---
+title: Azure AKS Kubernetes Namespaces Resource Quota
+description: Understand Kubernetes Namespaces Resource Quota Concept Azure Kubernetes Service 
+---
+
 # Kubernetes Namespaces - ResourceQuota - Declarative using YAML
 
+[![Image](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-resource-quota.png "Azure Kubernetes Service - Masterclass")](https://stacksimplify.com/course-images/azure-kubernetes-service-namespaces-resource-quota.png){:target="_blank"}  
+
 ## Step-01: Create Namespace manifest
 - **Important Note:** File name starts with `00-`  so that when creating k8s objects namespace will get created first so it don't throw an error.
 ```yml