From fd23663a29058ee4593ed29d306ef2037ed352a7 Mon Sep 17 00:00:00 2001
From: Shawn Clabough <sclabough@wsu.edu>
Date: Wed, 29 May 2019 12:19:53 -0700
Subject: [PATCH] docs: fix closing tags in deprecation summary (#30735)

 fix closing tags in "Cannot assign to template variables" section

PR Close #30735
---
 aio/content/guide/deprecations.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/aio/content/guide/deprecations.md b/aio/content/guide/deprecations.md
index 82af74b934..b4ab940d55 100644
--- a/aio/content/guide/deprecations.md
+++ b/aio/content/guide/deprecations.md
@@ -346,13 +346,13 @@ In the following example, the two-way binding means that `optionName`
 should be written when the `valueChange` event fires.
 
 ```html
-<option *ngFor="let optionName of options" [(value)]="optionName"></cmp>
+<option *ngFor="let optionName of options" [(value)]="optionName"></option>
 ```
 
 However, in practice, Angular simply ignores two-way bindings to template variables. Starting in version 8, attempting to write to template variables is deprecated. In a future version, we will throw to indicate that the write is not supported.
 
 ```html
-<option *ngFor="let optionName of options" [value]="optionName"></cmp>
+<option *ngFor="let optionName of options" [value]="optionName"></option>
 ```
 
 {@a binding-to-innertext}