summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMarkus Holtermann <info@markusholtermann.eu>2016-02-23 10:24:38 +1100
committerMarkus Holtermann <info@markusholtermann.eu>2016-02-23 10:24:38 +1100
commitb14470c7b7ee73c328c9c60100165301e6c2e24b (patch)
tree361a67fdc350534d56e5254f9fe3c8f052ea4369 /docs
parent5a541e2e6cb01e254f20c302093a24d7dc9af8ce (diff)
Fixed spelling error
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/auth/passwords.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/auth/passwords.txt b/docs/topics/auth/passwords.txt
index b57c846085..17d47d8a0b 100644
--- a/docs/topics/auth/passwords.txt
+++ b/docs/topics/auth/passwords.txt
@@ -210,7 +210,7 @@ upgrade to happen when a user logs in (which may never happen if a user doesn't
return to your site). In this case, you can use a "wrapped" password hasher.
For this example, we'll migrate a collection of SHA1 hashes to use
-PDKDF2(SHA1(password)) and add the corresponding password hasher for checking
+PBKDF2(SHA1(password)) and add the corresponding password hasher for checking
if a user entered the correct password on login. We assume we're using the
built-in ``User`` model and that our project has an ``accounts`` app. You can
modify the pattern to work with any algorithm or with a custom user model.