diff --git a/docker-and-k8s-security/podman_vs_docker.md b/docker-and-k8s-security/podman_vs_docker.md
index 190ff5c..212da91 100644
--- a/docker-and-k8s-security/podman_vs_docker.md
+++ b/docker-and-k8s-security/podman_vs_docker.md
@@ -4,7 +4,7 @@
 - Podman has a daemon-less architecture which means it can run containers under the user starting the container. 
 - Docker has a client-server logic mediated by a daemon; Podman does not need the mediator.
 - Podman allows for non-root privileges for containers.
-- Rootless containers are considered safer than containers with root privileges
+- Rootless containers are considered safer than containers with root privileges
 
 ## Podman Rootless?
 
@@ -15,11 +15,11 @@
 - Without a daemon, Podman needs another tool to manage services and support running containers in the background. 
 - Systemd creates control units for existing containers or to generate new ones. 
 - Systemd can also be integrated with Podman allowing it to run containers with systemd enabled by default, without any modification.
-- By using systemd, vendors can install, run, and manage their applications as containers since most are now exclusively packaged and delivered this way.
+- By using systemd, vendors can install, run, and manage their applications as containers since most are now exclusively packaged and delivered this way.
 
 ## Building images
 - As a self-sufficient tool, Docker can build container images on its own. 
-- Podman requires the assistance of another tool called Buildah, which expresses its specialized nature: it is made for running but not building containers on its own.![image](https://user-images.githubusercontent.com/1690898/172636340-a0963aab-eb27-46d6-ab47-f00c0d9aa680.png)
+- Podman requires the assistance of another tool called Buildah, which expresses its specialized nature: it is made for running but not building containers on its own.