diff --git a/docs/2_installation.rst b/docs/2_installation.rst
index 9e5d3ef..ab18c21 100644
--- a/docs/2_installation.rst
+++ b/docs/2_installation.rst
@@ -85,6 +85,7 @@ Axes has the following warnings codes built in:
 - ``axes.W001`` for invalid ``CACHES`` configuration.
 - ``axes.W002`` for invalid ``MIDDLEWARE`` configuration.
 - ``axes.W003`` for invalid ``AUTHENTICATION_BACKENDS`` configuration.
+- ``axes.W004`` for deprecated use of ``AXES_*`` setting flags.
 
 
 .. note::
@@ -96,10 +97,10 @@ Axes has the following warnings codes built in:
 Disabling Axes components in tests
 ----------------------------------
 
-If you get errors when running tests or other configurations, try setting the ``AXES_ENABLED``
-flag to ``False`` in your project or test settings configuration file::
+If you get errors when running tests, try setting the
+``AXES_ENABLED`` flag to ``False`` in your test settings::
 
     AXES_ENABLED = False
 
-This disables the Axes middleware, authentication backend and signal handlers
-which might produce errors with exotic test configurations.
+This disables the Axes middleware, authentication backend and signal receivers,
+which might fix errors with incompatible test configurations.
diff --git a/docs/7_architecture.rst b/docs/7_architecture.rst
index a0f1d1a..d670c27 100644
--- a/docs/7_architecture.rst
+++ b/docs/7_architecture.rst
@@ -73,5 +73,5 @@ to log in users or otherwise take care of notifying Axes of authentication
 attempts and failures the same way Django does via authentication signals.
 
 The login flows can be customized and the Axes
-authentication backend, middleware, and handlers
+authentication backend, middleware, and signal receivers
 can easily be swapped to alternative implementations.
diff --git a/docs/images/flow.png b/docs/images/flow.png
index 087512c..e7a726d 100644
Binary files a/docs/images/flow.png and b/docs/images/flow.png differ