From c3d6ca97e1618fa7b770d60fdc37b12ff51c65ab Mon Sep 17 00:00:00 2001
From: Wesley Cho
Date: Fri, 29 Nov 2013 09:28:03 -0500
Subject: docs(guide/forms): clarify how NgModelController can be added to
 scope

Closes #5200
---
 docs/content/guide/forms.ngdoc | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

(limited to 'docs/content/guide/forms.ngdoc')

diff --git a/docs/content/guide/forms.ngdoc b/docs/content/guide/forms.ngdoc
index f3f95b7c..ca44e553 100644
--- a/docs/content/guide/forms.ngdoc
+++ b/docs/content/guide/forms.ngdoc
@@ -115,9 +115,14 @@ This ensures that the user is not distracted with an error until after interacti
 
 A form is an instance of {@link api/ng.directive:form.FormController FormController}.
 The form instance can optionally be published into the scope using the `name` attribute.
-Similarly, control is an instance of {@link api/ng.directive:ngModel.NgModelController NgModelController}.
-The control instance can similarly be published into the form instance using the `name` attribute.
-This implies that the internal state of both the form and the control is available for binding in the view using the standard binding primitives.
+
+Similarly, an input control that has the {@link api.ng.directive:ng-model} directive holds an
+instance of {@link api/ng.directive:ngModel.NgModelController NgModelController}.
+Such a control instance can be published as a property of the form instance using the `name` attribute
+on the input control.  The name attribute specifies the name of the property on the form instance.
+
+This implies that the internal state of both the form and the control is available for binding in
+the view using the standard binding primitives.
 
 This allows us to extend the above example with these features:
 
-- 
cgit v1.2.3