summaryrefslogtreecommitdiff
path: root/general/tracing/SystemTraceControl
diff options
context:
space:
mode:
authorDen Delimarsky <[email protected]>2019-03-13 19:15:06 -0700
committerDen Delimarsky <[email protected]>2019-03-13 19:15:06 -0700
commitdbc7785c3a7ced56ecac6b5a9dfb81ef45dedac6 (patch)
tree2a8e1a39358b66cc2bc0d85e163956aafd5ccd16 /general/tracing/SystemTraceControl
parentffeacc14932f98db4e7926825909a37d2b6d332f (diff)
Update manifests
Diffstat (limited to 'general/tracing/SystemTraceControl')
-rw-r--r--general/tracing/SystemTraceControl/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/general/tracing/SystemTraceControl/README.md b/general/tracing/SystemTraceControl/README.md
index a1a18c9c..437f194c 100644
--- a/general/tracing/SystemTraceControl/README.md
+++ b/general/tracing/SystemTraceControl/README.md
@@ -24,4 +24,4 @@ The sample code provided shows how to start an [Event Tracing](http://msdn.micro
You can process the Systemtrace.etl file using Tracerpt.exe, a command-line trace tool included in Windows that formats trace events. It also analyzes the events and generates summary reports. For more information about how to use this tool, see [Tracerpt](http://go.microsoft.com/fwlink/p/?linkid=179389) topic on the TechNet website.
-You can also process the file using the [Windows Performance Toolkit](http://go.microsoft.com/fwlink/p/?linkid=250774) (WPT), which is available in the SDK.
+You can also process the file using the [Windows Performance Toolkit](http://go.microsoft.com/fwlink/p/?linkid=250774) (WPT), which is available in the SDK. \ No newline at end of file