Update release notes for Preview 7: add missing WPF entry, fix formatting in ASP.NET Core, SDK, and Windows Forms notes

Author: jamesmontemagno

.github/prompts/createprs-for-preview.prompt.md

@@ -39,4 +39,4 @@ Here are the files you need to do this one at a time for:
 - sdk.md
 - visualbasic.md
 - winforms.md
-- wpf.md
+- wpf.md

.github/prompts/scaffoldpreview.prompt.md

@@ -21,4 +21,4 @@ ASP.NET Core updates in .NET 10:
 
 Something about the feature
 
-```
+```

release-notes/10.0/preview/preview7/aspnetcore.md

@@ -120,6 +120,7 @@ else { /* ... */ }
 ```
 
 To sign in with a passkey, use `SignInManager.PasskeySignInAsync()`:
+
 ```csharp
 // 'credentialJson' is the JSON-serialized result from `navigator.credentials.get()`.
 var result = await signInManager.PasskeySignInAsync(credentialJson);

release-notes/10.0/preview/preview7/sdk.md

@@ -33,4 +33,4 @@ platform-specific .NET Tools work this way, you only need to add one thing to yo
 
 This RuntimeIdentifier is at the 'root' of our platform-compatibility checking, and since it declares support for, well, _any_ platform, the tool that we package for you will be the most compatible kind of tool - a framework-dependent, platform-agnostic .NET dll, which requires a compatible .NET Runtime in order to execute. When you perform a `dotnet pack` to create your tool, you'll see a new package for the `any` RuntimeIdentifier appear alongside the other platform-specific packages and the top-level manifest package.
 
-The eagle-eyed among you will note that this is the exact same kind of tool that you would make in .NET 9 and earlier, but now it fits into the overall goal of enabling platform-specific .NET Tools!
+The eagle-eyed among you will note that this is the exact same kind of tool that you would make in .NET 9 and earlier, but now it fits into the overall goal of enabling platform-specific .NET Tools!

release-notes/10.0/preview/preview7/winforms.md

@@ -1,17 +1,18 @@
-# WindowsWe've alsWe've also improved the rendering of special buttons within the PropertyGrid for dark mode. Previously, the ellipsis button used to open an editor and the drop-down button for ComboBox-type editors were not rendering well in dark mode. Now, these elements have dedicated renderers ensuring they appear consistently and at the same quality as the rest of the UI in dark mode.
+# Windows Forms in .NET 10 Preview 7 - Release Notes
 
-Everything mentioned above pertains specifically to dark mode improvements in Preview 7. Other functionalities remain unchanged in this release.ddressed the RichTextBox background issue in dark mode. Previously, a disabled RichTextBox would show a white background. Now it correctly displays the dark mode background. However, there's a known limitation: if the RichTextBox has formatted content, only the first few visible lines will appear correctly, and the formatting might not fully apply in the disabled state.
+Here's a summary of what's new in Windows Forms in this preview release:
 
-As a temporary workaround, if maintaining full formatting in a disabled RichTextBox is essential, we recommend setting it to read-only and manually disabling selections. This helps achieve a better preview until a more permanent fix is available. Note that this limitation is due to the underlying RichTextBox control in the common controls library, and a full fix may require a future version update.
+- [ComboBox Dark Mode Rendering Fix](#combobox-dark-mode-rendering-fix)
+- [RichTextBox Dark Mode Improvement and Known Limitation](#richtextbox-dark-mode-improvement-and-known-limitation)
+- [PropertyGrid Dark Mode Enhancements](#propertygrid-dark-mode-enhancements)
 
-## PropertyGrid Dark Mode Enhancementss in .NET 10 Preview 7 - Release Notes
+Windows Forms updates in .NET 10:
 
-Here's a summary of what's new in Windows Forms in this preview release:
+- [What's new in Windows Forms](https://learn.microsoft.com/dotnet/desktop/winforms/whats-new/) documentation
 
 ## ComboBox Dark Mode Rendering Fix
-
 In this update, we've resolved an issue where a disabled ComboBox displayed a white background instead of the appropriate dark mode color scheme. Now, regardless of whether the ComboBox is in editable, list, or simple mode, its constituent controls will correctly render with the proper dark mode background when disabled.
-
+ 
 ## RichTextBox Dark Mode Improvement and Known Limitation
 We’ve also addressed the RichTextBox background issue in dark mode. Previously, a disabled RichTextBox would show a white background. Now it correctly displays the dark mode background. However, there's a known limitation: if the RichTextBox has formatted content, only the first few visible lines will appear correctly, and the formatting might not fully apply in the disabled state.