diff --git a/documentation/source/readme/Contribution Process.rst b/documentation/source/readme/Contribution Process.rst
index 0fa9c43f3c1ffe8d95c084f551f54d8cfd5f09c6..9e0f7e9f73c2e55be1b6f564bfef3aaf316c3252 100644
--- a/documentation/source/readme/Contribution Process.rst	
+++ b/documentation/source/readme/Contribution Process.rst	
@@ -202,7 +202,7 @@ Upstreaming Patches via e-mail
 When upstreaming work we have done to a project which uses an e-mail based workflow there might be some pitfalls along the way.
 Our attribution should be in place (namingly the use of the company e-mail address as git author and maybe the signed-off-by), but sending the patches via Outlook/Exchange is not possible as the server side is known to mangle the e-mail format and patches would no longer apply.
 
-As a solution we recommend subscribing your private e-mail address to the mailing list and using it for sending the patches.We assume here that you have done the git commit with your correct company e-mail address and git send-email is already configured to send out e-mails ([sendemail] section of .gitconfig).
+As a solution we recommend subscribing your private e-mail address to the mailing list and using it for sending the patches. We assume here that you have done the git commit with your correct company e-mail address and git send-email is already configured to send out e-mails ([sendemail] section of .gitconfig).
 
 To keep the correct attribution in place we need to set set the --from field to our private e-mail when executing git send-email