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>

SourceLevelDebugPkg/Library/DebugCommunicationLibUsb3/DebugCommunicationLibUsb3Common.c

@@ -300,7 +300,7 @@ Done:
   Check if it needs to re-initialize usb debug port hardware.
 
   During different phases switch, such as SEC to PEI or PEI to DXE or DXE to SMM, we should check
-  whether the usb debug port hardware configuration is changed. Such case can be triggerred by
+  whether the usb debug port hardware configuration is changed. Such case can be triggered by
   Pci bus resource allocation and so on.
 
   @param  Handle           Debug port handle.
@@ -989,7 +989,7 @@ DebugPortPollBuffer (
 /**
   Initialize the debug port.
 
-  If Function is not NULL, Debug Communication Libary will call this function
+  If Function is not NULL, Debug Communication Library will call this function
   by passing in the Context to be the first parameter. If needed, Debug Communication
   Library will create one debug port handle to be the second argument passing in
   calling the Function, otherwise it will pass NULL to be the second argument of
@@ -997,7 +997,7 @@ DebugPortPollBuffer (
 
   If Function is NULL, and Context is not NULL, the Debug Communication Library could
     a) Return the same handle as passed in (as Context parameter).
-    b) Ignore the input Context parameter and create new hanlde to be returned.
+    b) Ignore the input Context parameter and create new handle to be returned.
 
   If parameter Function is NULL and Context is NULL, Debug Communication Library could
   created a new handle if needed and return it, otherwise it will return NULL.