Try to be as explicit as possible on the million different uses of 'validator'.

Closes #175.

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/faq.rst b/docs/faq.rst
index 4c1035f..7495cdb 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -16,10 +16,10 @@ It's perfectly valid (and perhaps even useful) to have a default that is not
 valid under the schema it lives in! So an instance modified by the default
 would pass validation the first time, but fail the second!
 
-Still, filling in defaults is a thing that is useful. :mod:`jsonschema` allows
-you to :doc:`define your own validators <creating>`, so you can easily create a
-:class:`IValidator` that does do default setting. Here's some code to get you
-started:
+Still, filling in defaults is a thing that is useful. :mod:`jsonschema`
+allows you to :doc:`define your own validator classes and callables
+<creating>`, so you can easily create a :class:`IValidator` that does do
+default setting. Here's some code to get you started:
 
     .. code-block:: python