Formatting and organziational fixes

Author: wadepickett

.github/copilot-instructions.md

@@ -9,6 +9,32 @@ ms.date: 07-29-2025
 ## 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.**
 
+## General Guidelines
+
+### 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
+3. For labeled issues:
+ - **new-feature:** State which version introduced the feature
+ - **bug:** Focus on correcting technical inaccuracies
+4. When you're assigned an issue, after you've completed your work and the workflows (status checks) have run, check to make sure there are no build warnings under the OpenPublishing.Build status check. If there are, open the build report (under View Details) and resolve any build warnings you introduced.
+
+### 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.
+
+### 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
+
+### 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
+
 ## Repository-Specific Guidelines
 - Follow the [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/)
 - **Repository Exceptions**:
@@ -21,30 +47,13 @@ This document contains repository-specific instructions for GitHub Copilot when
     - The correct order of metadata lines is to place the title (`title`) first and the rest of the metadata lines in alphabetical order. Example: `title`, `author`, `description`, `monikerRange`, `ms.author`, `ms.custom`, `ms.date`, `uid`, `zone_pivot_groups`
     - Metadata `ms.date: <today's date>` with a format of MM-DD-YYYY.  If the file already has a `ms.date` metadata, update it to today's date if more than 50 characters are changed in the file.
 
-## Version Targeting
-
-### Common Range Patterns
+### Version Targeting 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
-
-## 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
+### 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
@@ -66,21 +75,20 @@ This document contains repository-specific instructions for GitHub Copilot when
   ```
 - Use the latest, non-preview C# coding patterns in non-preview code examples
 - Use the latest preview C# coding patterns in preview code examples
+- Use the following code language and indentation standards for markdown code blocks or the `language` attribute of code snippets:
 
-The following table indicates the code language to use for markdown code blocks or the `language` attribute of a code snippet and the amount of indentation to use.
+  Content of the snippet | Code language | Indentation in spaces
+  :---: | :---: | :---:
+  C# | csharp | 4
+  HTML | html | 4
+  CSS | css | 4
+  JavaScript | javascript | 2 (4 spaces for line continuation)
+  XML | xml | 2
+  JSON | json | 2
+  Console | console | 2
+  Text | - | 2
 
-Content of the snippet | Code language | Indentation in spaces
-:---: | :---: | :---:
-C# | csharp | 4
-HTML | html | 4
-CSS | css | 4
-JavaScript | javascript | 2 (4 spaces for line continuation)
-XML | xml | 2
-JSON | json | 2
-Console | console | 2
-Text | - | 2
-
-## ASP.NET Core Specific Guidelines
+### 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")
@@ -90,13 +98,3 @@ Text | - | 2
 - Lead with Microsoft recommended approaches
 - Include differences between Minimal API and controller-based approaches when relevant
 - 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
-3. For labeled issues:
- - **new-feature:** State which version introduced the feature
- - **bug:** Focus on correcting technical inaccuracies
-4. When you're assigned an issue, after you've completed your work and the workflows (status checks) have run, check to make sure there are no build warnings under the OpenPublishing.Build status check. If there are, open the build report (under View Details) and resolve any build warnings you introduced.
-