docs: enhance pre-commit setup instructions for contributors (brisbanesocialchess#286)

* docs: enhance pre-commit setup instructions for contributors

* docs: finalize contributing guide with clear and consistent instructions

* docs: update pull request creation instructions for clarity and simplicity

* docs: minor update to Community Support section to trigger PR button

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* Update CONTRIBUTING.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

---------

Co-authored-by: John Bampton <jbampton@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Author: 3 people

CONTRIBUTING.md

@@ -112,31 +112,37 @@ Our configuration is already in the repo: [dprint.json](./dprint.json)
 
 #### 🧪 Setting Up pre-commit
 
-Used to enforce newline at end of files and OS-specific line endings.
+We use [pre-commit](https://pre-commit.com/) to automatically check your code for common issues, like missing end-of-file newlines and inconsistent line endings. This keeps our project clean and easy for everyone to work on.
 
-**Install (requires Python):**
+**How to install (requires Python):**
 
 ```bash
-pip install pre-commit
+python -m pip install --user pre-commit
 ```
 
-**Activate pre-commit hooks:**
+**Set up pre-commit hooks for this project:**
 
 ```bash
 pre-commit install
 ```
 
-**Run manually (optional):**
+This will make pre-commit run its checks every time you make a commit.
+**Running checks manually (optional):**
 
 ```bash
 pre-commit run --all-files
 ```
 
+This command runs all configured pre-commit hooks against all files in the repository.
+For more info, visit the [pre-commit website](https://pre-commit.com/).
+
 ---
 
 ### 5. 📝 Commit Changes
 
-Use descriptive commit messages that clearly state the purpose of your changes.
+Use meaningful and clear commit messages that describe the purpose of your changes. This helps maintain a clean and understandable project history.
+
+**Example of staging and committing changes:**
 
 ```bash
 git add .
@@ -145,22 +151,29 @@ git commit -m "Add feature: description of feature"
 
 ### 6. ⬆️ Push Changes
 
+Push your local branch to your remote fork. Replace `your-branch-name` with the name of your current branch.
+
 ```bash
 git push origin add-new-feature
 ```
 
+This makes your changes available for review and merging via a Pull Request.
+
 ### 7. 🔄 Create a Pull Request
 
 - Go to your forked repository on GitHub.
-- Click **"Compare & pull request"**.
-- Add a title and description (e.g., "Fixes #102").
-- Click **"Create pull request"**.
+- Click the **"Compare & pull request"** button near the top of the page.
+- Make sure your changes look correct and you are merging into the right branch.
+- Write a clear and simple title describing your changes.
+- Add a short description explaining what you changed and why. If it fixes an issue, mention it like this: `Fixes #issue-number`.
+- Click **"Create pull request"** to submit your contribution.
+- Watch for feedback on your Pull Request and respond to any comments.
 
 ---
 
 ## Community Support
 
 If you need help or have questions:
 
-- Join Discussions: Participate in discussions.
-- Contact Maintainers: Reach out to project maintainers if needed.
+- Join Discussions: Participate in ongoing discussions with the community.
+- Contact Maintainers: Reach out to project maintainers if you need direct assistance.