Wording changes #15
Merged
Wording changes #15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fryerd1
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
Please review and check off each item before submitting your PR:
Description of Changes
I have gone through the scripts and files and made some wording changes as corrections and for clarity. Please can you go through the changes and ensure the new wording makes sense in its context, or offer suggestions for improvements.
Additional Notes (Optional)
I have merged in a separate add quick start instructions branch which included clarification on the forking process for beginners
Reviewer Guidance
This template helps keep PRs consistent, clear, and easy to review. For more information, see the GitHub documentation on pull request templates.