kernel-dev: First re-write of the "Patches" section.

(From yocto-docs rev: 64e2b623e040efeefdef572024c867a57a883f24)

Signed-off-by: scott-lenovo <scott-lenovo@ubuntu.(none)>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 9 insertions, 6 deletions

diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 7d82b54f65..12d3d7c8ec 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -802,10 +802,13 @@ The description file can include multiple kconf statements, one per fragment.
         <title>Patches</title>
 
         <para>
-            Patches are described in a very similar way to configuration
-            fragments, which are described in the previous section.
-            Instead of a <filename>.cfg</filename> file, they work with
-            source patches.
+            Patch descriptions are very similar to configuration fragment
+            descriptions, which are described in the previous section.
+            However, instead of a <filename>.cfg</filename> file, these
+            descriptions work with source patches.
+        </para>
+
+        <para>
             A typical patch includes a description file and the patch itself:
             <literallayout class='monospaced'>
      patches/mypatch.scc:
@@ -814,8 +817,8 @@ The description file can include multiple kconf statements, one per fragment.
      patches/mypatch.patch:
         &lt;typical-patch&gt;
             </literallayout>
-            For <filename>.patch</filename> files, the typical patch
-            is created with <filename>diff -Nurp</filename> or
+            You can create the typical <filename>.patch</filename>
+            file using <filename>diff -Nurp</filename> or
             <filename>git format-patch</filename>.
         </para>