More suggestion added and clean up.

Author: wadepickett

.github/copilot-instructions.md

@@ -1,17 +1,15 @@
 ---
 author: wadepickett
 ms.author: wpickett
-ms.date: 07-28-2025
+ms.date: 07-29-2025
 ---
 
 # Copilot Instructions for `dotnet/AspNetCore.Docs`
 
 ## Introduction
-
 This document contains repository-specific instructions for GitHub Copilot when assisting with the `dotnet/AspNetCore.Docs` repository. **Unless otherwise specified, all ".NET" references refer to modern .NET, not .NET Framework.**
 
 ## Repository-Specific Guidelines
-
 - Follow the [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/)
 - **Repository Exceptions**:
   - Number ordered lists as "1." for every item (don't use sequential numbers)
@@ -25,46 +23,28 @@ This document contains repository-specific instructions for GitHub Copilot when
 
 ## Version Targeting
 
-### Detection Priority Order
-1. **Explicit PR/Issue Instructions** - Prioritize explicit version ranges mentioned
-2. **File Metadata** - Check YAML frontmatter for specifications
-3. **Inline Moniker Tags** - Look for version range specifications
-4. **Repository Branch Context** - Consider branch where PR will be merged
-5. **Directory Structure** - Check for version-specific directories
-
 ### Common Range Patterns
 - Fixed Range: `>= aspnetcore-7.0 <= aspnetcore-9.0`
 - Open Upper Bound: `>= aspnetcore-7.0`
 - Open Lower Bound: `<= aspnetcore-9.0`
 - Specific Version: `== aspnetcore-9.0`
 
 ## API References and Verification
-
 - Never guess API documentation IDs, always verify. If unable to verfy, say so.
 - Check if features were introduced after .NET Core 3.1
 - Default to most compatible syntax when uncertain
-- For breaking changes, check:
-  - Changes to default behavior of existing APIs
-  - Removed or renamed public API elements
-  - Modified method signatures or return types
-  - Changed serialization formats
-  - Altered dependency requirements
-  - Changes to configuration schema
 
 ## Links and References
-
 - Use relative links for files within this repo
 - When adding external links into a document, strip out the language/culture segment of the URL if present (example: remove the `en-us` or `en` part of links to English versions of webpages)
 - For learn.microsoft.com links, remove `https://learn.microsoft.com/en-us` from URLs
 - Use cross-references for APIs: `<xref:api-doc-ID>`
 - Get doc ID from the relevant XML doc in dotnet-api-docs, and omit the first two characters of the doc ID
 
 ## Markdown File Naming and Organization
-
 - If you're adding a new Markdown file, it should be named in all lowercase with hyphens separating words. Also, omit any filler words such as "the" or "a" from the file name.
 
 ## Code Snippets
-
 - For snippets **longer than 6 lines**:
   - Place in separate `.cs` file in a `snippets` folder next to the Markdown file
   - Create a subfolder named after the document
@@ -101,7 +81,6 @@ Console | console | 2
 Text | - | 2
 
 ## ASP.NET Core Specific Guidelines
-
 - Use the latest supported version for examples unless otherwise specified
 - Title and section header casing is sentence case (capitalize the first word and any proper nouns)
 - For parts of a title or section header that normally use code style in article text (backticks around the content), also use code style in the title or section header (example H1 header: "# Modify the `Program.cs` file")
@@ -113,7 +92,6 @@ Text | - | 2
 - For middleware content and examples, use the middleware class approach
 
 ## Issue Handling
-
 When creating a PR for an issue:
 1. Read the full issue and all linked references
 2. Study code samples from linked PRs for pre-release features