Improve wording of "Monitor mode" section

README.md

@@ -168,13 +168,13 @@ Having multiple conf files can then be run in a single cron command like
 
 Monitor mode will perform a sync upon file operations on initiator replica. This can be a drawback on functionality versus scheduled mode because this mode only launches a sync task if there are file modifications on the initiator replica, without being able to monitor the target replica. Target replica changes are only synced when initiator replica changes occur, or when a given amount of time (600 seconds by default) passed without any changes on initiator replica.
 
-File monitor mode can also be launched as a daemon with an init script. Please read the documentation for more info.
+This mode can also be launched as a daemon with an init script. Please read the documentation for more info.
 
 To use this mode, use `--on-changes`:
 
 	# osync.sh /etc/osync/my_sync.conf --on-changes
 
-Osync file monitor mode may be run as system service with the osync-srv script. You may run the install.sh script which should work in most cases or copy the files by hand:
+To run this mode as system service with the `osync-srv` script, you can run the `install.sh` script (which should work in most cases) or copy the files by hand:
 - `osync.sh` to `/usr/bin/local`
 - `sync.conf` to `/etc/osync`
 - For InitV, `osync-srv` to `/etc/init.d`