docs: update grammar

Update grammar per review.

Co-authored-by: TeriGlover <teriglover@google.com>
PR Close #43245
This commit is contained in:
Joe Martin (Crowdstaffing)
2021-09-14 15:02:00 -07:00
committed by Alex Rickabaugh
parent be1f686531
commit 407490adc7
+3 -3
View File
@@ -48,7 +48,7 @@ The translator may also need to know the meaning or intent of the text message w
Start the `i18n` attribute value with the *meaning* and separate it from the *description* with the `|` character: `<meaning>|<description>`.
For example, you may want to indicate that the `<h1>` tag is a site header that needs to be translated the same way whether it used as a header or referenced in another section of text.
The following example displays how to indicate that the `<h1>` tag needs to be translated as a header or referenced elsewhere.
The following example shows how to indicate that the `<h1>` tag needs to be translated as a header or referenced elsewhere.
<code-example path="i18n/doc-files/app.component.html" region="i18n-attribute-meaning" header="src/app/app.component.html"></code-example>
@@ -85,8 +85,8 @@ That one translation entry is merged back into the application wherever the same
{@a no-element}
If you translate non-displayed text using the `<span>` tag, you create a new DOM element.
To avoid doing a new DOM element, wrap the text in an `<ng-container>` element.
The following example displays the `<ng-container>` element transformed into a non-displayed HTML comment.
To avoid creating a new DOM element, wrap the text in an `<ng-container>` element.
The following example shows the `<ng-container>` element transformed into a non-displayed HTML comment.
<code-example path="i18n/src/app/app.component.html" region="i18n-ng-container"></code-example>