NetworkPkg/Ip4Dxe: Fix various typos

[mirror_edk2.git] / NetworkPkg / Ip4Dxe / Ip4Driver.c

diff --git a/NetworkPkg/Ip4Dxe/Ip4Driver.c b/NetworkPkg/Ip4Dxe/Ip4Driver.c
index 62be8b681a18b9d22a5a4de65564a88c3e4e6e9f..7fed659ca101d90708674030b422e9529d4ec214 100644 (file)
--- a/NetworkPkg/Ip4Dxe/Ip4Driver.c
+++ b/NetworkPkg/Ip4Dxe/Ip4Driver.c
@@ -581,7 +581,7 @@ Ip4DriverBindingStart (
   Ip4Cfg2  = &IpSb->Ip4Config2Instance.Ip4Config2;\r
 \r
   //\r
-  // Install the Ip4ServiceBinding Protocol onto ControlerHandle\r
+  // Install the Ip4ServiceBinding Protocol onto ControllerHandle\r
   //\r
   Status = gBS->InstallMultipleProtocolInterfaces (\r
                   &ControllerHandle,\r
@@ -829,7 +829,7 @@ ON_ERROR:
                       then a new handle is created. If it is a pointer to an existing UEFI handle,\r
                       then the protocol is added to the existing UEFI handle.\r
 \r
-  @retval EFI_SUCCES            The protocol was added to ChildHandle.\r
+  @retval EFI_SUCCESS           The protocol was added to ChildHandle.\r
   @retval EFI_INVALID_PARAMETER ChildHandle is NULL.\r
   @retval EFI_OUT_OF_RESOURCES  There are not enough resources available to create\r
                                 the child\r
@@ -933,7 +933,7 @@ ON_ERROR:
   @param  This        Pointer to the EFI_SERVICE_BINDING_PROTOCOL instance.\r
   @param  ChildHandle Handle of the child to destroy\r
 \r
-  @retval EFI_SUCCES            The protocol was removed from ChildHandle.\r
+  @retval EFI_SUCCESS           The protocol was removed from ChildHandle.\r
   @retval EFI_UNSUPPORTED       ChildHandle does not support the protocol that is being removed.\r
   @retval EFI_INVALID_PARAMETER Child handle is NULL.\r
   @retval EFI_ACCESS_DENIED     The protocol could not be removed from the ChildHandle\r
@@ -1020,14 +1020,14 @@ Ip4ServiceBindingDestroyChild (
   // Uninstall the IP4 protocol first. Many thing happens during\r
   // this:\r
   // 1. The consumer of the IP4 protocol will be stopped if it\r
-  // opens the protocol BY_DRIVER. For eaxmple, if MNP driver is\r
+  // opens the protocol BY_DRIVER. For example, if MNP driver is\r
   // stopped, IP driver's stop function will be called, and uninstall\r
   // EFI_IP4_PROTOCOL will trigger the UDP's stop function. This\r
   // makes it possible to create the network stack bottom up, and\r
   // stop it top down.\r
   // 2. the upper layer will recycle the received packet. The recycle\r
   // event's TPL is higher than this function. The recycle events\r
-  // will be called back before preceeding. If any packets not recycled,\r
+  // will be called back before preceding. If any packets not recycled,\r
   // that means there is a resource leak.\r
   //\r
   gBS->RestoreTPL (OldTpl);\r