docs: clarify usage examples requirement in README.md instructions

Author: joshjohanning

.github/copilot-instructions.md

@@ -17,6 +17,7 @@ When adding new scripts to any directory:
 - Always add an entry to the appropriate `README.md` file in alphabetical order
 - Follow the existing format and structure in the README
 - Include a clear description, usage examples, and any prerequisites/notes
+- We don't need both usage AND an example of running the script - just one please
 - Use proper kebab-case naming convention for script files
 - Avoid short words like "repo" (use "repository"), "org" (use "organization")
 - Test that the entry passes `lint-readme.js` validation

.github/prompts/add-script-to-readme.prompt.md

@@ -35,7 +35,7 @@ Each script entry must include:
 
 - **Heading**: `### script-name.sh` (or appropriate extension)
 - **Description**: Brief explanation of what the script does
-- **Usage examples**: If applicable, show how to run the script
+- **Usage examples**: If applicable, show how to run the script (We don't need both usage AND an example of running the script - just one please)
 - **Notes/Warnings**: Any important information about prerequisites, permissions, or limitations
 
 ### 4. File Existence