-

Author: javiereguiluz

security/password_migration.rst

@@ -9,16 +9,18 @@ hash algorithms. This means that if a better hash algorithm is supported on your
 system, the user's password should be *rehashed* using the newer algorithm and
 stored. That's possible with the ``migrate_from`` option:
 
-#. `Configure a new Encoder Using "migrate_from"`_
+#. `Configure a new Hasher Using "migrate_from"`_
 #. `Upgrade the Password`_
-#. Optionally, `Trigger Password Migration From a Custom Encoder`_
+#. Optionally, `Trigger Password Migration From a Custom Hasher`_
 
-Configure a new Encoder Using "migrate_from"
-----------------------------------------------
+.. _configure-a-new-encoder-using migrate_from:
+
+Configure a new Hasher Using "migrate_from"
+-------------------------------------------
 
 When a better hashing algorithm becomes available, you should keep the existing
-encoder(s), rename it, and then define the new one. Set the ``migrate_from`` option
-on the new encoder to point to the old, legacy encoder(s):
+hasher(s), rename it, and then define the new one. Set the ``migrate_from`` option
+on the new hasher to point to the old, legacy hasher(s):
 
 .. configuration-block::