OvmfPkg: Fix typing errors

Correct some typos (discovered with the codespell utility)

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Thomas Huth <thuth@redhat.com>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>

diff --git a/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpi.c b/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpi.c
index faaff3757cdb69bf76fb35b7c301acf4f5a8acd2..deaf14c6b0dccf3a17fba4823e5b5c1966c60050 100644 (file)
--- a/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpi.c
+++ b/OvmfPkg/AcpiPlatformDxe/QemuFwCfgAcpi.c
@@ -363,7 +363,7 @@ ProcessCmdAddChecksum (
   array is an ACPI table, and if so, install it.\r
 \r
   This function assumes that the entire QEMU linker/loader command file has\r
-  been processed successfuly in a prior first pass.\r
+  been processed successfully in a prior first pass.\r
 \r
   @param[in] AddPointer        The QEMU_LOADER_ADD_POINTER command to process.\r
 \r

diff --git a/OvmfPkg/Csm/CsmSupportLib/LegacyPlatform.c b/OvmfPkg/Csm/CsmSupportLib/LegacyPlatform.c
index 0ccfa975851829b1b3b9e746efadf7b0fa0e482f..dd75be00f676095c56246460b14d1412b47ec404 100644 (file)
--- a/OvmfPkg/Csm/CsmSupportLib/LegacyPlatform.c
+++ b/OvmfPkg/Csm/CsmSupportLib/LegacyPlatform.c
@@ -256,8 +256,8 @@ GetSelectedVgaDeviceInfo (
   *VgaHandle = NULL;\r
 \r
   //\r
-  // Initialize variable states.  Ths is important for selecting the VGA device\r
-  // if multiple devices exist behind a single bridge.\r
+  // Initialize variable states.  This is important for selecting the VGA\r
+  // device if multiple devices exist behind a single bridge.\r
   //\r
   HandleCount = 0;\r
   HandleBuffer = NULL;\r

diff --git a/OvmfPkg/Library/NvVarsFileLib/FsAccess.c b/OvmfPkg/Library/NvVarsFileLib/FsAccess.c
index 7cc7e68e385ff9fa5ba95162f18cc84ecb0da739..826901fc6b7546c22fd5002bb87873329db19010 100644 (file)
--- a/OvmfPkg/Library/NvVarsFileLib/FsAccess.c
+++ b/OvmfPkg/Library/NvVarsFileLib/FsAccess.c
@@ -184,7 +184,7 @@ FileHandleEmpty (
   @param[in]  ReadSize - The size of data to read from the file\r
 \r
   @return     Pointer to buffer allocated to hold the file\r
-              contents.  NULL if an error occured.\r
+              contents.  NULL if an error occurred.\r
 \r
 **/\r
 VOID*\r
@@ -332,7 +332,7 @@ LoadNvVarsFromFs (
   // We write a variable to indicate we've already loaded the\r
   // variable data.  If it is found, we skip the loading.\r
   //\r
-  // This is relevent if the non-volatile variable have been\r
+  // This is relevant if the non-volatile variable have been\r
   // able to survive a reboot operation.  In that case, we don't\r
   // want to re-load the file as it would overwrite newer changes\r
   // made to the variables.\r

diff --git a/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c b/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
index 87412598f51b38f1c7bf09f193d1952b5a45c9c8..7cd547e70741ce027aa56fa5904bfd1db52caa15 100644 (file)
--- a/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
+++ b/OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
@@ -1255,8 +1255,8 @@ ConnectRecursivelyIfPciMassStorage (
   This notification function is invoked when the\r
   EMU Variable FVB has been changed.\r
 \r
-  @param  Event                 The event that occured\r
-  @param  Context               For EFI compatiblity.  Not used.\r
+  @param  Event                 The event that occurred\r
+  @param  Context               For EFI compatibility.  Not used.\r
 \r
 **/\r
 VOID\r
@@ -1480,8 +1480,8 @@ Routine Description:
   This notification function is invoked when an instance of the\r
   EFI_DEVICE_PATH_PROTOCOL is produced.\r
 \r
-  @param  Event                 The event that occured\r
-  @param  Context               For EFI compatiblity.  Not used.\r
+  @param  Event                 The event that occurred\r
+  @param  Context               For EFI compatibility.  Not used.\r
 \r
 **/\r
 VOID\r

diff --git a/OvmfPkg/PlatformPei/MemDetect.c b/OvmfPkg/PlatformPei/MemDetect.c
index 8f66412763ad7fe37ba6d03bcdb7d133d0aaa396..4863eb101067d29e899f341156f3cea06a0d5bd0 100644 (file)
--- a/OvmfPkg/PlatformPei/MemDetect.c
+++ b/OvmfPkg/PlatformPei/MemDetect.c
@@ -433,7 +433,7 @@ QemuInitializeRam (
     // PEI RAM, in a backup buffer allocated with the normal PEI services.\r
     // CpuMpPei restores the original contents ("returns" the borrowed area) at\r
     // End-of-PEI. End-of-PEI in turn is emitted by S3Resume2Pei before\r
-    // transfering control to the OS's wakeup vector in the FACS.\r
+    // transferring control to the OS's wakeup vector in the FACS.\r
     //\r
     // We expect any other PEIMs that "borrow" memory similarly to CpuMpPei to\r
     // restore the original contents. Furthermore, we expect all such PEIMs\r

diff --git a/OvmfPkg/QemuVideoDxe/VbeShim.c b/OvmfPkg/QemuVideoDxe/VbeShim.c
index 6bb175bfd4443f2c6225bf8c13fb9b95c2e15d57..6a569f62744938d2e38f6ae9239ce4a2a0058267 100644 (file)
--- a/OvmfPkg/QemuVideoDxe/VbeShim.c
+++ b/OvmfPkg/QemuVideoDxe/VbeShim.c
@@ -134,7 +134,7 @@ InstallVbeShim (
   PciWrite8 (Pam1Address, Pam1 | (BIT1 | BIT0));\r
 \r
   //\r
-  // We never added memory space durig PEI or DXE for the C segment, so we\r
+  // We never added memory space during PEI or DXE for the C segment, so we\r
   // don't need to (and can't) allocate from there. Also, guest operating\r
   // systems will see a hole in the UEFI memory map there.\r
   //\r

diff --git a/OvmfPkg/XenBusDxe/EventChannel.c b/OvmfPkg/XenBusDxe/EventChannel.c
index 6a36dca29911103071b92ab287137d501fd6f7d6..490ca58cb4c6c75c51c6f32f41ed005c67d16df9 100644 (file)
--- a/OvmfPkg/XenBusDxe/EventChannel.c
+++ b/OvmfPkg/XenBusDxe/EventChannel.c
@@ -1,7 +1,7 @@
 /** @file\r
   Event Channel function implementation.\r
 \r
-  Event channel are use to notify of an event that happend in a shared\r
+  Event channel are use to notify of an event that happened in a shared\r
   structure for example.\r
 \r
   Copyright (C) 2014, Citrix Ltd.\r

diff --git a/OvmfPkg/XenBusDxe/XenStore.c b/OvmfPkg/XenBusDxe/XenStore.c
index 5757e78b18016a0bc321866857137d7cfb1bd87d..fb00e7393bb10d82585e851a14e7c6c8e7e0f195 100644 (file)
--- a/OvmfPkg/XenBusDxe/XenStore.c
+++ b/OvmfPkg/XenBusDxe/XenStore.c
@@ -10,7 +10,7 @@
 \r
   The XenStore is ASCII string based, and has a structure and semantics\r
   similar to a filesystem.  There are files and directories, the directories\r
-  able to contain files or other directories.  The depth of the hierachy\r
+  able to contain files or other directories.  The depth of the hierarchy\r
   is only limited by the XenStore's maximum path length.\r
 \r
   The communication channel between the XenStore service and other\r

diff --git a/OvmfPkg/XenPvBlkDxe/BlockIo.c b/OvmfPkg/XenPvBlkDxe/BlockIo.c
index ae6aa62ac0d3bb4e4a9977be502f03e987133d44..70bf32cab0160c3e57aaa2748a32be5f4aaef8e2 100644 (file)
--- a/OvmfPkg/XenPvBlkDxe/BlockIo.c
+++ b/OvmfPkg/XenPvBlkDxe/BlockIo.c
@@ -156,7 +156,7 @@ XenPvBlkDxeBlockIoReadWriteBlocks (
     Sector += IoData.Size / 512;\r
     Status = XenPvBlockIo (&IoData, IsWrite);\r
     if (EFI_ERROR (Status)) {\r
-      DEBUG ((EFI_D_ERROR, "XenPvBlkDxe: Error durring %a operation.\n",\r
+      DEBUG ((EFI_D_ERROR, "XenPvBlkDxe: Error during %a operation.\n",\r
               IsWrite ? "write" : "read"));\r
       return Status;\r
     }\r