SourceLevelDebugPkg: Fix typos in comments

- descrption -> description
- Libary -> Library
- funciton -> function
- paramter -> parameter
- triggerred -> triggered
- hanlde -> handle

Cc: Jeff Fan <jeff.fan@intel.com>
Cc: Hao Wu <hao.a.wu@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Gary Lin <glin@suse.com>
Reviewed-by: Hao Wu <hao.a.wu@intel.com>
Reviewed-by: Jeff Fan <jeff.fan@intel.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/SourceLevelDebugPkg/Library/DebugCommunicationLibSerialPort/DebugCommunicationLibSerialPort.c b/SourceLevelDebugPkg/Library/DebugCommunicationLibSerialPort/DebugCommunicationLibSerialPort.c
index 388286b406..6a854ff2a2 100644
--- a/SourceLevelDebugPkg/Library/DebugCommunicationLibSerialPort/DebugCommunicationLibSerialPort.c
+++ b/SourceLevelDebugPkg/Library/DebugCommunicationLibSerialPort/DebugCommunicationLibSerialPort.c
@@ -26,9 +26,9 @@
   stack, this function must work on the mode that doesn't return to the caller, then

   the caller needs to wrap up all rest of logic after DebugPortInitialize() into one

   function and pass it into DebugPortInitialize(). DebugPortInitialize() is

-  responsible to invoke the passing-in funciton at the end of DebugPortInitialize().

+  responsible to invoke the passing-in function at the end of DebugPortInitialize().

 

-  If the paramter Function is not NULL, Debug Communication Libary instance will

+  If the parameter Function is not NULL, Debug Communication Library instance will

   invoke it by passing in the Context to be the first parameter. Debug Communication

   Library instance could create one debug port handle to be the second parameter

   passing into the Function. Debug Communication Library instance also could pass