doc: cleanup kernel.rst

[mirror_frr.git] / COMMUNITY.md

diff --git a/COMMUNITY.md b/COMMUNITY.md
index 5bc95ddcc826f9023071fbd3f4fbb0d71416245c..7605b03201ae1f12038e18b05ff6c4dda3886e60 100644 (file)
--- a/COMMUNITY.md
+++ b/COMMUNITY.md
@@ -82,7 +82,7 @@ for the release notes.
 
 ### Pre-submission Checklist
 
-* Format code (see [Coding style requirements](#coding-style-requirements))
+* Format code (see [Developer's Guidelines](#developers-guidelines))
 * Verify and acknowledge license (see [License for contributions](#license-for-contributions))
 * Ensure you have properly signed off (see [Signing Off](#signing-off))
 * Test building with various configurations:
@@ -111,7 +111,7 @@ the Developer's Certificate of Origin (below). Code without a proper signoff
 can not and will not be merged.
 
 If you are unfamiliar with this process, you should read the [official policy
-at kernel.org](http://www.kernel.org/doc/Documentation/SubmittingPatches) and
+at kernel.org](https://www.kernel.org/doc/html/latest/process/submitting-patches.html) and
 you might find this article about [participating in the Linux community on the
 Linux Foundation
 website](http://www.linuxfoundation.org/content/how-participate-linux-community-0)
@@ -227,9 +227,11 @@ merged in a timely manner.
 Commit messages should be formatted in the same way as Linux kernel commit
 messages. The format is roughly
 
-``` dir: short summary
+```
+dir: short summary
 
-extended summary ```
+extended summary
+```
 
 `dir` should be the top level source directory under which the change was made.
 For example, a change in bgpd/rfapi would be formatted as: