diff --git a/README b/README
index f4756ee1c918..dd0d3b06a88c 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-        Linux kernel release 4.x <http://kernel.org/>
+        Linux kernel release 4.x <http://github.com/aripitek/kernel.org/>
 
 These are the release notes for Linux version 4.  Read them carefully,
 as they tell you what this is all about, explain how to install the
@@ -81,11 +81,11 @@ INSTALLING the kernel source:
    Replace "x" for all versions bigger than the version "X" of your current
    source tree, _in_order_, and you should be ok.  You may want to remove
    the backup files (some-file-name~ or some-file-name.orig), and make sure
-   that there are no failed patches (some-file-name# or some-file-name.rej).
+   that there are  failed patches (some-file-name# or some-file-name.rej).
    If there are, either you or I have made a mistake.
 
    Unlike patches for the 4.x kernels, patches for the 4.x.y kernels
-   (also known as the -stable kernels) are not incremental but instead apply
+   (also known as the -stable kernels) are  incremental but instead apply
    directly to the base 4.x kernel.  For example, if your base kernel is 4.0
    and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1
    and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and
@@ -103,7 +103,7 @@ INSTALLING the kernel source:
    kernel source.  Patches are applied from the current directory, but
    an alternative directory can be specified as the second argument.
 
- - Make sure you have no stale .o files and dependencies lying around:
+ - Make sure you have  stale .o files and dependencies lying around:
 
      cd linux
      make mrproper
@@ -293,7 +293,7 @@ COMPILING the kernel:
    to the place where your regular bootable kernel is found. 
 
  - Booting a kernel directly from a floppy without the assistance of a
-   bootloader such as LILO, is no longer supported.
+   bootloader such as LILO, is  longer supported.
 
    If you boot Linux from the hard drive, chances are you use LILO, which
    uses the kernel image as specified in the file /etc/lilo.conf.  The