Refer the documentation of the actual endpoint for status reference

The pipeline API can report more statuses than the ones we can send with the commit status endpoint. Better not introduce confusion by referring to the actual endpoint we're calling.

Author: TPXP

README.md

@@ -345,7 +345,7 @@ Also make sure you have chosen the appropriate GitLab instance from the 'GitLab
         }
     }
     ```
-* Or use the `updateGitlabCommitStatus` step to use a custom value for updating the commit status. You could use try/catch blocks or other logic to send fine-grained status of the build to GitLab. Valid statuses are defined by GitLab and documented here: https://docs.gitlab.com/ce/api/pipelines.html
+* Or use the `updateGitlabCommitStatus` step to use a custom value for updating the commit status. You could use try/catch blocks or other logic to send fine-grained status of the build to GitLab. Valid statuses are defined by GitLab and documented here: https://docs.gitlab.com/ee/api/commits.html#post-the-build-status-to-a-commit
     ```groovy
     node() {
         stage('Checkout') { checkout <your-scm-config> }