BaseTools: Remove duplicated words in C tools

In an effort to clean the documentation of the above
package, remove duplicated words.

Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Reviewed-by: Bob Feng <bob.c.feng@intel.com>
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>

diff --git a/BaseTools/Source/C/Common/FirmwareVolumeBuffer.c b/BaseTools/Source/C/Common/FirmwareVolumeBuffer.c
index 70741c8afcb58516e2e0010b935d49e4f6ada11c..ace26eb71c6bd724f8c79b75c166ac9ba79c2b19 100644 (file)
--- a/BaseTools/Source/C/Common/FirmwareVolumeBuffer.c
+++ b/BaseTools/Source/C/Common/FirmwareVolumeBuffer.c
@@ -91,7 +91,7 @@ Routine Description:
 \r
 Arguments:\r
 \r
-  SourceFv - Address of the Fv in memory, this firmware volume volume will\r
+  SourceFv - Address of the Fv in memory, this firmware volume will\r
              be modified, if SourceFfsFile exists\r
   SourceFfsFile - Input FFS file to replace\r
 \r
@@ -141,7 +141,7 @@ Routine Description:
 \r
 Arguments:\r
 \r
-  SourceFv - Address of the Fv in memory, this firmware volume volume will\r
+  SourceFv - Address of the Fv in memory, this firmware volume will\r
              be modified, if SourceFfsFile exists\r
   SourceFfsFile - Input FFS file to replace\r
 \r
@@ -285,7 +285,7 @@ Routine Description:
 \r
 Arguments:\r
 \r
-  SourceFv - Address of the Fv in memory, this firmware volume volume will\r
+  SourceFv - Address of the Fv in memory, this firmware volume will\r
              be modified, if SourceFfsFile exists\r
   SourceFfsFile - Input FFS file to replace\r
 \r

diff --git a/BaseTools/Source/C/DevicePath/DevicePathUtilities.c b/BaseTools/Source/C/DevicePath/DevicePathUtilities.c
index 2ffefa8ceeeff9a1d0504ad71918c9f0d9fd1aab..49078aac8caf8efde292525c99d0e2e0fdfa468b 100644 (file)
--- a/BaseTools/Source/C/DevicePath/DevicePathUtilities.c
+++ b/BaseTools/Source/C/DevicePath/DevicePathUtilities.c
@@ -37,7 +37,7 @@ CONST EFI_DEVICE_PATH_PROTOCOL  mUefiDevicePathLibEndDevicePath = {
   @retval TRUE        DevicePath is valid.\r
   @retval FALSE       DevicePath is NULL.\r
   @retval FALSE       Maxsize is less than sizeof(EFI_DEVICE_PATH_PROTOCOL).\r
-  @retval FALSE       The length of any node node in the DevicePath is less\r
+  @retval FALSE       The length of any node in the DevicePath is less\r
                       than sizeof (EFI_DEVICE_PATH_PROTOCOL).\r
   @retval FALSE       If MaxSize is not zero, the size of the DevicePath\r
                       exceeds MaxSize.\r

diff --git a/BaseTools/Source/C/GenFv/GenFv.c b/BaseTools/Source/C/GenFv/GenFv.c
index 43cc5cd3fe822f645676929ff74bea93b09d567b..a742d55e52708dc4ee3b8514886b8263d2e9eecb 100644 (file)
--- a/BaseTools/Source/C/GenFv/GenFv.c
+++ b/BaseTools/Source/C/GenFv/GenFv.c
@@ -299,7 +299,7 @@ Returns:
         return STATUS_ERROR;\r
       }\r
       if (TempNumber == 0) {\r
-        Error (NULL, 0, 1003, "Invalid option value", "Fv block size can't be be set to zero");\r
+        Error (NULL, 0, 1003, "Invalid option value", "Fv block size can't be set to zero");\r
         return STATUS_ERROR;\r
       }\r
       mFvDataInfo.FvBlocks[0].Length = (UINT32) TempNumber;\r

diff --git a/BaseTools/Source/C/VfrCompile/Pccts/antlr/mrhoist.c b/BaseTools/Source/C/VfrCompile/Pccts/antlr/mrhoist.c
index b57f5ded846cf1401866858c4a161727d1af9b82..bf3dd18eaf6f737da7d798f2fc3ba92e5dfbfb89 100644 (file)
--- a/BaseTools/Source/C/VfrCompile/Pccts/antlr/mrhoist.c
+++ b/BaseTools/Source/C/VfrCompile/Pccts/antlr/mrhoist.c
@@ -714,7 +714,7 @@ Tree *MR_compute_pred_tree_ctxXX(p)
     if (p == NULL) return NULL;\r
 \r
 /* this appears strange: why do we OR the context\r
-   of and AND predicate ?  It is because of the way\r
+   of an AND predicate ?  It is because of the way\r
    that predicates are evaluated: if the context is\r
    wrong then it's the same as if the predicate was\r
    true.  That means that even when one leg of an\r
@@ -1531,7 +1531,7 @@ Predicate * MR_find_in_aSubBlk(alt)
  *      1.  if lookahead for alt i is contained in the lookahead for any\r
  *          alt j then ignore semantic predicate of alt i\r
  *      2.  if lookahead for alt i is not contained in the lookahead for\r
- *          any alt j then add add predicate i to the OR list to be hoisted\r
+ *          any alt j then add predicate i to the OR list to be hoisted\r
  *      3.  if lookahead for alt i overlaps the lookahead for some alt j then\r
  *          add a dummy semantic predicate for alt j\r
  *\r