Fix markdown heading formatting and typo in documentation

[Copilot]

Addresses review feedback from PR #3 to improve document structure and fix redundant wording.

Changes:

• PowerShell/system-administration/maintenance/README.md

  • Convert section titles ("Usage and placement", "Naming and contribution", "Examples") to proper ## headings
  • Fix typo: "rotate and compress rotating logs" → "rotate and compress log files"

• .github/PR_PREFERENCES.md

  • Convert section titles ("Recommendations", "Why this preference") to proper ## headings

These changes establish proper heading hierarchy for better document navigation and accessibility.

Original prompt

Based on the comments in the thread at #3 (review), please apply the following changes:

In PowerShell/system-administration/maintenance/README.md:

• The section headings "Usage and placement", "Naming and contribution", and "Examples" should be formatted as proper Markdown headings (using ##) instead of plain text. This improves document structure and navigation.
• Typo in comment: "rotating logs" should be "log files" for clarity. The phrase "rotate and compress rotating logs" is redundant.

In .github/PR_PREFERENCES.md:

• The section headings "Recommendations" and "Why this preference" should be formatted as proper Markdown headings (using ##) instead of plain text. This improves document structure and navigation.

This pull request was created as a result of the following prompt from Copilot chat.

Based on the comments in the thread at #3 (review), please apply the following changes:

In PowerShell/system-administration/maintenance/README.md:

• The section headings "Usage and placement", "Naming and contribution", and "Examples" should be formatted as proper Markdown headings (using ##) instead of plain text. This improves document structure and navigation.
• Typo in comment: "rotating logs" should be "log files" for clarity. The phrase "rotate and compress rotating logs" is redundant.

In .github/PR_PREFERENCES.md:

• The section headings "Recommendations" and "Why this preference" should be formatted as proper Markdown headings (using ##) instead of plain text. This improves document structure and navigation.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull Request Overview

This PR addresses review feedback by improving markdown document structure and correcting a typo in documentation files. The changes enhance document navigation and accessibility through proper heading hierarchy.

• Converts plain text section titles to proper ## markdown headings across two documentation files
• Fixes redundant wording in an example description: "rotating logs" → "log files"

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
PowerShell/system-administration/maintenance/README.md	Converts three section titles ("Usage and placement", "Naming and contribution", "Examples") to proper ## headings and fixes typo in example description
.github/PR_PREFERENCES.md	Converts two section titles ("Recommendations", "Why this preference") to proper ## headings

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.