From 9d9c40d27e2f43f5e815f6fa76d210292aa60b01 Mon Sep 17 00:00:00 2001 From: Edward Betts Date: Sat, 28 May 2022 15:20:01 +0200 Subject: [PATCH] Correct spelling mistakes --- ChangeLog | 2 +- docs/changelog.rst | 2 +- docs/usage.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index ae02704..c62da4a 100644 --- a/ChangeLog +++ b/ChangeLog @@ -114,7 +114,7 @@ x.x (yyyy-mm-dd) Refactor as generic invite app -- Removed the dependancy on django-allauth, this package is now a +- Removed the dependency on django-allauth, this package is now a generic invite app. [bee_keeper] 1.4 (2015-11-27) diff --git a/docs/changelog.rst b/docs/changelog.rst index 396204c..24cf092 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -95,7 +95,7 @@ Not available Refactor as generic invite app -- Removed the dependancy on django-allauth, this package is now a +- Removed the dependency on django-allauth, this package is now a generic invite app. [bee_keeper] 1.4 (2015-11-27) diff --git a/docs/usage.rst b/docs/usage.rst index 9d2e3a8..b555981 100644 --- a/docs/usage.rst +++ b/docs/usage.rst @@ -5,7 +5,7 @@ There are two primary ways to use `django-invitations` described below. Generic Invitation flow: -* Priviledged user invites prospective user by email (via either Django admin, form post, JSON post or programmatically) +* Privileged user invites prospective user by email (via either Django admin, form post, JSON post or programmatically) * User receives invitation email with confirmation link * User clicks link and is redirected to a preconfigured url (default is accounts/signup)