diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 396c297..7aa0f2a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -47,11 +47,11 @@ If you want to contribute changes without write access to the repository, you ca
 2. Once you have a fork, clone it to your local machine and create a new branch from the `develop` branch.
 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.
+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 `develop` 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.
 
-The merge request notifies project maintainers that you've made changes and allows them to review your code and potentially merge it into the main project.
+The merge request notifies project maintainers that you've made changes and allows them to review your code and potentially merge it into the `develop` branch.
 
 When your branch is merged, you may want to [update your fork](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#update-your-fork) to be synced with upstream.