From 6fd39a084793c5c51299d2b779463bb2d581d0e4 Mon Sep 17 00:00:00 2001
From: moabdelaziz <44748548+Mohamed-abdalazez@users.noreply.github.com>
Date: Thu, 25 Jan 2024 01:19:36 +0200
Subject: [PATCH] Update README.md

---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 52a369e..a281958 100644
--- a/README.md
+++ b/README.md
@@ -97,8 +97,11 @@
      
      <img alt="Namespaces and cgroups" src="assets/6.png" />
 - In the figure below, let say that the container starts with proc_1, which is ```RUN CONTAINER```, then opens proc_2, which is ```OS specification```, and each process will open the next one. Linux Kernal considers all of these processes as a single process. and using the ```namespaces``` technique to isolate all these processes from all operating system.
+  
 <img alt="container_architecture" src="assets/7.png" />
 
+> [!TIP]
+> Look here for more explanation on namespaces and cgroups: [cgroups&Namespaces;](https://github.com/SafrotTechUniverse/Insights.To.Different.Micro.Topics/tree/main/Linux/cgroups%26Namespaces%3B)
 <a name="desc5"></a>
 ### The technology that is provided to deal with this container concept.