Mention some more man pages in SEE ALSO.

README.rst

@@ -662,10 +662,10 @@ by the varnishd parameters ``thread_pools``, ``thread_pool_min`` and
 ``thread_pool_max``; this in turn affects how much secure memory will
 need to be available for each object in each thread. ``thread_pools``
 determines how many thread pools there are, and for each pool, at
-least ``thread_pool_min`` will always be started. More threads may be
-started to respond to increasing load, up to the maximum given by
-``thread_pool_max`` for each thread. As load decreases (that is, when
-threads become idle for time given by ``thread_pool_timeout``),
+least ``thread_pool_min`` threads will always be started. More threads
+may be started to respond to increasing load, up to the maximum given
+by ``thread_pool_max`` for each thread. As load decreases (that is,
+when threads become idle for time given by ``thread_pool_timeout``),
 threads will be stopped until the minimum ``thread_pool_min`` is
 reached.
 
@@ -801,6 +801,8 @@ SEE ALSO
 * varnishd(1)
 * vcl(7)
 * varnishlog(1)
+* mlock(2)
+* pthread_key_create(3)
 * libgcrypt: https://gnupg.org/software/libgcrypt/index.html
 * source repository: https://code.uplex.de/uplex-varnish/libvmod-gcrypt
 * VMOD blobcode: https://code.uplex.de/uplex-varnish/libvmod-blobcode

src/vmod_gcrypt.vcc

@@ -730,6 +730,8 @@ SEE ALSO
 * varnishd(1)
 * vcl(7)
 * varnishlog(1)
+* mlock(2)
+* pthread_key_create(3)
 * libgcrypt: https://gnupg.org/software/libgcrypt/index.html
 * source repository: https://code.uplex.de/uplex-varnish/libvmod-gcrypt
 * VMOD blobcode: https://code.uplex.de/uplex-varnish/libvmod-blobcode