EventPipeProfiler doc improvements (#1419)

Author: WojciechNagorski

docs/articles/features/event-pipe-profiler.md

@@ -5,7 +5,7 @@ name: EventPipeProfiler
 
 # EventPipeProfiler
 
-`EventPipeProfiler` is a cross-platform profiler that allows profile .NET code on every platform - Windows, Linux, macOS. Collected data are exported to trace files (`.speedscope.json` and `.nettrace`) which can be analyzed using [SpeedScope](https://www.speedscope.app/), [PerfView](https://github.com/Microsoft/perfview), and [Windows Performance Analyzer](https://docs.microsoft.com/en-us/windows-hardware/test/wpt/windows-performance-analyzer). This new profiler is available from the 0.12.1 version.
+`EventPipeProfiler` is a cross-platform profiler that allows profile .NET code on every platform - Windows, Linux, macOS. Collected data are exported to trace files (`.speedscope.json` and `.nettrace`) which can be analyzed using [SpeedScope](https://www.speedscope.app/), [PerfView](https://github.com/Microsoft/perfview), and [Visual Studio Profiler](https://docs.microsoft.com/en-us/visualstudio/profiling/profiling-feature-tour). This new profiler is available from the 0.12.1 version.
 
 ![](https://wojciechnagorski.com/images/EventPipeProfiler/SpeedScopeAdvance.png)
 

docs/articles/samples/IntroEventPipeProfilerAdvanced.md

@@ -5,7 +5,7 @@ uid: BenchmarkDotNet.Samples.IntroEventPipeProfilerAdvanced
 ## Sample: EventPipeProfilerAdvanced
 
 The most advanced and powerful way to use `EventPipeProfiler` is a custom configuration. As you can see the below configuration adds `EventPipeProfiler` that constructor can take the profile and/or a list of providers. 
-Both `EventPipeProfiler` and `dotnet trace` use the `Microsoft.Diagnostics.NETCore.Client` package internally. So before you start using the custom configuration of this profiler, it is worth reading the documentation [here](https://github.com/dotnet/diagnostics/blob/master/documentation/dotnet-trace-instructions.md) and [here](https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace#dotnet-trace-collect) where you can fine more information about how to configure provider list.
+Both `EventPipeProfiler` and `dotnet trace` use the `Microsoft.Diagnostics.NETCore.Client` package internally. So before you start using the custom configuration of this profiler, it is worth reading the documentation [here](https://github.com/dotnet/diagnostics/blob/master/documentation/dotnet-trace-instructions.md) and [here](https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace#dotnet-trace-collect) where you can find more information about how to configure provider list.
 
 ### Source code