Improve titles

docs/core/diagnostics/tutorial/app_is_leaking_memory_eventual_crash.md

@@ -1,11 +1,11 @@
 ---
-title:
-description:
+title: Debugging a memory leak - .NET Core
+description: A tutorial walk-through, debugging a memory leak in .NET Core.
 author: sdmaclea
 ms.author: stmaclea
 ms.date: 08/27/2019
 ---
-# App is leaking memory (eventual crash/hang)
+# Debugging a memory leak
 
 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.
 

docs/core/diagnostics/tutorial/app_running_slow_highcpu.md

@@ -1,11 +1,11 @@
 ---
-title:
-description:
+title: Debugging high CPU usage - .NET Core
+description: A tutorial walk-through, debugging high CPU usage in .NET Core.
 author: sdmaclea
 ms.author: stmaclea
 ms.date: 08/27/2019
 ---
-# App is running slow with high CPU usage
+# Debugging high CPU usage
 
 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.
 

docs/core/diagnostics/tutorial/diagnostic-scenarios.md

@@ -1,5 +1,5 @@
 ---
-title: Diagnostics walk throughs - .NET Core
+title: Diagnostics walk-throughs - .NET Core
 description:
 author: sdmaclea
 ms.author: stmaclea
@@ -12,7 +12,7 @@ ms.topic: overview
 .NET Core has a wide range of diagnostics capabilities. To learn more about production diagnostics in .NET Core 3, we'll run through a set of diagnostics scenarios using the `dotnet` tools.
 
 > [!NOTE]
-> The walkthroughs were all run on Ubuntu 16.04 and using the .NET Core 3 preview 5 bits.
+> The walk-throughs were all run on Ubuntu 16.04 and using the .NET Core 3 preview 5 bits.
 >
 > The tools/APIs that are used are based on preview 5 and are subject to change. The tutorial will be updated to account for later previews and final release
 >
@@ -37,12 +37,12 @@ Each of the scenarios:
 
 ### Debugging a memory leak
 
-[Scenario - App is leaking memory](app_is_leaking_memory_eventual_crash.md) walks through finding a memory leak. The [dotnet-counters](../cli-tools/dotnet-counters.md) tool is used to confirm the leak. Then the [dotnet-dump](../cli-tools/dotnet-dump.md) tool is used to diagnose the leak.
+[Debugging a memory leak](app_is_leaking_memory_eventual_crash.md) walks through finding a memory leak. The [dotnet-counters](../cli-tools/dotnet-counters.md) tool is used to confirm the leak. Then the [dotnet-dump](../cli-tools/dotnet-dump.md) tool is used to diagnose the leak.
 
 ### Debugging high CPU usage
 
-[Scenario - App is running slow](app_running_slow_highcpu.md) walks through investigating high CPU usage. It uses the [dotnet-counters](../cli-tools/dotnet-counters.md) tool to confirm the high CPU usage. It then walks through using [Trace for performance analysis utility (`dotnet-trace`)](../cli-tools/dotnet-trace.md) or Linux `perf` to collect and view CPU usage profile.
+[Debugging high CPU usage](app_running_slow_highcpu.md) walks through investigating high CPU usage. It uses the [dotnet-counters](../cli-tools/dotnet-counters.md) tool to confirm the high CPU usage. It then walks through using [Trace for performance analysis utility (`dotnet-trace`)](../cli-tools/dotnet-trace.md) or Linux `perf` to collect and view CPU usage profile.
 
 ### Debugging deadlock
 
-The [Scenario - App is hanging](hung_app.md) tutorial explores using the [dotnet-dump](../cli-tools/dotnet-dump.md) tool to investigate threads and locks.
+The [debugging deadlock](hung_app.md) tutorial explores using the [dotnet-dump](../cli-tools/dotnet-dump.md) tool to investigate threads and locks.

docs/core/diagnostics/tutorial/hung_app.md

@@ -1,11 +1,11 @@
 ---
-title:
-description:
+title: Debugging deadlock - .NET Core
+description: A tutorial walk-through, debugging locking issues in .NET Core.
 author: sdmaclea
 ms.author: stmaclea
 ms.date: 08/27/2019
 ---
-# App is hanging
+# Debugging deadlock
 
 In this scenario, the endpoint will experience a hang and thread accumulation. We'll show how you can use the existing tools to analyze the problem.