Applies to check

dotnet · Oct 17, 2019 · 6b81f02 · 6b81f02
1 parent 04a00d8
commit 6b81f02
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/core/diagnostics/app_is_leaking_memory_eventual_crash.md b/docs/core/diagnostics/app_is_leaking_memory_eventual_crash.md
@@ -7,7 +7,7 @@ ms.date: 10/14/2019
 ---
 # Debugging a memory leak
 
-**This article applies to:** .NET Core 3.0 SDK and later versions
+**This article applies to: ✓** .NET Core 3.0 SDK and later versions
 
 In this scenario, the endpoint will slowly start leaking memory and eventually will result in an out of memory exception. To diagnose this scenario, we need several key pieces of diagnostics data.
 

diff --git a/docs/core/diagnostics/app_running_slow_highcpu.md b/docs/core/diagnostics/app_running_slow_highcpu.md
@@ -7,7 +7,7 @@ ms.date: 10/14/2019
 ---
 # Debugging high CPU usage
 
-**This article applies to:** .NET Core 3.0 SDK and later versions
+**This article applies to: ✓** .NET Core 3.0 SDK and later versions
 
 In this scenario, the [sample debug target](sample-debug-target.md) will consume excessive CPU. To diagnose this scenario, we need several key pieces of diagnostics data.
 

diff --git a/docs/core/diagnostics/dotnet-trace.md b/docs/core/diagnostics/dotnet-trace.md
@@ -7,7 +7,7 @@ ms.date: 10/14/2019
 ---
 # Trace for performance analysis utility (`dotnet-trace`)
 
-**This article applies to:** .NET Core 3.0 SDK and later versions
+**This article applies to: ✓** .NET Core 3.0 SDK and later versions
 
 ## Installing `dotnet-trace`
 

diff --git a/docs/core/diagnostics/hung_app.md b/docs/core/diagnostics/hung_app.md
@@ -7,7 +7,7 @@ ms.date: 10/14/2019
 ---
 # Debugging deadlock
 
-**This article applies to:** .NET Core 3.0 SDK and later versions
+**This article applies to: ✓** .NET Core 3.0 SDK and later versions
 
 In this scenario, the endpoint will experience a hang and thread accumulation. We'll show how you can use the tools to analyze the problem.