From 4cde87dc2c8c7b486fd8564d1d2a1611e8ebfd53 Mon Sep 17 00:00:00 2001
From: abregman <abregman@redhat.com>
Date: Mon, 27 Sep 2021 00:34:59 +0300
Subject: [PATCH] Update

---
 README.md                                                | 6 ++++++
 exercises/kubernetes/solutions/replicaset_03_solution.md | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f165483..29a8a75 100644
--- a/README.md
+++ b/README.md
@@ -7278,6 +7278,12 @@ The pod is automatically assigned with the default service account (in the names
 `kubectl get serviceaccounts`
 </b></details>
 
+<details>
+<summary>Explain "Security Context"</summary><br><b>
+
+[kubernetes.io](https://kubernetes.io/docs/tasks/configure-pod-container/security-context): "A security context defines privilege and access control settings for a Pod or Container."
+</b></details>
+
 #### Kubernetes - Patterns
 
 <details>
diff --git a/exercises/kubernetes/solutions/replicaset_03_solution.md b/exercises/kubernetes/solutions/replicaset_03_solution.md
index 461936b..0a21860 100644
--- a/exercises/kubernetes/solutions/replicaset_03_solution.md
+++ b/exercises/kubernetes/solutions/replicaset_03_solution.md
@@ -51,7 +51,7 @@ kubectl label pod <POD_NAME> type-
 5. List the Pods running. Are there more Pods running after removing the label? Why?
 
 ```
-Yes, there is an additional Pod running because once the label, used as a matching selector, was removed, the Pod became independant meaning, it's not controlled by the ReplicaSet anymore and the ReplicaSet was missing replicas based on its definition so, it created a new Pod.
+Yes, there is an additional Pod running because once the label (used as a matching selector) was removed, the Pod became independant meaning, it's not controlled by the ReplicaSet anymore and the ReplicaSet was missing replicas based on its definition so, it created a new Pod.
 ```
 
 6. Verify the ReplicaSet indeed created a new Pod