Simplified_Deployment.md

@@ -6,7 +6,7 @@ To deploy the branches `main` and `dev` see [Deployment](deployment). After the
 
 You need a server with installed `docker` and the `docker compose` plugin. The server mus be reachable from the internet and must have a domain like `leafwriter.your-university.example.com` assigned and properly configured (DNS etc.). This server needs to have a web server such as Apache or Nginx installed and running to act as a reverse proxy. You must have the right to execute docker containers either directly or via `sudo` and you must be able to configure the web server.
 
-LEAF-Writer must be exposed to the internet only via an encrypted connection (`https`). It is the task of the reverse proxy ensure an encrypted connection, therefore you need a suitable certificate. It is enough if this certificate is valid for your chosen domain, e.g. `leafwriter.your-university.example.com`, no subdomain or wildcard capabilities are needed. You can use a `Let's encrypt` certificate, issued via `certbot`. 
+LEAF-Writer must be exposed to the internet only via an encrypted connection (`https`). It is the task of the reverse proxy to ensure an encrypted connection, therefore you need a suitable certificate. It is enough if this certificate is valid for your chosen domain, e.g. `leafwriter.your-university.example.com`, no subdomain or wildcard capabilities are needed. You can use a `Let's encrypt` certificate, issued via `certbot`. 
 The following deployment tutorial will assume that you use `certbot` to get a SSL-certificate. For this to work, you need to have `certbot` and the appropriate plugin for the webserver of your choice installed. However, as described, you can also use other certificates, you just have to properly configure them in conjunction with your reverse proxy.
 
 The machine you want to deploy LEAF-Writer on also needs to have `git` installed. The following guide will assume you are operating in a UNIX-like shell such as bash.