BaseTools: Various typo

[mirror_edk2.git] / BaseTools / Source / C / VfrCompile / Pccts / CHANGES_SUMMARY.txt

diff --git a/BaseTools/Source/C/VfrCompile/Pccts/CHANGES_SUMMARY.txt b/BaseTools/Source/C/VfrCompile/Pccts/CHANGES_SUMMARY.txt
index 91defae169c4e7f5c3f059ae52130b94715a9e77..7134500e2fbf6d44dcbef02487bc97180d8c7f94 100644 (file)
--- a/BaseTools/Source/C/VfrCompile/Pccts/CHANGES_SUMMARY.txt
+++ b/BaseTools/Source/C/VfrCompile/Pccts/CHANGES_SUMMARY.txt
@@ -1350,7 +1350,7 @@
       the variable [zz]traceOptionValueDefault is set to 0 or 1.  When\r
       the parser is initialized or [zz]traceReset() is called the\r
       value of [zz]traceOptionValueDefault is copied to [zz]traceOptionValue.\r
-      The value of [zz]traceGuessOptionValue is always initialzed to 1,\r
+      The value of [zz]traceGuessOptionValue is always initialized to 1,\r
       but, as noted earlier, nothing will be reported unless\r
       [zz]traceOptionValue is also positive.\r
 \r
@@ -1766,7 +1766,7 @@
         This is especially important for predicates formed by rules\r
         like the following:\r
 \r
-            uppperCaseVowel : <<isUpperCase(LATEXT(1))>>?  vowel;\r
+            upperCaseVowel  : <<isUpperCase(LATEXT(1))>>?  vowel;\r
             vowel:          : <<isVowel(LATEXT(1))>>? LETTERS;\r
 \r
         These predicates are combined using AND since both must be\r
@@ -1928,7 +1928,7 @@
             parse by "falling through".  The parse can still be easily\r
             resumed in other ways, but not in the most natural fashion.\r
 \r
-            This results in an inconsistentcy between named exception\r
+            This results in an inconsistency between named exception\r
             handlers and exception handlers for alternatives.  When\r
             an exception handler for an alternative "falls through"\r
             it goes to the nextmost outer handler - not the "normal\r
@@ -1990,7 +1990,7 @@
         The reason for "Normal Action" is that the normal flow of the\r
         program after a user-written exception handler is to "drop through".\r
         In the case of an exception handler for a rule this results in\r
-        the exection of a "return" statement.  In the case of an\r
+        the execution of a "return" statement.  In the case of an\r
         exception handler attached to an alternative, rule, or token\r
         this is the code that would have executed had there been no\r
         exception.\r