README.md in remote_syslog-1.6.5 vs README.md in remote_syslog-1.6.6.rc1

@@ -69,10 +69,16 @@
 exists, write PID to `/tmp/remote_syslog.pid`, and send with facility local0
 to `a.server.com:514`:
 
     $ remote_syslog -D -d a.server.com -f local0 -P /tmp /var/log/mysqld.log
 
+### Windows
+
+To run in Windows, start in a DOS Prompt or batch file and do not daemonize:
+
+    C:\> remote_syslog -D
+
 ## Auto-starting at boot
 
 The gem includes sample [init files] such as [remote_syslog.init.d]. remote_syslog will 
 daemonize by default. You may be able to:
 
@@ -139,16 +145,22 @@
     ssl_client_private_key: syslog_client.key
 
 
 ### Detecting new files
 
-All input files (filenames or globs) are re-checked for new files every 60
-seconds. Ruby's `Dir.glob` is used.
+remote_syslog automatically detects and activates new log files that match 
+its file specifiers. For example, `*.log` may be provided as a file specifier, 
+and remote_syslog will detect a `some.log` file created after it was started. 
+Globs are re-checked every 60 seconds. Ruby's `Dir.glob` is used.
 
-This means that files may be added and removed as long as they match a glob 
-path provided to `remote_syslog`. Also, explicitly-provided filenames need 
-not exist when `remote_syslog` is started. `remote_syslog` can be preconfigured 
-to monitor log files which are created later (or may never be created).
+Also, explicitly-provided filenames need not exist when `remote_syslog` is 
+started. `remote_syslog` can be pre-configured to monitor log files which are 
+created later (or may never be created).
+
+If globs are specified on the command-line, enclose each one in single-quotes 
+(`'*.log'`) so the shell passes the raw glob string to remote_syslog (rather 
+than the current set of matches). This is not necessary for globs defined in 
+the config file.
 
 
 ### Multiple instances
 
 Run multiple instances to support more than one message-specific file format