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

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

diff --git a/MdePkg/Include/Protocol/FirmwareVolumeBlock.h b/MdePkg/Include/Protocol/FirmwareVolumeBlock.h
index d44f61558430bab5e8879e65289498b9882391a3..d25a2a0fa0fabdc743a6a2614dc86993e2e57f29 100644 (file)
--- a/MdePkg/Include/Protocol/FirmwareVolumeBlock.h
+++ b/MdePkg/Include/Protocol/FirmwareVolumeBlock.h
@@ -206,9 +206,9 @@ EFI_STATUS
   function, or else the result will be unpredictable. This\r
   unpredictability arises because, for a sticky-write firmware\r
   volume, a write may negate a bit in the EFI_FVB_ERASE_POLARITY\r
-  state but it cannot flip it back again. In general, before\r
+  state but cannot flip it back again. In general, before\r
   calling the Write() function, the caller should call the\r
-  EraseBlocks() function first to erase the specified block to\r
+  EraseBlocks() function first to erase the block it intends to\r
   write. A block erase cycle will transition bits from the\r
   (NOT)EFI_FVB_ERASE_POLARITY state back to the\r
   EFI_FVB_ERASE_POLARITY state. Implementations should be\r
@@ -276,7 +276,7 @@ EFI_STATUS
 /**\r
   Erases and initializes a firmware volume block.\r
 \r
-  The EraseBlocks() function erases one or more blocks as denoted\r
+  The EraseBlocks() function erases one or more blocks, as denoted\r
   by the variable argument list. The entire parameter list of\r
   blocks must be verified before erasing any blocks. If a block is\r
   requested that does not exist within the associated firmware\r