diff --git a/README.md b/README.md
index 479f97d0..f4e49bd9 100644
--- a/README.md
+++ b/README.md
@@ -97,9 +97,9 @@ Once you have the podman remote socket you can run Dozzle on podman.
 podman run --volume=/run/user/1000/podman/podman.sock:/var/run/docker.sock -d -p 8080:8080 amir20/dozzle:latest
 ```
 
-Additionally you have to create a fake engine-id to prevent ```host not found``` errors. Podman doesn´t generate an engine-id like Docker by itself due to its daemonless architecture.
+Additionally you have to create a fake engine-id to prevent ```host not found``` errors. Podman doesn't generate an engine-id like Docker by itself due to its daemonless architecture.
 
-Under ```/var/lib/docker``` create a file named ```engine-id```, on a system with Podman you will have to creater the folder path as well. Inside the file place a UUID, for instance using ```uuidgen > engine-id```. After that the file should have an identifier that looks like this: ```b9f1d7fc-b459-4b6e-9f7a-e3d1cd2e14a9```.
+Under ```/var/lib/docker``` create a file named ```engine-id```. On a system with Podman you will have to create the folder path as well. Inside the file place the UUID, for instance using ```uuidgen > engine-id```. After that the file should have an identifier that looks like this: ```b9f1d7fc-b459-4b6e-9f7a-e3d1cd2e14a9```.
 
 For more details check [Podman Infos](docs/guide/podman.md) or the [FAQ](docs/guide/faq.md#i-am-seeing-host-not-found-error-in-the-logs-how-do-i-fix-it)
 
diff --git a/docs/guide/faq.md b/docs/guide/faq.md
index a5fc1826..61f1e21d 100644
--- a/docs/guide/faq.md
+++ b/docs/guide/faq.md
@@ -104,9 +104,9 @@ To resolve the error take following steps:
 
 The engine-id file should now have an UUID inside.
 
-An example setup for Ansible can be found in [Podman](podman.md)
+An example setup for Ansible can be found in [Podman Infos](podman.md)
 
-It might be neccessary to clean up your existing dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After that you can redeploy the Dozzle container and your logs should now show up.
+It might be necessary to clean up your existing Dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After that you can redeploy the Dozzle container and your logs should now show up.
 
 ## Why am I only seeing running containers? How do I see stopped containers?
 
diff --git a/docs/guide/podman.md b/docs/guide/podman.md
index 83245289..bbb95bbe 100644
--- a/docs/guide/podman.md
+++ b/docs/guide/podman.md
@@ -7,7 +7,7 @@ title: Podman
 This should be mainly a Podman only error: Using Podman doesn't create an engine-id like Docker.
 If you are using Docker check if the ```engine-id``` file exists with correct permissions in ```/var/lib/docker``` and has the UUID inside.
 
-It might be neccessary to clean up your existing dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After you created the engine-id you can redeploy the Dozzle container and your logs should now show up.
+It might be necessary to clean up your existing Dozzle deployment under Podman, stop the container and remove the associated data (container/volumes). After you created the engine-id you can redeploy the Dozzle container and your logs should now show up.
 
 ## Create UUID
 
@@ -15,7 +15,7 @@ Options for generating UUIDs
 
 ### uuidgen
 
-:warning: Adjust folder/file permissions if necessary. There isn't an critial info but depending on your existing setup you might want to take additional steps
+:warning: Adjust folder/file permissions if necessary. There isn't any critial info but depending on your existing setup you might want to take additional steps
 
 1. Install uuidgen
 2. Create the folders:  ```mkdir -p /var/lib/docker```
@@ -24,9 +24,9 @@ Options for generating UUIDs
 
 ### Ansible
 
-:warning: Depending on your setup you might have to take adjustments for file/folder permissions. The following task snippets would run as the become_user of the playbook running these tasks.
+:warning: Depending on your setup you might have to take adjustments for file/folder permissions. The following task snippets would run as the become_user/remote_user of the playbook running these tasks.
 
-If you wish to adjust the user have to set individual become/become_user parameters for the task.
+If you wish to adjust the user you have to set individual become/become_user parameters for these tasks.
 
 ```
 - name: Create /var/lib/docker