docs(reactive-forms): Kara's Rnd 2 comments

Author: kapunahelewong

public/docs/ts/latest/guide/reactive-forms.jade

@@ -55,7 +55,7 @@ a#intro
   in the component class and bind them to native form control elements in the 
   component template, using techniques described in this guide. 
 
-  With reactive forms, you create and manipulate form control objects directly in the 
+  You create and manipulate form control objects directly in the 
   component class. As the component class has immediate access to both the data 
   model and the form control structure, you can push data model values into 
   the form controls and pull user-changed values back out. The component can 
@@ -90,7 +90,6 @@ a#intro
   Angular updates the mutable _data model_ with user changes as they happen.
 
   When writing in a reactive style, you rarely, if ever, use two-way data binding. 
-  For this reason, the `ngModel` directive is not part of the ReactiveFormsModule.
 
   These differences reflect two architectural paradigms, 
   with their own strengths and weaknesses,
@@ -173,11 +172,16 @@ a#create-template
 :marked
   ## Create the template
 
-  
   Now create the component's template, `app/hero-detail.component.html`, with the following markup.
 
 +makeExample('reactive-forms/ts/app/hero-detail-1.component.html', 'simple-control','app/hero-detail.component.html')(format=".")
 
+:marked
+  To let Angular know that this is the input that you want to 
+  associate to the `name` `FormControl` in the class, 
+  you need `[formControl]="name"` in the template on the `<input>`. 
+  
+
 .l-sub-section
   :marked
     Disregard the `form-control` _CSS_ class. It belongs to the 
@@ -189,8 +193,8 @@ a#import
 :marked
   ## Import the _ReactiveFormsModule_
 
-  The HeroDetailComponent template uses `formGroup` and `formControlName` 
-  directives from the `ReactiveFormsModule`.
+  The HeroDetailComponent template uses `formControlName` 
+  directive from the `ReactiveFormsModule`.
 
   In this sample, you declare the `HeroDetailComponent` in the `AppModule`.
   Therefore, do the following three things in `app.module.ts`:
@@ -249,7 +253,8 @@ figure.image-display
 a#formgroup
 :marked
   ## Add a FormGroup
-  Usually, *FormControls* reside within a `FormGroup`. 
+  Usually, if you have multiple *FormControls*, you'll want to register 
+  them within a parent `FormGroup`.
   This is simple to do. To add a `FormGroup`, add it to the imports section 
   of `hero-detail.component.ts`:
 
@@ -362,7 +367,9 @@ a#validators
 :marked
  Then, you can easily make the `name` `FormControl` required by supplying the `name` 
  property in the class with an array that holds two arguments, 
- the initial value for `name` and `Validators.required`.  
+ the initial value for `name` and `Validators.required`. By contrast, 
+ in template driven forms, you must wrap validators in a directive. 
+ Reactive validators are simple, composable functions.
 
 +makeExample('reactive-forms/ts/app/hero-detail-3.component.ts', 'required','app/hero-detail.component.ts (excerpt)')(format=".")
 
@@ -597,8 +604,8 @@ a#set-data
   error messages if you have a typo or if you've nested controls incorrectly. 
   `patchValue` will fail silently.
 
-  If you have a typo or nested controls incorrectly, `setValue` will catch 
-  the error and report it clearly. `patchValue` will fail silently.
+  On the other hand,`setValue` will catch 
+  the error and report it clearly. 
 
   Notice that you can _almost_ use the entire `hero` as the argument to `setValue`
   because its shape is similar to the component's `FormGroup` structure.
@@ -964,7 +971,7 @@ a#appendix
   This also affects testing of template-driven forms. You always 
   have to wrap your test block in `async()` or `fakeAsync()` to 
   avoid looking for values in the form that aren't available yet. 
-  With reactive forms, you don't everything is available 
+  With reactive forms, everything is available 
   when you expect it to be.