diff --git a/README.md b/README.md
index 4cb511f..55bc357 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ may occur!**
Here's a video of kpatch in action:
-[](http://www.youtube.com/watch?v=juyQ5TsJRTA)
+[](https://www.youtube.com/watch?v=juyQ5TsJRTA)
And a few more:
@@ -195,7 +195,14 @@ apt update may report a "404 Not Found" error, as well as a complaint about
disabling the repository by default. This message may be ignored (see issue
#710).
-#### Debian 8.0
+#### Debian 9 (Stretch)
+
+Since Stretch the stock kernel can be used without changes, however the
+version of kpatch in Stretch is too old so you still need to build it
+manually. Follow the instructions for Debian Jessie (next section) but skip
+building a custom kernel/rebooting.
+
+#### Debian 8 (Jessie)
*NOTE: You'll need about 15GB of free disk space for the kpatch-build cache in
`~/.kpatch` and for ccache.*
@@ -229,7 +236,7 @@ Install the dependencies for the "kpatch-build" command:
apt-get install ccache
ccache --max-size=5G
-#### Debian 7.x
+#### Debian 7 (Lenny)
*NOTE: You'll need about 15GB of free disk space for the kpatch-build cache in
`~/.kpatch` and for ccache.*
@@ -270,6 +277,7 @@ Compile kpatch:
make
+
### Install
OPTIONAL: Install kpatch to `/usr/local`:
@@ -351,6 +359,7 @@ can have some major pitfalls if you're not careful. To learn more about how to
properly create live patches, see the [Patch Author
Guide](doc/patch-author-guide.md).
+
How it works
------------
@@ -405,6 +414,7 @@ The primary steps in kpatch-build are:
- Link all the output objects into a cumulative object
- Generate the patch module
+
### Patching
The patch modules register with the core module (`kpatch.ko`).
@@ -508,7 +518,7 @@ updating the instruction directly. This approach also ensures that the code
modification path is reliable, since ftrace has been doing it successfully for
years.
-**Q Is kpatch compatible with \<insert kernel debugging subsystem here\>?**
+**Q. Is kpatch compatible with \<insert kernel debugging subsystem here\>?**
We aim to be good kernel citizens and maintain compatibility. A kpatch
replacement function is no different than a function loaded by any other kernel
@@ -555,7 +565,7 @@ We hope to make the following changes to other projects:
- ftrace improvements to close any windows that would allow a patch to
be inadvertently disabled
-**Q: Is it possible to register a function that gets called atomically with
+**Q. Is it possible to register a function that gets called atomically with
`stop_machine` when the patch module loads and unloads?**
We do have plans to implement something like that.
@@ -618,6 +628,7 @@ For big PRs, it's a good idea to discuss them first in github issues or on the
[mailing list](https://www.redhat.com/mailman/listinfo/kpatch) before you write
a lot of code.
+
License
-------
diff --git a/doc/patch-author-guide.md b/doc/patch-author-guide.md
index eb4ea58..e2c38fa 100644
--- a/doc/patch-author-guide.md
+++ b/doc/patch-author-guide.md
@@ -17,7 +17,7 @@ are safe to apply. Every patch must also be analyzed in-depth by a human.
The most important point here cannot be stressed enough. Here comes the bold:
-**Do not blindly apply patches. There is no subsitute for human analysis and
+**Do not blindly apply patches. There is no substitute for human analysis and
reasoning on a per-patch basis. All patches must be thoroughly analyzed by a
human kernel expert who completely understands the patch and the affected code
and how they relate to the live patching environment.**
@@ -167,7 +167,7 @@ data structures, you can use the `kpatch_shadow_*()` functions:
Example: The `shadow-newpid.patch` integration test demonstrates the usage of
these functions.
-A shadow PID variable is allocated in `do_fork()` : it is associated with the
+A shadow PID variable is allocated in `do_fork()`: it is associated with the
current `struct task_struct *p` value, given a string lookup key of "newpid",
sized accordingly, and allocated as per `GFP_KERNEL` flag rules.