-
-
diff --git a/aio/content/guide/form-validation.md b/aio/content/guide/form-validation.md
index c277b314e5..91c8991b18 100644
--- a/aio/content/guide/form-validation.md
+++ b/aio/content/guide/form-validation.md
@@ -213,27 +213,33 @@ This section shows how to perform cross field validation. It assumes some basic
-If you haven't created custom validators before, start by reviewing the [CustomValidators](guide/form-validation#custom-validators).
+If you haven't created custom validators before, start by reviewing the [custom validators section](guide/form-validation#custom-validators).
-In the following section we will make sure that our heroes do not reveal their true identities by filling out the Hero Form. We will do that by validating that the hero names and alter egos do not match. The form has the following structure:
+In the following section, we will make sure that our heroes do not reveal their true identities by filling out the Hero Form. We will do that by validating that the hero names and alter egos do not match.
+
+### Adding to reactive forms
+
+The form has the following structure:
```javascript
const heroForm = new FormGroup({
'name': new FormControl(),
'alterEgo': new FormControl(),
'power': new FormControl()
-};
+});
```
-Notice that the `name` and `alterEgo` are sibling controls. To evaluate both controls in a single custom validator, we should perform the validation in the ancestor control. That way we can query the form tree for the child controls which will allow us to compare their values.
+Notice that the name and alterEgo are sibling controls. To evaluate both controls in a single custom validator, we should perform the validation in a common ancestor control: the FormGroup. That way, we can query the FormGroup for the child controls which will allow us to compare their values.
+
+To add a validator to the FormGroup, pass the new validator in as the second argument on creation.
```javascript
const heroForm = new FormGroup({
'name': new FormControl(),
- 'alterEgo': new FormControl(),
- 'power': new FormControl()
+ 'alterEgo': new FormControl(),
+ 'power': new FormControl()
}, { validators: identityRevealedValidator });
```
@@ -242,18 +248,11 @@ The validator code is as follows:
-Identity validator implements the `ValidatorFn` interface. It takes an Angular control object as an argument and returns either null if the form is valid, or ValidationErrors otherwise.
+Identity validator implements the `ValidatorFn` interface. It takes an Angular control object as an argument and returns either null if the form is valid, or `ValidationErrors` otherwise.
First we retrieve the child controls by calling the `FormGroup`'s [get](api/forms/AbstractControl#get) method. Then we simply compare the values of the `name` and `alterEgo` controls.
-If the values do not match the hero's identity remains disguised, and we can safely return null. Otherwise, the hero's identity is revealed and we must mark the form as invalid by returning an error object.
-
-
-### Adding to reactive forms
-
-As with all reactive forms, the validator can be registered during the form creation. We make sure to register it at the `FormGroup` level, to give it access to the child controls.
-
-
+If the values do not match, the hero's identity remains secret, and we can safely return null. Otherwise, the hero's identity is revealed and we must mark the form as invalid by returning an error object.
Next, to provide better user experience, we show an appropriate error message when the form is invalid.
@@ -263,34 +262,10 @@ Note that we check if:
- the `FormGroup` has the cross validation error returned by the `identityRevealed` validator,
- the user is yet to [interact](guide/form-validation#why-check-dirty-and-touched) with the form.
-Finally, we want to style the `input` elements to give visual feedback about form control's validity. Unfortunately, the `identityRevealed` error is on the form group control (`heroForm`) and not on the child form controls (`name`, `alterEgo`). That means that the `` and `` will not have the `ng-invalid` class after the cross validation fails.
-
-We can get around this problem by binding our own css class to the same expression that was used to show and hide the validation error message.
-
-
-
-
-
-
-
-
-Below you can inspect the cross validation example for the reactive forms. The example skips over the parts that are not related to cross validation to keep this section focused on a single task. You can see the complete code example at the end of this chapter.
-
-
-
-
-
-
-
-
-
-
-
-
### Adding to template driven forms
-First we must create a directive that will wrap the validator function. We provide it as the validator using the `NG_VALIDATORS` token. If you are not sure why, or you do not fully understand the syntax revisit the previous [section](guide/form-validation#adding-to-template-driven-forms).
+First we must create a directive that will wrap the validator function. We provide it as the validator using the `NG_VALIDATORS` token. If you are not sure why, or you do not fully understand the syntax, revisit the previous [section](guide/form-validation#adding-to-template-driven-forms).
-
+
Next, we have to add the directive to the html template. Since the validator must be registered at the `FormGroup` level, we put the directive on the `form` tag.
@@ -305,32 +280,8 @@ Note that we check if:
- the `FormGroup` has the cross validation error returned by the `identityRevealed` validator,
- the user is yet to [interact](guide/form-validation#why-check-dirty-and-touched) with the form.
-Finally, we want to style the `input` elements to give visual feedback about form control's validity. Unfortunately, the `identityRevealed` error is on the form group control (`heroForm`) and not on the child form controls (`name`, `alterEgo`). That means that the `` and `` will not have the `ng-invalid` class after the cross validation fails.
-
-We can get around this problem by binding our own css class to the same expression that was used to show and hide the validation error message.
-
-
-
-
-
-
-
-
-Below you can inspect the cross validation example for the template-driven forms. The example skips over parts that are not related to cross validation to keep this section focused on a single task. You can see the complete code example at the end of this chapter.
-
-
-
-
-
-
-
-
-
-
-
This completes the cross validation example. We managed to:
- validate the form based on the values of two sibling controls,
-- show a descriptive error message after the user interacted with the form and the validation failed,
-- give visual feedback on the form validity.
+- show a descriptive error message after the user interacted with the form and the validation failed.
**You can run the to see the complete reactive and template-driven example code.**