/* Backports development flow */
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki
index 8503512..75c9a29 100644
--- a/wiki/Documentation_backports_hacking.mediawiki
+++ b/wiki/Documentation_backports_hacking.mediawiki
@@ -10,8 +10,8 @@
= Backports development flow =
-The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] master
-development branch always tracks linux-next, allowing it to
+The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] "master"
+development branch always tracks "linux-next", allowing it to
track all the development trees. This ensures that at the end
of each merge window, the state of the backports will be
very close to the state of the first release candidate. At this
@@ -21,9 +21,11 @@
a stable kernel.
The backports project thus makes three kinds
-of backports releases possible: those derived from linux-next, those
-derived from the most recent release candidate if any, and
-those derived from recent stable kernels.
+of backports releases possible:
+
+* those derived from linux-next
+* those derived from the most recent release candidate (if any)
+* those derived from recent stable kernels.
= Backports git tree tags and branches =
