Update readme

Author: jcberquist

README.md

@@ -11,9 +11,15 @@ If it is passed a component path it will, by default, print the formatted compon
 
 When passed a directory, `cfformat` always overwrites component files in place, and so it will ask for confirmation before proceeding. Here you can use the `--overwrite` flag to skip this confirmation check.
 
+`cfformat` can also be called with a directory path and the `--watch` flag. When this is done, `cfformat` will use CommandBox's built in support for file watching to watch that directory for component changes, and will perform formatting passes on those files.
+
+```bash
+cfformat ./ --watch
+```
+
 ## Settings
 
-To see the settings used for formatting, use the `--settings` flag. When that is present the `cfformat` command will just dump to the console the settings it will use to format, and not perform any formatting:
+To see the settings used for formatting, use the `--settings` flag. When that is present the `cfformat` command will just dump the settings it will use to format to the console, and not perform any formatting:
 
 ```bash
 cfformat --settings
@@ -43,6 +49,13 @@ Specifying a settings file to use inline when running `cfformat` is done as foll
 cfformat path/to/my.cfc /path/to/.cfformat.json
 ```
 
+For more information on the settings used and what they do please see the [reference](reference.md). You can also print reference information to the console using the `settingInfo` argument. `settingInfo` can be passed either a full setting name, or just a prefix:
+
+```bash
+cfformat settingInfo=array.padding
+cfformat settingInfo=array
+```
+
 ## Syntect
 
 Behind the scenes, `cfformat` makes use of the [syntect](https://github.com/trishume/syntect) library along with syntax files from Sublime Text's [Packages](https://github.com/sublimehq/Packages) repository to create an executable that uses the CFML syntax for Sublime Text to generate syntax scopes for component files. `cfformat` attempts to download this executable from GitHub when installed, or when it is updated (if necessary). If it is unable to download the executable, it should print a message to the console prompting you to download from GitHub, and indicating where to put it. If you have Rust installed, you can also build the executable yourself by running the `build.cfc` task runner in the root of this repository: