Correct spelling mistakes

README.rst

@@ -158,7 +158,7 @@ CI/CD Workflow
 
 - Driven by `.gitlab-ci.yml`
 
-Stages 1 and 2 use sqlite databases; fixtures in the repo are loaded when the container starts but there is no persistent storage - *except* that stage 2 has some persistence of admin accounts. Stages 3 and 4 have (seperate) mysql backends which persist between deploys.
+Stages 1 and 2 use sqlite databases; fixtures in the repo are loaded when the container starts but there is no persistent storage - *except* that stage 2 has some persistence of admin accounts. Stages 3 and 4 have (separate) mysql backends which persist between deploys.
 
 Stages 2-4 use SSO for login; stage 1 has admin accounts defined in fixtures.
 

TODO

@@ -1,5 +1,5 @@
 # General
-- Turn the site_base template back into an actual base template, preferrably a navbar, an empty body and our default footer.
+- Turn the site_base template back into an actual base template, preferably a navbar, an empty body and our default footer.
 - Decide if we want to use the flatpages app at all, or just pull everything into static templates.
     * Pro flatpages:
         - Easy to add block with important information to pages without a deploy

dev_db.json

@@ -1977,7 +1977,7 @@
   "model": "auth.permission",
   "pk": 61,
   "fields": {
-    "name": "Can add Addtional speaker",
+    "name": "Can add Additional speaker",
     "content_type": 21,
     "codename": "add_additionalspeaker"
   }
@@ -1986,7 +1986,7 @@
   "model": "auth.permission",
   "pk": 62,
   "fields": {
-    "name": "Can change Addtional speaker",
+    "name": "Can change Additional speaker",
     "content_type": 21,
     "codename": "change_additionalspeaker"
   }
@@ -1995,7 +1995,7 @@
   "model": "auth.permission",
   "pk": 63,
   "fields": {
-    "name": "Can delete Addtional speaker",
+    "name": "Can delete Additional speaker",
     "content_type": 21,
     "codename": "delete_additionalspeaker"
   }

docs/schedule.rst

@@ -50,7 +50,7 @@ Sample CSV data is included below::
    need to be done manually.
 
 .. tip::
-   Sessions such as the ``plenary`` and ``break`` which need to be exlusive will need to be flagged this way in the admin (``/admin/symposion_schedule/slot/``)
+   Sessions such as the ``plenary`` and ``break`` which need to be exclusive will need to be flagged this way in the admin (``/admin/symposion_schedule/slot/``)
 
 One can also **delete** an existing schedule via the delete action. This is
 irreversible (save for a database restore).