the Event is NULL.\r
@retval EFI_WRITE_PROTECTED The device can not be written to.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
- @retval EFI_MEDIA_CHNAGED The MediaId does not matched the current device.\r
+ @retval EFI_MEDIA_CHANGED The MediaId does not match the current device.\r
@retval EFI_DEVICE_ERROR The device reported an error while performing the write.\r
@retval EFI_BAD_BUFFER_SIZE The Buffer was not a multiple of the block size of the device.\r
@retval EFI_INVALID_PARAMETER The write request contains LBAs that are not valid,\r
@retval EFI_SUCCESS The flush request was queued if Event is not NULL.\r
All outstanding data was written correctly to the\r
device if the Event is NULL.\r
- @retval EFI_DEVICE_ERROR The device reported an error while writting back\r
+ @retval EFI_DEVICE_ERROR The device reported an error while writing back\r
the data.\r
@retval EFI_WRITE_PROTECTED The device cannot be written to.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
If FileName contains only a single L'\', return TRUE.\r
If FileName contains two adjacent L'\', return FALSE.\r
If FileName conatins L'/' , return FALSE.\r
- If FielName contains more than two dots seperated with other FileName characters\r
+ If FileName contains more than two dots separated with other FileName characters\r
by L'\', return FALSE. For example, L'.\...\filename.txt' is invalid path name. But L'..TwoDots\filename.txt' is valid path name.\r
\r
@param FileName The File Name String to check.\r
UINT32 Width;\r
UINT32 Height;\r
//\r
- // This screen is used to redraw the scree when windows events happen. It's\r
+ // This screen is used to redraw the screen when windows events happen. It's\r
// updated in the main thread and displayed in the windows thread.\r
//\r
BITMAPV4HEADER *VirtualScreenInfo;\r
\r
Routine Description:\r
Reads the next keystroke from the input device. The WaitForKey Event can\r
- be used to test for existance of a keystroke via WaitForEvent () call.\r
+ be used to test for existence of a keystroke via WaitForEvent () call.\r
\r
Arguments:\r
Private - The private structure of WinNt Gop device.\r
\r
Returns:\r
EFI_SUCCESS - The keystroke information was returned.\r
- EFI_NOT_READY - There was no keystroke data availiable.\r
+ EFI_NOT_READY - There was no keystroke data available.\r
EFI_DEVICE_ERROR - The keystroke information was not returned due to\r
hardware errors.\r
EFI_INVALID_PARAMETER - KeyData is NULL.\r
@param X X location on graphics screen.\r
@param Y Y location on the graphics screen.\r
@param Width Width of BltBuffer.\r
- @param Height Hight of BltBuffer\r
+ @param Height Height of BltBuffer\r
@param BltOperation Operation to perform on BltBuffer and video memory\r
@param BltBuffer Buffer containing data to blt into video buffer.\r
This buffer has a size of\r
\r
@retval EFI_SUCCESS The palette is updated with PaletteArray.\r
@retval EFI_INVALID_PARAMETER BltOperation is not valid.\r
- @retval EFI_DEVICE_ERROR A hardware error occured writting to the video\r
+ @retval EFI_DEVICE_ERROR A hardware error occurred writing to the video\r
buffer.\r
\r
**/\r
\r
\r
/**\r
- This thread simulates the end of WinMain () aplication. Each Winow nededs\r
- to process it's events. The messages are dispatched to\r
+ This thread simulates the end of WinMain () application. Each Window needs\r
+ to process its events. The messages are dispatched to\r
WinNtGopThreadWindowProc ().\r
- Be very careful sine WinNtGopThreadWinMain () and WinNtGopThreadWindowProc ()\r
- are running in a seperate thread. We have to do this to process the events.\r
+ Be very careful since WinNtGopThreadWinMain () and WinNtGopThreadWindowProc ()\r
+ are running in a separate thread. We have to do this to process the events.\r
\r
@param lpParameter Handle of window to manage.\r
\r
);\r
\r
//\r
- // The reset of this thread is the standard winows program. We need a sperate\r
+ // The reset of this thread is the standard windows program. We need a separate\r
// thread since we must process the message loop to make windows act like\r
// windows.\r
//\r
NT_FD_INFO *gFdInfo;\r
\r
//\r
-// Array that supports seperate memory rantes.\r
+// Array that supports separate memory ranges.\r
// The memory ranges are set by PcdWinNtMemorySizeForSecMain.\r
// The number of array elements is allocated base on parsing\r
// PcdWinNtMemorySizeForSecMain value and the memory is never freed.\r
\r
Routine Description:\r
Return the FD Size and base address. Since the FD is loaded from a\r
- file into host memory only the SEC will know it's address.\r
+ file into host memory only the SEC will know its address.\r
\r
Arguments:\r
Index - Which FD, starts at zero.\r
Returns:\r
EFI_SUCCESS - The file was opened and mapped.\r
EFI_NOT_FOUND - FileName was not found in the current directory\r
- EFI_DEVICE_ERROR - An error occured attempting to map the opened file\r
+ EFI_DEVICE_ERROR - An error occurred attempting to map the opened file\r
\r
--*/\r
{\r
SecCorePe32File - SEC Core PE32\r
\r
Returns:\r
- Success means control is transfered and thus we should never return\r
+ Success means control is transferred and thus we should never return\r
\r
--*/\r
{\r
// the *.dll file as a library using Windows* APIs. This allows\r
// source level debug. The image is still loaded and relocated\r
// in the Framework memory space like on a real system (by the code above),\r
- // but the entry point points into the DLL loaded by the code bellow.\r
+ // but the entry point points into the DLL loaded by the code below.\r
//\r
\r
DllEntryPoint = NULL;\r
SecCorePe32File - SEC Core PE32\r
\r
Returns:\r
- Success means control is transfered and thus we should never return\r
+ Success means control is transferred and thus we should never return\r
\r
--*/\r
;\r