diff --git a/reference/blueprint-api/blueprint-api.md b/reference/blueprint-api/blueprint-api.md
index c0faaac85..bce31c6fc 100644
--- a/reference/blueprint-api/blueprint-api.md
+++ b/reference/blueprint-api/blueprint-api.md
@@ -26,7 +26,7 @@ See the [blueprints subsection of the configuration reference](http://sailsjs.or
 
 Blueprint actions (not to be confused with blueprint action *routes*) are generic actions designed to work with any of your controllers that have a model of the same name (e.g. `ParrotController` would need a `Parrot` model).  Think of them as the default behavior for your application.  For instance, if you have a `User.js` model and an empty `UserController.js` controller, `find`, `create`, `update`, `destroy`, `populate`, `add` and `remove` actions exist implicitly, without you having to write them.
 
-By default, the blueprint RESTful routes and shortcut routes are bound to their corresponding blueprint actions.  However, any blueprint action can be overridden for a particular controller by creating a custom action in that controller file (e.g. `ParrotController.find`).  Alternatively, you can override the blueprint action _everywhere in your app_ by creating your own [custom blueprint action](http://sailsjs.org/documentation/guides/customBlueprints). (e.g. `api/blueprints/create.js`).
+By default, the blueprint RESTful routes and shortcut routes are bound to their corresponding blueprint actions.  However, any blueprint action can be overridden for a particular controller by creating a custom action in that controller file (e.g. `ParrotController.find`).  Alternatively, you can override the blueprint action _everywhere in your app_ by creating your own custom blueprint action. (e.g. `api/blueprints/create.js`).
 
 The current version of Sails ships with the following blueprint actions: