-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
-The Intel(R) UDK Debugger Tool and its detailed user manual may be obtained from:\r
-http://www.intel.com/technology/efi. \r
-\r
-NOTE: In addition to the known issues listed in the user manual, the following \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
+The Intel(R) UDK Debugger Tool and its detailed user manual can be obtained\r
+from: https://firmware.intel.com/develop/intel-uefi-tools-and-utilities/intel-uefi-development-kit-debugger-tool.\r