docs: Minor changes to Contributing.md (#121)

* udated clone url to make it clearer that it is a fork
* bolded section titles

Author: Grazerquart

CONTRIBUTING.md

@@ -2,26 +2,26 @@
 
 Thank you for considering contributing to this project! All contributors, big or small, are welcomed. To make the contribution process as smooth as possible, please follow the guidelines below.
 
-1. Fork the repository: Start by forking the repository to your own GitHub account. This will create a copy of the repository under your username.
-2. Create a new branch: Clone the forked repository to your local machine and create a new branch for your feature or bug fix.
+1. **Fork the repository:** Start by forking the repository to your own GitHub account. This will create a copy of the repository under your username.
+2. **Create a new branch:** Clone the forked repository to your local machine and create a new branch for your feature or bug fix.
    ```bash
-   git clone https://github.com/goniszewski/grimoire/repository.git
+   git clone https://github.com/your-username/grimoire.git
    cd grimoire
    git checkout -b your-branch-name
    ```
-3. Make the changes: Make the necessary changes to the codebase, ensuring that you follow any coding style guidelines mentioned in the project documentation or README file.
-4. Test your changes: Thoroughly test your changes to ensure that they do not break existing functionality and introduce new bugs.
-5. Commit your changes: Once you are satisfied with your modifications, commit them using a descriptive commit message following the rules of [Semantic Commit Messages](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716).
+3. **Make the changes:** Make the necessary changes to the codebase, ensuring that you follow any coding style guidelines mentioned in the project documentation or README file.
+4. **Test your changes:** Thoroughly test your changes to ensure that they do not break existing functionality and introduce new bugs.
+5. **Commit your changes:** Once you are satisfied with your modifications, commit them using a descriptive commit message following the rules of [Semantic Commit Messages](https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716).
    ```bash
    git add .
    git commit -m "fix: Your detailed description of your changes."
    ```
-6. Push to your branch: Push your changes to your forked repository on GitHub.
+6. **Push to your branch:** Push your changes to your forked repository on GitHub.
    ```bash
    git push origin your-branch-name
    ```
-7. Submit a Pull Request: Navigate to the GitHub page of the original project and submit a pull request with a clear description of your changes.
-8. Wait for review: Patiently wait for the maintainers to review your pull request. They might ask for additional information or changes, which you can address by updating your branch and submitting an updated pull request.
-9. Let it spark ✨ Yay, your contribution has been accepted and merged into the project! Thank you for making this project better 🤝
+7. **Submit a Pull Request:** Navigate to the GitHub page of the original project and submit a pull request with a clear description of your changes.
+8. **Wait for review:** Patiently wait for the maintainers to review your pull request. They might ask for additional information or changes, which you can address by updating your branch and submitting an updated pull request.
+9. **Let it spark** ✨ Yay, your contribution has been accepted and merged into the project! Thank you for making this project better 🤝
 
 Thank you for contributing to this project! We appreciate your efforts in making it even better. If you have any questions or need further clarification, feel free to reach out to us.