From 716b5fd3e24e11986ded2cc381b9fbb77971a1e2 Mon Sep 17 00:00:00 2001 From: Igor Minar Date: Tue, 13 Mar 2012 23:00:30 -0700 Subject: docs(*): fixing various docs --- docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (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 17928adc..b5fe6bd8 100644 --- a/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc +++ b/docs/content/guide/dev_guide.mvc.understanding_controller.ngdoc @@ -65,9 +65,9 @@ Do not use controllers for: manipulation—the presentation logic of an application—is well known for being hard to test. 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 and +you have to perform your own manual DOM manipulation, encapsulate the presentation logic in {@link api/angular.module.ng.$compileProvider.directive directives}. -- Input formatting — Use {@link dev_guide.forms angular form widgets} instead. +- 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 services} instead. -- cgit v1.2.3