Fix second round of PR review feedback

- Restore missing H1 headings in create-winrt-component-winui-cswinrt.md
  and create-windows-runtime-component-cswinrt.md (were lost during
  front-matter repair)
- Update .NET 6.0 SDK prereqs to .NET 8.0 SDK (LTS) or later, and fix
  links to point to generic download page instead of version-specific
  .NET 6 page, in all three walkthrough files

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/develop/platform/csharp-winrt/create-windows-runtime-component-cswinrt.md

@@ -6,6 +6,8 @@ ms.topic: article
 ms.localizationpriority: medium
 ---
 
+# Walkthrough—Create a C#/WinRT component, and consume it from C++/WinRT
+
 C#/WinRT enables developers using .NET to author their own Windows Runtime components in C# using a class library project. Authored components can be consumed in native desktop applications as a package reference or as a project reference with a few modifications.
 
 This walkthrough demonstrates how to create a simple Windows Runtime component using C#/WinRT, distribute the component as a NuGet package, and consume the component from a C++/WinRT console application. For the full sample that provides the code for this article, see the [C#/WinRT authoring sample](https://github.com/microsoft/CsWinRT/tree/master/src/Samples/AuthoringDemo). For more details about authoring, see [Authoring components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md).
@@ -17,7 +19,7 @@ For a walkthrough on authoring WinUI 3 controls with C#/WinRT specifically for u
 This walkthrough requires the following tools and components:
 
 - [Visual Studio 2022 or later](/visualstudio/releases/2022/release-notes)
-- [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet) or later
+- [.NET 8.0 SDK (LTS)](https://dotnet.microsoft.com/download) or later
 - [C++/WinRT VSIX](https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264) for C++/WinRT project templates
 
 ## Create a simple Windows Runtime Component using C#/WinRT

hub/apps/develop/platform/csharp-winrt/create-winrt-component-winui-cswinrt.md

@@ -6,6 +6,8 @@ ms.topic: article
 ms.localizationpriority: medium
 ---
 
+# Walkthrough—Create a C# component with WinUI 3 controls, and consume it from a C++/WinRT app that uses the Windows App SDK
+
 C#/WinRT provides support for authoring Windows Runtime components, including WinUI custom types and custom controls. These components can be consumed from either C# or C++/WinRT applications that use the Windows App SDK. We recommend using C#/WinRT v1.6.4 or later to author runtime components with NuGet packaging support.
 
 For more details about the supported scenarios, refer to [Authoring C#/WinRT components](https://github.com/microsoft/CsWinRT/blob/master/docs/authoring.md) in the C#/WinRT GitHub repo.
@@ -17,7 +19,7 @@ This walkthrough demonstrates how to author a C# component with a custom WinUI c
 This walkthrough requires the following tools and components:
 
 - [Visual Studio 2022 or later](/visualstudio/releases/2022/release-notes)
-- [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or later
+- [.NET 8.0 SDK (LTS)](https://dotnet.microsoft.com/download) or later
 - [Windows App SDK VSIX](../../../windows-app-sdk/downloads.md) (1.1 from the stable channel)
 
 ## Author your C#/WinRT component using the Windows App SDK

hub/apps/develop/platform/csharp-winrt/net-projection-from-cppwinrt-component.md

@@ -22,7 +22,7 @@ In .NET 6 and later, consumption of Windows metadata (WinMD) files is no longer
 This walkthrough and the corresponding sample require the following tools and components:
 
 * [Visual Studio 2022 or later](https://visualstudio.microsoft.com/downloads/) with the Universal Windows Platform development workload installed. In **Installation Details** > **Universal Windows Platform development**, check the **C++ (v14x) Universal Windows Platform tools** option.
-* [.NET 6.0 SDK](https://dotnet.microsoft.com/download/) or later.
+* [.NET 8.0 SDK (LTS)](https://dotnet.microsoft.com/download) or later.
 
 We'll be using Visual Studio 2022 or later and .NET 8 in this walkthrough.