diff --git a/INSTALL.md b/INSTALL.md
index 84e5cd8d9aa89fc9ecdf9ea1010b2e5c396d5a71..316e9c85954130565aa5dc4cb2dbc1b5f2af1fda 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.