README.md in clockwork-1.0.2 vs README.md in clockwork-1.1.0

@@ -325,10 +325,13 @@
 ### :sleep_timeout
 
 Clockwork wakes up once a second and performs its duties. To change the number of seconds Clockwork
 sleeps, set the `sleep_timeout` configuration option as shown below in the example.
 
+From 1.1.0, Clockwork does not accept `sleep_timeout` less than 1 seconds.
+This restriction is introduced to solve more severe bug [#135](https://github.com/tomykaira/clockwork/pull/135).
+
 ### :tz
 
 This is the default timezone to use for all events.  When not specified this defaults to the local
 timezone.  Specifying :tz in the parameters for an event overrides anything set here.
 
@@ -464,26 +467,26 @@
 topography:
 
 * App server 1: 3 web (thin start), 3 workers (rake jobs:work), 1 clock (clockwork clock.rb)
 * App server 2: 3 web (thin start), 3 workers (rake jobs:work)
 
-You should use Monit, God, Upstart, or Inittab to keep your clock process
+You should use [Monit](http://mmonit.com/monit/), [God](https://github.com/mojombo/god), [Upstart](http://upstart.ubuntu.com/), or [Inittab](http://www.tldp.org/LDP/sag/html/config-init.html) to keep your clock process
 running the same way you keep your web and workers running.
 
 Daemonization
 -------------
 
 Thanks to @fddayan, `clockworkd` executes clockwork script as a daemon.
 
-You will need the `daemons` gem to use `clockworkd`.  It is not automatically installed, please install by yourself.
+You will need the [daemons gem](https://github.com/ghazel/daemons) to use `clockworkd`.  It is not automatically installed, please install by yourself.
 
 Then,
 
 ```
 clockworkd -c YOUR_CLOCK.rb start
 ```
 
-For more details, see help shown by `clockworkd`.
+For more details, you can run `clockworkd -h`.
 
 Issues and Pull requests
 ------------------------
 
 If you find a bug, please create an issue - [Issues · tomykaira/clockwork](https://github.com/tomykaira/clockwork/issues).