diff --git a/docs/de/llm-prompt.md b/docs/de/llm-prompt.md
index 156976b91..cfe17db98 100644
--- a/docs/de/llm-prompt.md
+++ b/docs/de/llm-prompt.md
@@ -28,7 +28,7 @@ Source (English) – These are three code snippets:
 `"me"`
 `"items"`
 
-Result (German) – You change nothing:
+Result (German) – you change nothing:
 
 `"word"`
 `"me"`
diff --git a/docs/en/docs/deployment/docker.md b/docs/en/docs/deployment/docker.md
index a1de2dc46..6b71f7360 100644
--- a/docs/en/docs/deployment/docker.md
+++ b/docs/en/docs/deployment/docker.md
@@ -490,7 +490,7 @@ And normally this **load balancer** would be able to handle requests that go to
 
 In this type of scenario, you probably would want to have **a single (Uvicorn) process per container**, as you would already be handling replication at the cluster level.
 
-So, in this case, you **would not** want to have a multiple workers in the container, for example with the `--workers` command line option.You would want to have just a **single Uvicorn process** per container (but probably multiple containers).
+So, in this case, you **would not** want to have a multiple workers in the container, for example with the `--workers` command line option. You would want to have just a **single Uvicorn process** per container (but probably multiple containers).
 
 Having another process manager inside the container (as would be with multiple workers) would only add **unnecessary complexity** that you are most probably already taking care of with your cluster system.
 
diff --git a/scripts/translate.py b/scripts/translate.py
index d8494f88e..3e4b9458c 100644
--- a/scripts/translate.py
+++ b/scripts/translate.py
@@ -123,7 +123,7 @@ flowchart LR
     end
 ```
 
-Result (German) – You change nothing:
+Result (German) – you change nothing:
 
 ```mermaid
 flowchart LR