diff --git a/docs/reference/pip_install.rst b/docs/reference/pip_install.rst
index 6f3ac11b1..e18dcc4b2 100644
--- a/docs/reference/pip_install.rst
+++ b/docs/reference/pip_install.rst
@@ -453,6 +453,7 @@ the project path.  This is one advantage over just using ``setup.py develop``,
 which creates the "egg-info" directly relative the current working directory.
 
 
+.. _`controlling-setup-requires`:
 
 Controlling setup_requires
 ++++++++++++++++++++++++++
diff --git a/docs/user_guide.rst b/docs/user_guide.rst
index a5cd19202..ead4b8b3d 100644
--- a/docs/user_guide.rst
+++ b/docs/user_guide.rst
@@ -535,7 +535,7 @@ From within a real python, where ``SomePackage`` *is* installed globally, and is
 Ensuring Repeatability
 **********************
 
-Three things are required to fully guarantee a repeatable installation using requirements files.
+Four things are required to fully guarantee a repeatable installation using requirements files.
 
 1. The requirements file was generated by ``pip freeze`` or you're sure it only
    contains requirements that specify a specific version.
@@ -544,7 +544,10 @@ Three things are required to fully guarantee a repeatable installation using req
    This guarantees that only what is explicitly listed in the requirements file is
    installed.
 
-3. The installation is performed against an index or find-links location that is
+3. None of the packages to be installed utilize the setup_requires keyword. See
+   :ref:`Controlling setup_requires<controlling-setup-requires>`.
+
+4. The installation is performed against an index or find-links location that is
    guaranteed to *not* allow archives to be changed and updated without a
    version increase.  Unfortunately, this is *not* true on PyPI. It is possible
    for the same pypi distribution to have a different hash over time. Project