wording, markdown formatting.

en/integration-kernel.md

@@ -16,11 +16,19 @@ CONFIG_IP_PNP_DHCP=y
 CONFIG_ROOT_NFS=y
 ```
 
-## Patch files
+## Patch file requirements
 
-Patch files should be named `<number>-<description>.patch`.
+- Patch file name should follow format `<number>-<description>.patch`.
-- The patch files should not contain any package version reference in their filename.
+
-- The field `<number>` in the patch file name refers to the apply order, and shall start at 1.
+- Patch file should not contain any reference to package version in its name.
-It is preferred to pad the number with zeros up to 4 digits, like git-format-patch does. E.g.: _0001-foobar-the-buz.patch_
+
-- A message explaining what the patch does, and why it is needed, should be added in the header commentary of the patch.
+- The `<number>` part of patch's file name refers to the application order
-- You should add a Signed-off-by statement in the header of each patch to help with keeping track of the changes and to certify that the patch is released under the same license as the software that is modified.
+  starting from 1. It is preferred to left-pad the number with zeros up to total
+  of four digits, like `git-format-patch` does. _0001-foobar-the-buz.patch_
+
+- Patch file should contain a commentary in its header, explaining what this
+  patch does, and why it is needed.
+
+- Add a _Signed-off-by_ statement in the header of each patch file to help
+  tracking changes and certify that the patch is released under the same license
+  as the software it modifies.