diff --git a/CURATORS.md b/CURATORS.md
index d2fad636..8fbafd60 100644
--- a/CURATORS.md
+++ b/CURATORS.md
@@ -21,10 +21,12 @@ process works:
 
 ## Pull requests
 
-The typical story on pull requests is: If Travis accepts it, packdeps
-says the package is up to date, and the author only added packages
-under his/her own name, merge it.  If the build later fails (see
-below), then block the package until it's fixed.
+The typical story on pull requests is: If Travis accepts it and the
+author only added packages under his/her own name, merge it.  If the
+build later fails (see below), then block the package until it's
+fixed.
+
+Optionally we can check if packdeps says the package is up to date.
 
 ## Fixing bounds issues
 
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index 8c8ca954..a47eb400 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -3,7 +3,7 @@ This project is built around the concept of maintainers taking responsibility fo
 The idea behind Stackage is that, if all packages work with the newest versions of dependencies, we avoid dependency hell. Specifically, we aim for:
 
 * All packages are buildable and testable from Hackage. We recommend [the Stack Travis script](http://docs.haskellstack.org/en/stable/GUIDE.html#travis-with-caching), which ensures a package is not accidentally incomplete.
-* All packages are compatible with the newest versions of all dependencies (You can verify this by checking http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
+* All packages are compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
 * All packages in a snapshot are compatible with the versions of libraries that ship with the GHC used in the snapshot ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
 
 ## Adding a package
diff --git a/README.md b/README.md
index d2bdeb68..9ad3259a 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ We welcome all packages, provided:
 
 * The package author/maintainer agrees to the [maintainers agreement](https://github.com/fpco/stackage/blob/master/MAINTAINERS.md).
 * The package is buildable and testable from Hackage. We recommend [the Stack Travis script](http://docs.haskellstack.org/en/stable/GUIDE.html#travis-with-caching), which ensures a package is not accidentally incomplete.
-* The package is compatible with the newest versions of all dependencies (You can verify this by checking http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
+* The package is compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
 * The package is compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
 
 Full details on how to add a package can be found in the [maintainers agreement](https://github.com/fpco/stackage/blob/master/MAINTAINERS.md#adding-a-package).