Reviewed the code comments in the Include/Protocol directory for typos, grammar issues, and language clarity.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@8462 6f19259b-4bc3-4df7-8a09-765794883524

1 files changed, 3 insertions, 3 deletions

diff --git a/MdePkg/Include/Protocol/FirmwareVolumeBlock.h b/MdePkg/Include/Protocol/FirmwareVolumeBlock.h
index d44f615584..d25a2a0fa0 100644
--- 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

   unpredictability arises because, for a sticky-write firmware

   volume, a write may negate a bit in the EFI_FVB_ERASE_POLARITY

-  state but it cannot flip it back again. In general, before

+  state but cannot flip it back again. In general, before

   calling the Write() function, the caller should call the

-  EraseBlocks() function first to erase the specified block to

+  EraseBlocks() function first to erase the block it intends to

   write. A block erase cycle will transition bits from the

   (NOT)EFI_FVB_ERASE_POLARITY state back to the

   EFI_FVB_ERASE_POLARITY state. Implementations should be

@@ -276,7 +276,7 @@ EFI_STATUS
 /**

   Erases and initializes a firmware volume block.

 

-  The EraseBlocks() function erases one or more blocks as denoted

+  The EraseBlocks() function erases one or more blocks, as denoted

   by the variable argument list. The entire parameter list of

   blocks must be verified before erasing any blocks. If a block is

   requested that does not exist within the associated firmware