README.md in r509-ca-http-0.3.1 vs README.md in r509-ca-http-0.3.2

@@ -23,11 +23,11 @@
 
 Required POST parameters:
 
 - ca
 - profile
-- validityPeriod (in days)
+- validityPeriod (in seconds)
 - csr (or spki)
 - subject
 
 The subject is provided like so:
 
@@ -92,13 +92,17 @@
 
 Running r509-ca-http will let you issue and revoke certificates. But that's not everything you need to do, if you're going to run a CA. You're going to need information about validity, and you may want to save a record of issued certificates to the filesystem.
 
 For that, we've created a few pieces of Rack middleware for your use.
 
-- [r509-middleware-validity](https://github.com/sirsean/r509-middleware-validity)
-- [r509-middleware-certwriter](https://github.com/sirsean/r509-middleware-certwriter)
+- [r509-middleware-validity](https://github.com/r509/r509-middleware-validity)
+- [r509-middleware-certwriter](https://github.com/r509/r509-middleware-certwriter)
 
-After installing one or both of them, you'll have to edit your ```config.ru`` and/or ```config.yaml``` files.
+After installing one or both of them, you'll have to edit your ```config.ru``` and/or ```config.yaml``` files.
+
+##Signals
+
+You can send a kill -USR2 signal to any running r509-ca-http process to cause it to reload and print its config to the logs (provided your app server isn't trapping USR2 first).
 
 ##Support
 
 You can file bugs on GitHub or join the #r509 channel on irc.freenode.net to ask questions.