Merge pull request #15 from jcberquist/source

minor documentation updates

Author: seancorfield

source/documentation/3.5/developing-applications.markdown

@@ -628,7 +628,7 @@ The keys in the structure have the following meanings:
 * `controllersFolder` - The name used for the controllers folder. Must be plural. Defaults to `"controllers"` but could be `"handlers"` for example. _New in 3.5._
 * `layoutsFolder` - The name used for the layouts folder. Must be plural. Defaults to `"layouts"` but could be `"wrappers"` for example. _New in 3.5._
 * `subsystemsFolder` - The name used for the subsystems folder. Must be plural. Defaults to `"subsystems"` but could be `"plugins"` for example. _New in 3.5._
-* `viewssFolder` - The name used for the views folder. Must be plural. Defaults to `"views"` but could be `"pages"` for example. _New in 3.5._
+* `viewsFolder` - The name used for the views folder. Must be plural. Defaults to `"views"` but could be `"pages"` for example. _New in 3.5._
 * `diOverrideAllowed` - If `true`, FW/1 will throw an exception if you attempt to call `setBeanFactory()` twice. If `false`, FW/1 will allow you to call `setBeanFactory()` twice and override the previous Dependency Injection setting, but it will log a warning to the console. If you want FW/1 to manage your bean factory, use the `di*` settings above to configure it -- and do not call `setBeanFactory()` yourself. If you want to manage your bean factory directly, set `diEngine` to `"none"` so FW/1 doesn't also attempt to do this. _New in 3.5._
 * `diEngine` - The Dependency Injection framework that FW/1 should use.
 * `diLocations` - The list of folders to check for CFCs to manage; defaults to `[ "model", "controllers" ]`.

source/documentation/3.5/reference-manual.markdown

@@ -449,11 +449,11 @@ Will generate:
 
 If `header` is provided (as a non-empty string), instead of performing an actual redirect, FW/1 will set the named HTTP header to the target URL and then abort the controller lifecycle. This allows custom handling of "redirects" in AJAX-based applications.
 
-### Public void function redirectCustomURL( string uri, string preserve = 'none', string statusCode = '302', string header = '' )
+### public void function redirectCustomURL( string uri, string preserve = 'none', string statusCode = '302', string header = '' )
 
 This is to `redirect()` as `buildCustomURL()` is to `buildURL()`.
 
-### public void function renderData( string type, any data, numeric statusCode = 200, jsonpCallback = "" )
+### public void function renderData( string type, any data, numeric statusCode = 200, string jsonpCallback = "" )
 
 Call this from your controller to tell FW/1 to skip views and layouts
 and instead render `data` in the specified content `type` format. `type`

source/documentation/3.5/using-di-one.markdown

@@ -171,6 +171,7 @@ When you create the bean factory, you can optionally supply a second argument th
 * `exclude` - array - defaults to `[]`. DI/1 will ignore any CFCs whose file path contains the strings in this array. DI/1 always excludes paths containing `/WEB-INF` and `/Application.cfc`, as well as various FW/1 and DI/1 framework files. The strings are not case-sensitive.
 * `initMethod` - string - If specified, identifies a method name on beans that DI/1 will attempt to call (with no arguments) on each bean after its dependencies have been injected.
 * `liberal` - boolean - default to `false`. If `true`, treat folder names ending in `ies` as plurals (of names ending in `y`, e.g., `libraries` would be treated as the plural of `librarie` by default, but with `liberal : true`, it would be treated as the plural of `library`).
+* `loadListener` - any - If specified, DI/1 will register it as a load listener by calling `this.onLoad( loadListener )`. It can be a CFC instance, the name of a bean, or a function or closure.
 * `omitDirectoryAliases` - boolean - defaults to `false`. If `true`, use CFC names as bean names directly, without appending the singular directory name as a suffix. If your CFC names are not unique, you will get an exception.
 * `omitTypedProperties` - boolean - defaults to `false`. If `true`, property declarations that specify a type will be ignored for injection. That is useful if you are working with the ORM (since those property declarations will have types and should not be treated as dependencies).
 * `recurse` - boolean - defaults to `true`. Controls whether DI/1 searches subfolders recursively or not.