typos from Frans Pop for the HOWTO file.

1 files changed, 15 insertions, 14 deletions

diff --git a/HOWTO b/HOWTO
index fa07c28decfa1..e4f21aab326f5 100644
--- a/HOWTO
+++ b/HOWTO
@@ -221,12 +221,12 @@ branches.  These different branches are:
 2.6.x kernels are maintained by Linus Torvalds, and can be found on
 kernel.org in the pub/linux/kernel/v2.6/ directory.  It's development
 process is as follows:
-  - As soon as a new kernel is released a two weeks windows is open,
+  - As soon as a new kernel is released a two weeks window is open,
     during this period of time maintainers can submit big diffs to
-    Linus, usually the patched sited in -mm kernels for a few weeks.
-    The preferred way to submit big changes is using git (more
-    information about git can be found at http://git.or.cz/) but plain
-    patches are also just fine.
+    Linus, usually the patches that have already been included in the
+    -mm kernel for a few weeks.  The preferred way to submit big changes
+    is using git (more information about git can be found at
+    http://git.or.cz/) but plain patches are also just fine.
   - After two weeks a -rc1 kernel is released it is now possible to push
     only patches that do not include new features that could affect the
     stability of the whole kernel.  Please note that a whole new driver
@@ -271,7 +271,7 @@ how the release process works.
 
 2.6.x -git patches
 ------------------
-These are daily snapshots of Linus' kernel tree which is managed in a
+These are daily snapshots of Linus' kernel tree which are managed in a
 git repository (hence the name.) These patches are usually released
 daily and represent the current state of Linus' tree.  They are more
 experimental than -rc kernels since they are generated automatically
@@ -298,9 +298,9 @@ If you wish to help out with the kernel development process, please test
 and use these kernel releases and provide feedback to the linux-kernel
 mailing list if you have any problems, and if everything works properly.
 
-These kernels in addition to all the other experimental patches they
-contain usually also contain any changes in the mainline -git kernels
-available at the time of release.
+In addition to all the other experimental patches, these kernels usually
+also contain any changes in the mainline -git kernels available at the
+time of release.
 
 The -mm kernels are not released on a fixed schedule, but usually a few
 -mm kernels are released in between each -rc kernel (1 to 3 is common).
@@ -380,8 +380,8 @@ places.  Use a search engine to find these archives.  For example:
 	http://dir.gmane.org/gmane.linux.kernel
 It is highly recommended that you search the archives about the topic
 you want to bring up, before you post it to the list. A lot of things
-are already discussed in detail and are only recorded at the mailing
-list archives.
+already discussed in detail are only recorded at the mailing list
+archives.
 
 Most of the individual kernel subsystems also have their own separate
 mailing list where they do their development efforts.  See the
@@ -504,7 +504,7 @@ recommended that you check your emails to make sure they make sense in
 English before sending them.
 
 
-Break your changes up
+Break up your changes
 ---------------------
 
 The Linux kernel community does not gladly accept large chunks of code
@@ -602,8 +602,9 @@ to be based on text he had written, and to Randy Dunlap and Gerrit
 Huizenga for some of the list of things you should and should not say.
 Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers,
 Vojtech Pavlik, Jan Kara, Josh Boyer, Kees Cook, Andrew Morton, Andi
-Kleen, Vadim Lobanov, Jesper Juhl, Adrian Bunk, Keri Harris, and Alex
-Shepard for their review and comments on early drafts of this document.
+Kleen, Vadim Lobanov, Jesper Juhl, Adrian Bunk, Keri Harris, Frans Pop,
+and Alex Shepard for their review and comments on early drafts of this
+document.