Reviewed the code comments in the Include/Protocol directory for typos, grammar issue...

[mirror_edk2.git] / MdePkg / Include / Protocol / SimpleTextInEx.h

diff --git a/MdePkg/Include/Protocol/SimpleTextInEx.h b/MdePkg/Include/Protocol/SimpleTextInEx.h
index 430ec601bed9bdecf70efe25c0d091583d488c2e..df5e6fd393842490658a25ddac98d72250b0234b 100644 (file)
--- a/MdePkg/Include/Protocol/SimpleTextInEx.h
+++ b/MdePkg/Include/Protocol/SimpleTextInEx.h
@@ -58,8 +58,8 @@ EFI_STATUS
 \r
 \r
 ///\r
-/// EFI_KEY_TOGGLE_STATE. The toggle state are defined.\r
-/// They are EFI_TOGGLE_STATE_VALID, EFI_SCROLL_LOCK_ACTIVE\r
+/// EFI_KEY_TOGGLE_STATE. The toggle states are defined.\r
+/// They are: EFI_TOGGLE_STATE_VALID, EFI_SCROLL_LOCK_ACTIVE\r
 /// EFI_NUM_LOCK_ACTIVE, EFI_CAPS_LOCK_ACTIVE\r
 ///\r
 typedef UINT8 EFI_KEY_TOGGLE_STATE;\r
@@ -149,29 +149,28 @@ typedef struct {
   there is no pending keystroke the function returns\r
   EFI_NOT_READY. If there is a pending keystroke, then\r
   KeyData.Key.ScanCode is the EFI scan code defined in Error!\r
-  Reference source not found.. The KeyData.Key.UnicodeChar is the\r
-  actual printable character or is zero if the key does not\r
+  Reference source not found. The KeyData.Key.UnicodeChar is the\r
+  actual printable character, or is zero if the key does not\r
   represent a printable character (control key, function key,\r
   etc.). The KeyData.KeyState is shift state for the character\r
   reflected in KeyData.Key.UnicodeChar or KeyData.Key.ScanCode .\r
-  When interpreting the data from this function, it should be\r
-  noted that if a class of printable characters that are\r
+  When interpreting the data from this function, printable characters that are\r
   normally adjusted by shift modifiers (e.g. Shift Key + "f"\r
-  key) would be presented solely as a KeyData.Key.UnicodeChar\r
-  without the associated shift state. So in the previous example\r
-  of a Shift Key + "f" key being pressed, the only pertinent\r
+  key) are presented solely as a KeyData.Key.UnicodeChar\r
+  without the associated shift state. For example,\r
+  if Shift Key + "f" key are pressed, the only pertinent\r
   data returned would be KeyData.Key.UnicodeChar with the value\r
-  of "F". This of course would not typically be the case for\r
-  non-printable characters such as the pressing of the Right\r
-  Shift Key + F10 key since the corresponding returned data\r
+  of "F". This would not typically be the case for\r
+  non-printable characters such as pressing the Right\r
+  Shift Key + F10 key, since the corresponding returned data\r
   would be reflected both in the KeyData.KeyState.KeyShiftState\r
   and KeyData.Key.ScanCode values. UEFI drivers which implement\r
   the EFI_SIMPLE_TEXT_INPUT_EX protocol are required to return\r
   KeyData.Key and KeyData.KeyState values. These drivers must\r
   always return the most current state of\r
   KeyData.KeyState.KeyShiftState and\r
-  KeyData.KeyState.KeyToggleState. It should also be noted that\r
-  certain input devices may not be able to produce shift or toggle\r
+  KeyData.KeyState.KeyToggleState. \r
+  Certain input devices may not be able to produce shift or toggle\r
   state information, and in those cases the high order bit in the\r
   respective Toggle and Shift state fields should not be active.\r
 \r
@@ -238,7 +237,7 @@ EFI_STATUS
 \r
 /**\r
   The RegisterKeystrokeNotify() function registers a function\r
-  which will be called when a specified keystroke will occur.\r
+  to be called when a specified keystroke will occur.\r
   \r
   @param This                     A pointer to the EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL instance.\r
   \r
@@ -271,8 +270,8 @@ EFI_STATUS
 );\r
 \r
 /**\r
-  The UnregisterKeystrokeNotify() function removes the\r
-  notification which was previously registered.\r
+  The UnregisterKeystrokeNotify() function removes a\r
+  notification that was previously registered.\r
   \r
   @param This               A pointer to the EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL instance.\r
   \r