Skip to content

Commit 7f5c150

Browse files
committed
Fix broken links to WPR
1 parent 6d5fba4 commit 7f5c150

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

hub/apps/trace-processing/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ You can use this package in a console app to list the process command lines cont
7474

7575
In Solution Explorer, right-click on the project and choose Properties. Switch to the Debug tab and enter the path to a trace (.etl file) in Application arguments.
7676

77-
If you do not already have a trace file, you can use [Windows Performance Recorder](/windows-hardware/test/wpt/start-a-recording) to create one.
77+
If you do not already have a trace file, you can use [Windows Performance Recorder](/windows-hardware/test/wpt/windows-performance-recorder) to create one.
7878

7979
3. Run the application.
8080

hub/apps/trace-processing/tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.topic: tutorial
1313

1414
Microsoft.Windows.EventTracing.Processing.All
1515

16-
This package allows you to access data in a trace file. If you do not already have a trace file, you can use [Windows Performance Recorder](/windows-hardware/test/wpt/start-a-recording) to create one.
16+
This package allows you to access data in a trace file. If you do not already have a trace file, you can use [Windows Performance Recorder](/windows-hardware/test/wpt/windows-performance-recorder) to create one.
1717

1818
The following example console app shows how to access the command lines of all processes contained in the trace:
1919

0 commit comments

Comments
 (0)