From e31a307db32692d9ca191826216cf2c23ace3213 Mon Sep 17 00:00:00 2001 From: Edward Betts Date: Sun, 6 Aug 2023 09:46:41 +0100 Subject: [PATCH] Correct spelling mistakes --- README.rst | 2 +- TODO | 2 +- dev_db.json | 6 +++--- docs/schedule.rst | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.rst b/README.rst index 2404e22b..207a6224 100644 --- a/README.rst +++ b/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. diff --git a/TODO b/TODO index 99eba96b..021fe36d 100644 --- a/TODO +++ b/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 diff --git a/dev_db.json b/dev_db.json index dfd339cd..fd28e5f6 100644 --- a/dev_db.json +++ b/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" } diff --git a/docs/schedule.rst b/docs/schedule.rst index 17bbbde6..d83c9f24 100644 --- a/docs/schedule.rst +++ b/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).