diff --git a/topics/containers/write_containerfile_run_container.md b/topics/containers/write_containerfile_run_container.md
index 7b31a14..04d2942 100644
--- a/topics/containers/write_containerfile_run_container.md
+++ b/topics/containers/write_containerfile_run_container.md
@@ -2,7 +2,7 @@
 
 ## Objectives
 
-1. Create a Docker image:
+1. Create an image:
   * Use centos or ubuntu as the base image
   * Install apache web server
   * Deploy any web application you want
diff --git a/topics/devops/README.md b/topics/devops/README.md
index 0b27fd0..ef95e17 100644
--- a/topics/devops/README.md
+++ b/topics/devops/README.md
@@ -436,6 +436,12 @@ Read more [here](https://about.gitlab.com/topics/gitops)
 
 </b></details>
 
+<details>
+<summary>When a repository refereed to as "GitOps Repository" what does it means?</summary><br><b>
+
+A repository that doesn't holds the application source code, but the configuration, infra, ... files that required to test and deploy the application.
+</b></details>
+
 <details>
 <summary>What are some practical implementations or practices of GitOp?</summary><br><b>
 
@@ -448,7 +454,8 @@ Read more [here](https://about.gitlab.com/topics/gitops)
 
 One might say we need more details as to what these configuration and infra files look like exactly and how complex the application and its CI/CD pipeline(s), but in general, most of the time you will want to put configuration and infra related files in their own separate repository and not in the repository of the application for multiple reasons:
 
-* Every change submitted to the configuration, shouldn't trigger the CI/CD of the application, it should be testing out and applying the modified configuration
+* Every change submitted to the configuration, shouldn't trigger the CI/CD of the application, it should be testing out and applying the modified configuration, not the application itself
+* When you mix application code with conifguration and infra related files
 </b></details>
 
 #### SRE
diff --git a/topics/kubernetes/README.md b/topics/kubernetes/README.md
index 28454da..d05d51f 100644
--- a/topics/kubernetes/README.md
+++ b/topics/kubernetes/README.md
@@ -120,8 +120,8 @@ metadata, kind and apiVersion
 
 Kubectl is the Kubernetes command line tool that allows you to run commands against Kubernetes clusters. For example, you can use kubectl to deploy applications, inspect and manage cluster resources, and view logs.
 </b></details>
-<details>
 
+<details>
 <summary>What Kubernetes objects do you usually use when deploying applications in Kubernetes?</summary><br><b>
 
 * Deployment - creates the Pods () and watches them