Refine wording in SourceLevelDebugPkg/Readme.txt.

Signed-off-by: niruiyu
Reviewed-by: vanjeff
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@12857 6f19259b-4bc3-4df7-8a09-765794883524

diff --git a/SourceLevelDebugPkg/Readme.txt b/SourceLevelDebugPkg/Readme.txt
index a1a2ffe18df690833d0123cbc2da920efb12b409..7dcd6d538b0365301def4cc56c6397cf39d5d135 100644 (file)
--- a/SourceLevelDebugPkg/Readme.txt
+++ b/SourceLevelDebugPkg/Readme.txt
@@ -1,16 +1,14 @@
-UDK based firmware on UEFI IA-32 and UEFI x64 platforms may be debugged using \r
-Microsoft(R) Debugging Tools for Windows(R) (WinDbg). Debug capability is enabled\r
-with SourceLevelDebugPkg in conjunction with the Intel(R) UEFI Development Kit \r
-Debugger Tool (Intel(R) UDK Debugger Tool).\r
+UDK based firmware on UEFI IA-32 and UEFI x64 platforms can be debugged with\r
+SourceLevelDebugPkg in conjunction with Intel(R) UEFI Development Kit Debugger\r
+Tool (Intel (R) UDK Debugger Tool).\r

 \r
 \r

-The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:\r
-http://www.intel.com/technology/efi. \r
+The Intel(R) UDK Debugger Tool and its detailed user manual can be obtained\r
+from: http://www.intel.com/technology/efi.\r

 \r
 \r

-NOTE: In addition to the known issues listed in the user manual, the following \r
+NOTE: In addition to the known issues listed in the user manual, the following\r

 anomalies have been observed:\r
 \r
 anomalies have been observed:\r
 \r

-1) When using a USB debug cable, after the TARGET completes a reset during memory\r
-   initialization, the connection between the HOST and the TARGET may be lost \r
-   (e.g. WinDbg reports busy status and does not respond to a break request). A \r
-   work around for this issue is to unplug the USB debug cable and then plug the\r
-   cable back in. A new debug session may then be started.\r
+1) When using a USB debug cable, after the TARGET completes a reset during\r
+   memory initialization, the connection between the HOST and the TARGET may be\r
+   lost. A work around for this issue is to unplug the USB debug cable and then\r
+   plug the cable back in. A new debug session can then be started.\r