Merge commit '6e39eb8ca7100c27aa42409b0491592be0d67a0d'

Author: Frantisek Hrbata

redhat/rhdocs/docs/README.adoc

@@ -128,14 +128,14 @@ Note that kernel repositories take a long time to fork.
 . Find the name of the fork.
 * `git remote -v | grep _<GitLab_username>_` +
 Note that GitLab username is used for the remote name.
-. Modify your fork while following the details outlined in xref:commitrules.adoc#commitdescriptioninfo[CommitRules Section 3: Commit-Specific Description Information]
+. Modify your fork while following the details outlined in xref:CommitRules.adoc#commitdescriptioninfo[CommitRules Section 3: Commit-Specific Description Information]
 
 . Push the updated branch to your kernel fork on GitLab.
 * `git push -u _<GitLab_fork_name>_ _<branch_name>_`
 
 == Creating merge requests
 
-. Familiarize yourself with xref:commitrules.adoc[CommitRules] and xref:verifying_a_gitlab_mr.adoc[Verify the MR information] documents.
+. Familiarize yourself with xref:CommitRules.adoc[CommitRules] and xref:verifying_a_gitlab_mr.adoc[Verify the MR information] documents.
 
 . When done with your work, create a merge request (MR) on some branch other than the `main` branch. +
 `git checkout -b <branch_name>` +
@@ -303,7 +303,7 @@ All approved MR's, assuming they have the +readyForMerge+ label, will normally b
 * https://source.redhat.com/groups/public/kernel[General Kernel Info Page]
 * https://gitlab.com/redhat/centos-stream/src/kernel/documentation/-/blob/main/docs/what_is_a_GitLab_fork.adoc[What is a GitLab Fork?]
 * xref:faq.adoc[Frequently Asked Questions]
-* xref:commitrules.adoc[CommitRules]
+* xref:CommitRules.adoc[CommitRules]
 * xref:rh_and_gitlab_configuration.adoc[Red Hat and GitLab Configuration]
 * xref:lab.adoc[Gitlab 'lab' utility and the Red Hat Kernel]
 * https://gitlab.cee.redhat.com/kernel-review/revumatic/[Red Hat Specific 'revumatic' tool]