Update contributing.md (#200)

Co-authored-by: Marc Bernard <[email protected]>

Author: francisco-milan

src/development-guide/read-first/contributing.md

@@ -24,8 +24,8 @@ Having already [installed](/user-guide/getting-started/install.md#install-standa
 
 6. Submit a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) with the changes.
 
-Alternatively to the steps above, use the GitHub web interface to change the files directly on a GitHub branch of your forked abapGit repository and then submit a pull request. This might make sense when, e.g., contributing to the documentation files such as the one you are reading right now (where contributions may be initiated through the "Improve this page" link above).
+Alternatively to the steps above, use the GitHub web interface to change the files directly on a GitHub branch of your forked abapGit repository and then submit a pull request. This might make sense when, e.g., contributing to the documentation files such as the one you are reading right now (where contributions may be initiated through the "Edit this page" link below).
 
 If you already have an old fork and would like to create a new pull request, you can sync your old fork to the current state following this guide: [Sync your fork to original repository](https://github.com/KirstieJane/STEMMRoleModels/wiki/Syncing-your-fork-to-the-original-repository-via-the-browser).
 
-After your pull request is merged to the abapGit default branch, abapmerge will automatically run to build the standalone report version of abapGit. Every time a commit is pushed to the default branch, GitHub Actions is triggered to perform this build. It uses [abapmerge](https://github.com/larshp/abapmerge) to merge all the includes into a single file (the standalone version) which can be downloaded from [here](https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap)
+After your pull request is merged to the abapGit default branch, abapmerge will automatically run to build the standalone report version of abapGit. Every time a commit is pushed to the default branch, GitHub Actions is triggered to perform this build. It uses [abapmerge](https://github.com/larshp/abapmerge) to merge all the includes into a single file (the standalone version) which can be downloaded from [here](https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap)

src/user-guide/projects/online/contributing.md

@@ -16,5 +16,5 @@ Check out further details in [Understanding the GitHub flow](https://guides.gith
 The forked repository can be deleted after the pull request has been closed.
 
 :::tip
-If you want to contribute to abapGit, please [see read this](/development-guide/read-first/contributing.md).
-:::
+If you want to contribute to abapGit, please see [Read First](/development-guide/read-first/).
+:::