From 62b87e15a0efac6be98c382a0429e9cb0d3c67a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjamin=20H=C3=A4ttasch?=
 <benjamin.haettasch@fachschaft.informatik.tu-darmstadt.de>
Date: Thu, 17 Jun 2021 14:40:32 +0000
Subject: [PATCH] Apply 2 suggestion(s) to 1 file(s)

---
 INSTALL.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/INSTALL.md b/INSTALL.md
index 84e5cd8d..316e9c85 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -208,7 +208,7 @@ On the first start, the database must be initialized (the Tables created and so
 When updating the project the database must be migrated.
 Both are done using the `migrate` command.
 
-This can be done manually by runningthe following command after the container has started:
+This can be done manually by running the following command after the container has started:
 `docker-compose exec -it akplanning-server ./manage.py migrate`
 
 It can also be done automatically on each container start by setting `AUTO_MIGRATE_DB` to the string `true`
@@ -227,7 +227,7 @@ Using the environment variables `DJANGO_SUPERUSER_{USERNAME,EMAIL,PASSWORD}`.
 The second way is to run the following command after the container has started:
 `docker-compose exec -it akplanning-server ./manage.py createsuperuser`
 
-### Extra djnago settings
+### Extra django settings
 For simple cases you can pass environment variables starting with `EXTRA_DJANGO_SETTING`.
 The content of such variables is written into python files, which are loaded as settings.
 
-- 
GitLab