Small updates to notifier docs

content/dev/code/inclusion.md

@@ -23,7 +23,7 @@ See [Extra folders](/dev/code/extra_folders/) for a complete list.
 
 ### Auto Loaded Observers 
 
-These are described in the [Notifiers and Observers](/dev/code/notifiers/#auto-loaded-observers) documentation. Auto-loaded Observer files include those in `includes/classes/observers` (and Admin) whose name begins with `auto` and which define a class named **zcObserver** + the [CamelCased](http://en.wikipedia.org/wiki/CamelCase) filename. 
+These are described in the [Notifiers and Observers](/dev/code/notifiers/#auto-loaded-observers) documentation. Auto-loaded Observer files include those in `includes/classes/observers` (and Admin) whose name begins with `auto.` and which define a class named **zcObserver** + the [CamelCased](http://en.wikipedia.org/wiki/CamelCase) filename - for example, `class zcObserverFooObserver`. 
 
 ### Stylesheets 
 

content/dev/code/notifiers.md

@@ -226,6 +226,8 @@ Note that this technique will work so long as your class doesn't have any specia
 
 For example, the *Products Viewed Counter* described [above](#update) could provide the same functionality and not need its auto-loader component if the observer-class file was renamed to `/includes/classes/observers/auto.products_viewed_counter.php` and its class name was updated to be `zcObserverProductsViewedCounter.php`.
 
+**Note:** The text above describes the behavior of auto loading on the storefront side.  Support for auto-loading on the admin side was added in Zen Cart 1.5.7. 
+
 ### Event-Specific Update Methods
 
 Problem: If in one Observer class you attach to a number of different events, a single `update` function will fire for all of those events ... but that means it will likely be receiving different function parameters depending on which event was triggered.