From 4dc6c0330e62281613eb1066fa36243c0b0db666 Mon Sep 17 00:00:00 2001 From: puneetse <22071208+puneetse@users.noreply.github.com> Date: Wed, 20 Feb 2019 18:40:47 -0800 Subject: [PATCH] Clarify a few sentences --- .../clear-linux/guides/maintenance/kernel-development.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/clear-linux/guides/maintenance/kernel-development.rst b/source/clear-linux/guides/maintenance/kernel-development.rst index 35d9ee9f..cdac8a7c 100644 --- a/source/clear-linux/guides/maintenance/kernel-development.rst +++ b/source/clear-linux/guides/maintenance/kernel-development.rst @@ -263,8 +263,8 @@ consider using a patch management tool in addition to Git such as source working directory. -#. Initialize the kernel source directory as a new git repo and commit - all the files to begin tracking changes. +#. Initialize the kernel source directory as a new git repo and create a + commit with all the existing source files to begin tracking changes. .. code-block:: bash @@ -273,7 +273,7 @@ consider using a patch management tool in addition to Git such as git commit -m "Initial commit of Linux kernel source" -#. Apply ptches provided by the |CL| kernel package to the kernel source +#. Apply patches provided by the |CL| kernel package to the kernel source in the working directory. .. code-block:: bash @@ -281,7 +281,7 @@ consider using a patch management tool in addition to Git such as git am ../*.patch -#. Make any desired code changes to the Linux source code files. +#. Make any of your desired code changes to the Linux source code files. #. Track and commit your changes to the local git repo.