\r
According to a file GUID, check a Fv file device path is valid. If it is invalid,\r
try to return the valid device path.\r
- FV address maybe changes for memory layout adjust from time to time, use this funciton\r
+ FV address maybe changes for memory layout adjust from time to time, use this function\r
could promise the Fv file device path is right.\r
\r
@param DevicePath On input, the FV file device path to check\r
If Binding protocol is not found, it is set to NULL. \r
\r
@return Pointer into the Binding Protocol interface\r
- @retval NULL The paramter is not valid or the binding protocol is not found.\r
+ @retval NULL The parameter is not valid or the binding protocol is not found.\r
\r
**/\r
EFI_DRIVER_BINDING_PROTOCOL *\r
//\r
if (CheckExistInStack (OverrideItem->ControllerDevicePath)) {\r
//\r
- // There is a dependecy dead loop if the ControllerDevicePath appear in stack twice\r
+ // There is a dependency dead loop if the ControllerDevicePath appear in stack twice\r
//\r
return EFI_UNSUPPORTED;\r
}\r
// If the image device path contains an FV node, check the FV file device path is valid.\r
// If it is invalid, try to return the valid device path.\r
// FV address maybe changes for memory layout adjust from time to time,\r
- // use this funciton could promise the FV file device path is right.\r
+ // use this function could promise the FV file device path is right.\r
//\r
Status = UpdateFvFileDevicePath (&TempDriverImagePath, NULL, CallerImageHandle);\r
if (!EFI_ERROR (Status)) {\r