From 8e2675029f5ca404a7c649cc161df3ea642d941f Mon Sep 17 00:00:00 2001
From: Misko Hevery
Date: Sat, 28 Apr 2012 22:45:28 -0700
Subject: chore(docs): re-skin main documentation

---
 docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc')

diff --git a/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc b/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc
index 162bfbce..b95bdf5b 100644
--- a/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc
+++ b/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc
@@ -57,7 +57,7 @@ manipulation—the presentation logic of an application—is well known for bein
 Putting any presentation logic into controllers significantly affects testability of the business
 logic. Angular offers {@link dev_guide.templates.databinding} for automatic DOM manipulation. If
 you have to perform your own manual DOM manipulation, encapsulate the presentation logic in
-{@link api/angular.module.ng.$compileProvider.directive directives}.
+{@link guide/directive directives}.
 - Input formatting — Use {@link dev_guide.forms angular form controls} instead.
 - Output filtering — Use {@link dev_guide.templates.filters angular filters} instead.
 - Run stateless or stateful code shared across controllers — Use {@link dev_guide.services angular
-- 
cgit v1.2.3