From 76166d83e966d9ec834bd30424045c44438fbe9b Mon Sep 17 00:00:00 2001
From: puneetse <22071208+puneetse@users.noreply.github.com>
Date: Tue, 5 Feb 2019 14:18:40 -0800
Subject: [PATCH] Move patch management suggestion

---
 .../guides/maintenance/kernel-development.rst        | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/source/clear-linux/guides/maintenance/kernel-development.rst b/source/clear-linux/guides/maintenance/kernel-development.rst
index 293628d3..3816a5eb 100644
--- a/source/clear-linux/guides/maintenance/kernel-development.rst
+++ b/source/clear-linux/guides/maintenance/kernel-development.rst
@@ -186,11 +186,6 @@ eventually merged with the main :file:`.config`.
       make config
 
 
-If you have a large number of patches or a more complex workflow, 
-consider using a patch management tool in addition to Git such as 
-`Quilt`_. 
-
-
 
 Modify kernel source code 
 =========================
@@ -198,6 +193,11 @@ Modify kernel source code
 Changes to kernel code are applied with patch files. Patch files are 
 formatted git commits that can be applied to the main source code.
 
+If you have a large number of patches or a more complex workflow, 
+consider using a patch management tool in addition to Git such as 
+`Quilt`_. 
+
+
 #. Clone the linux kernel source code into a new working directory
 
    .. code-block:: bash
@@ -291,7 +291,7 @@ formatted git commits that can be applied to the main source code.
 
 
 Build and install the kernel
-============================
+****************************
 After changes have been made to the kernel SPEC file and config file, 
 the kernel is ready to be compiled and packaged into a RPM.