From 421e807f80651a746caa3ba9da2bc3706f6b8471 Mon Sep 17 00:00:00 2001 From: Aristeidis Bampakos Date: Sun, 5 Jul 2020 23:45:53 +0300 Subject: [PATCH] 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 --- aio/content/guide/forms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aio/content/guide/forms.md b/aio/content/guide/forms.md index ad00df810c..6fd30c28ab 100644 --- a/aio/content/guide/forms.md +++ b/aio/content/guide/forms.md @@ -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. * Show and hide validation-error messages. 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. * 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 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.