fixup! [Docs] Add more details to commit message styleguide

Signed-off-by: Michał Kowalczyk <mkow@invisiblethingslab.com>

CONTRIBUTING.rst

@@ -144,7 +144,7 @@ Reviewing Guidelines
    the same time).
 #. Meaningful commit messages (it's much easier to get them right if commits are
    really atomic). Commit messages should follow `commit message style guidelines
-   <coding-style.html#commit-message-formatting>`__.
+   <https://gramine.readthedocs.io/en/latest/devel/coding-style.html#commit-message-formatting>`__.
 #. Every PR description should include: what's the purpose of the changes, what
    is changed (and how, in case of redesigning a component), and how to test the
    changes.

Documentation/devel/coding-style.rst

@@ -43,16 +43,17 @@ Commit message formatting
 TL;DR: we follow https://commit.style/.
 
 Additionally, commit message one-liner should include which component was
-changed (``PAL-{Linux,SGX}`` / ``LibOS`` / ``Docs`` / ``CI``) in the format
-"[component] Change description". The one-liner should be
+changed (``PAL/{Linux,Linux-SGX}`` / ``LibOS`` / ``Docs`` / ``CI``) in the
+format "[component] Change description". The one-liner should be
 written in imperative mood and say what this particular commit changes.
 
 We aim for our repository and commit history to be self-contained and still
 usable even without GitHub (e.g. in case we migrate to a different provider).
 Thus, please restrain from descriptions like "Fixes #1234" and instead describe
 the fix in the commit message. If you really need to reference something on our
 GitHub, then use the full URL instead of #1234, so that it won't break if we
-move to a different repository.
+move to a different repository. If you want to reference a specific commit,
+please quote its one-liner message and optionally its hash.
 
 Please never write descriptions like "file.c doesn't flush buffers on exit" -
 it's not clear whether it's what the commit does, or whether it's the problem it