docs(forms): Fix typos in template-driven forms tutorial (#37933)

Fix two typos in the 'Building a template-driven form` that caused the guide to not be displayed correctly.

PR Close #37933
This commit is contained in:
Aristeidis Bampakos 2020-07-05 23:45:53 +03:00 committed by Andrew Scott
parent df8b387570
commit 421e807f80
1 changed files with 2 additions and 2 deletions

View File

@ -93,7 +93,7 @@ In the course of this tutorial, you bind a sample form to data and handle user i
* Add custom CSS to provide visual feedback on the status. * Add custom CSS to provide visual feedback on the status.
* Show and hide validation-error messages. * Show and hide validation-error messages.
4. Respond to a native HTML button-click event by adding to the model data. 4. Respond to a native HTML button-click event by adding to the model data.
5. Handle form submission using the [`ngSubmit`(api/forms/NgForm#properties)] output property of the form. 5. Handle form submission using the [`ngSubmit`](api/forms/NgForm#properties) output property of the form.
* Disable the **Submit** button until the form is valid. * Disable the **Submit** button until the form is valid.
* After submit, swap out the finished form for different content on the page. * After submit, swap out the finished form for different content on the page.
@ -467,7 +467,7 @@ You will bind the form property that indicates its overall validity to the **Sub
3. Run the application now. Notice that the button is enabled—although 3. Run the application now. Notice that the button is enabled—although
it doesn't do anything useful yet. it doesn't do anything useful yet.
4. Delete the **Name** value. This violates the "required" rule, so it displays the error message&emdash;and notice that it also disables the **Submit** button. 4. Delete the **Name** value. This violates the "required" rule, so it displays the error message—and notice that it also disables the **Submit** button.
You didn't have to explicitly wire the button's enabled state to the form's validity. You didn't have to explicitly wire the button's enabled state to the form's validity.