diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 52fe722..5a879f2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -28,13 +28,11 @@ This practice ensures that everyone remains updated on ongoing tasks, fostering
 
 If you want to contribute changes without write access to the repository, you can still do so by forking. This is a simple way for anyone to contribute by creating your own copy of the project where you can make changes freely.
 
-First, you'll need to fork the repository. Once you have a fork, clone it to your local machine.
-
-Then, you can make changes just like you would if you were a member of the project.
-
-After you've made your changes, you commit them locally and push these back to your fork on gitlab.
-
-Finally, you can [create a merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#when-you-work-in-a-fork) from your fork's branch to upstream's branch.
+1. First, you'll need to fork the repository. 
+2. Once you have a fork, clone it to your local machine.
+3. Then, you can make changes just like you would if you were a member of the project.
+4. After you've made your changes, you commit them locally and push these back to your fork on gitlab.
+5. Finally, you can [create a merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#when-you-work-in-a-fork) from your fork's branch to upstream's branch.
 
 > We encourage you to [allow commits from upstream members](https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html#allow-commits-from-upstream-members) so that they can [push to the fork as the upstream member](https://docs.gitlab.com/ee/user/project/merge_requests/allow_collaboration.html#push-to-the-fork-as-the-upstream-member) in order for you to reach out for help.