diff --git a/docs/debug-attach_service.md b/docs/debug-attach_service.md
index a45a10ce6..51729e8d3 100644
--- a/docs/debug-attach_service.md
+++ b/docs/debug-attach_service.md
@@ -8,7 +8,7 @@ docker-compose exec $Service_Name /bin/bash
 
 ### Connecting to Services
 
-If you whant to connect to a service / application directly it is always a good idea to `source mailcow.conf` to get all relevant variables in your environment.
+If you whant to connect to a service / application directly it is always a good idea to `source mailcow.conf` to get all relevant variables into your environment.
 
 #### MySQL
 
diff --git a/docs/debug-logs.md b/docs/debug-logs.md
index d3ec41f0c..1926ce420 100644
--- a/docs/debug-logs.md
+++ b/docs/debug-logs.md
@@ -1,4 +1,4 @@
-To view the logs of all mailcow: dockerized related containers, you can use `docker-compose logs` inside your mailcow-dockerized folder that contains your `mailcow.conf`. This is usually a bit mutch but you could trim the output with `--tail=100` to the last 100 lines, or add a `-f` to follow the live output of all your services.
+To view the logs of all mailcow: dockerized related containers, you can use `docker-compose logs` inside your mailcow-dockerized folder that contains your `mailcow.conf`. This is usually a bit much, but you could trim the output with `--tail=100` to the last 100 lines per container, or add a `-f` to follow the live output of all your services.
 
 To view the logs of a specific service you can use `docker-compose logs [options] $Service_Name`
 
diff --git a/docs/debug.md b/docs/debug.md
index 5cfba7c4b..e17b3ab47 100644
--- a/docs/debug.md
+++ b/docs/debug.md
@@ -2,7 +2,7 @@ When a problem occurs, then always for a reason! What you want to do in such a c
 
 1. Read your logs; follow them to see what the reason for your problem is.
 2. Follow the leads given to you in your logfiles and start investigating.
-3. Restarting the troubled service or the whole stack to see if the problem persists.
+3. Restart the troubled service or the whole stack to see if the problem persists.
 4. Read the documentation of the troubled service and search it's bugtracker for your problem.
 5. Search our [issues](https://github.com/mailcow/mailcow-dockerized/issues) and [forum](https://forum.mailcow.email/) for topics related to your problem.
 6. [Create an issue](https://github.com/mailcow/mailcow-dockerized/issues) over at our GitHub repository if you think your problem might be a bug or a missing feature you badly need. But please make sure, that you include **all the logs** and a full description to your problem.
diff --git a/docs/u_e-mailcow_ui-bl_wl.md b/docs/u_e-mailcow_ui-bl_wl.md
index e78e7f53d..2c39b1112 100644
--- a/docs/u_e-mailcow_ui-bl_wl.md
+++ b/docs/u_e-mailcow_ui-bl_wl.md
@@ -4,4 +4,4 @@ To add or edit an entry to your **domain wide** filter table, login to your *mai
 
 
 !!! info
-    Be aware that a user [may override](u_e-mailcow_ui-spamalias.md) this setting by setting his own black- and whitelist!
+    Be aware that a user [may override](u_e-mailcow_ui-spamfilter.md) this setting by setting his own black- and whitelist!