doc(errors): update docs related to throwing errors

The documentation was not clear that epilogue specific errors need
to be imported before being used.

Author: Matt Broadstone

README.md

@@ -64,9 +64,13 @@ Controller actions in turn have hooks for setting and overriding behavior at eac
 We have these milestones to work with: `start`, `auth`, `fetch`, `data`, `write`, `send`, and `complete`.
 
 ```javascript
+var ForbiddenError = require('epilogue').Errors.ForbiddenError;
+
 // disallow deletes on users
 users.delete.auth(function(req, res, context) {
     throw new ForbiddenError("can't delete a user");
+    // optionally:
+    // return context.error(403, "can't delete a user");
 })
 ```
 
@@ -153,6 +157,8 @@ module.exports = {
 To show an error and halt execution of milestone functions you can throw an error:
 
 ```javascript
+var ForbiddenError = require('epilogue').Errors.ForbiddenError;
+
 before: function(req, res, context) {
     return authenticate.then(function(authed) {
         if(!authed) throw new ForbiddenError();

docs/Milestones.md

@@ -94,6 +94,8 @@ users.list.fetch.before(function(req, res, context) {
 });
 
 // example for 2 and 4
+var ForbiddenError = require('epilogue').Errors.ForbiddenError;
+
 users.list.fetch.before(function(req, res, context) {
 	return checkLoggedIn(function(loggedIn) {
 		if(!loggedIn) {
@@ -234,4 +236,4 @@ The default implementation is to do the following:
 
 All Sequelize ValidationError objects are wrapped in a BadRequestError and are accessed on error.cause.
 Any EpilogueError object are passed as-is and any other errors are wrapped in an EpilogueError and can be accessed on
-error.cause
+error.cause