Skip to content

Commit 02ee9d2

Browse files
bampakoaatscott
authored andcommitted
docs(forms): Fix typos in template-driven forms tutorial (angular#37933)
Fix two typos in the 'Building a template-driven form` that caused the guide to not be displayed correctly. PR Close angular#37933
1 parent a4c7f18 commit 02ee9d2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

aio/content/guide/forms.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ In the course of this tutorial, you bind a sample form to data and handle user i
9393
* Add custom CSS to provide visual feedback on the status.
9494
* Show and hide validation-error messages.
9595
4. Respond to a native HTML button-click event by adding to the model data.
96-
5. Handle form submission using the [`ngSubmit`(api/forms/NgForm#properties)] output property of the form.
96+
5. Handle form submission using the [`ngSubmit`](api/forms/NgForm#properties) output property of the form.
9797
* Disable the **Submit** button until the form is valid.
9898
* After submit, swap out the finished form for different content on the page.
9999

@@ -467,7 +467,7 @@ You will bind the form property that indicates its overall validity to the **Sub
467467
3. Run the application now. Notice that the button is enabled—although
468468
it doesn't do anything useful yet.
469469

470-
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.
470+
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.
471471

472472

473473
You didn't have to explicitly wire the button's enabled state to the form's validity.

0 commit comments

Comments
 (0)