spelling fixes found by Avuton Olrich in the HOWTO

1 files changed, 18 insertions, 17 deletions

diff --git a/HOWTO b/HOWTO
index 2e7f017e48d4e..584939e62ba23 100644
--- a/HOWTO
+++ b/HOWTO
@@ -208,22 +208,23 @@ branches.  These different branches are:
 2.6.x kernel tree
 -----------------
 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 a new kernel is released a two weeks windows 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.
-  - After two weeks a -rc1 kernel is released and now is possible to push only
-    patches that do not include new functionalities that could affect the
-    stability of the whole kernel.  Please note that a whole new driver (or
-    filesystem) might be accepted after -rc1 because there is no risk of
-    causing regressions with such a change as long as the change is
-    self-contained and does not affect areas outside of the code that is being
-    added.  git can be used to send patches to Linus after -rc1 is
-    released, but the patches need to also be sent to a public mailing
-    list for review.
+kernel.org in the pub/linux/kernel/v2.6/ directory.  It's development
+process is as follows:
+  - As soon a new kernel is released a two weeks windows 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.
+  - After two weeks a -rc1 kernel is released and now is 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 (or filesystem) might be accepted after -rc1 because there is
+    no risk of causing regressions with such a change as long as the
+    change is self-contained and does not affect areas outside of the
+    code that is being added.  git can be used to send patches to Linus
+    after -rc1 is released, but the patches need to also be sent to a
+    public mailing list for review.
   - A new -rc is released whenever Linus deems the current git (the
     kernel's source management) tree to be in a reasonably sane state
     adequate for testing.  The goal is to release a new -rc kernel every
@@ -240,7 +241,7 @@ mailing list about kernel releases:
 2.6.x.y -stable kernel tree
 ---------------------------
 Kernels with 4 digit versions are -stable kernels. They contain
-relativly small and critical fixes for security problems or significant
+relatively small and critical fixes for security problems or significant
 regressions discovered in a given 2.6.x kernel.
 
 This is the recommended branch for users who want the most recent stable