diff --git a/aio/content/guide/angular-compiler-options.md b/aio/content/guide/angular-compiler-options.md
index d79b2e841fd..123162d3b70 100644
--- a/aio/content/guide/angular-compiler-options.md
+++ b/aio/content/guide/angular-compiler-options.md
@@ -88,16 +88,16 @@ When `true`, the compiler does not check the TypeScript version and does not rep
 
 ### `enableI18nLegacyMessageIdFormat`
 
-Instructs the Angular template compiler to generate legacy ids for messages that are tagged in templates by the `i18n` attribute.
+Instructs the Angular template compiler to generate legacy IDs for messages that are tagged in templates by the `i18n` attribute.
 See [Localizing your app](guide/i18n#mark-text-for-translations) for more information about marking messages for localization.
 
-Set this option to `false` unless your project relies upon translations that were previously generated using legacy ids. Default is `true`.
+Set this option to `false` unless your project relies upon translations that were previously generated using legacy IDs. Default is `true`.
 
-The pre-Ivy message extraction tooling generated a variety of legacy formats for extracted message ids.
+The pre-Ivy message extraction tooling generated a variety of legacy formats for extracted message IDs.
 These message formats have a number of issues, such as whitespace handling and reliance upon information inside the original HTML of a template.
 
 The new message format is more resilient to whitespace changes, is the same across all translation file formats, and can be generated directly from calls to `$localize`.
-This allows `$localize` messages in application code to use the same id as identical `i18n` messages in component templates.
+This allows `$localize` messages in application code to use the same ID as identical `i18n` messages in component templates.
 
 ### `enableIvy`