commit: 50e2eba27e09f94194699f767d9cf171e675dfc4
parent 9a68008eaf9537eec613c10081142dce52b3e545
Author: Drew DeVault <sir@cmpwn.com>
Date: Thu, 3 Sep 2020 07:51:14 -0400
Fix typos
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/blog/Linux-development-is-profoundly-distributed.md b/content/blog/Linux-development-is-profoundly-distributed.md
@@ -21,7 +21,7 @@ let's start reading some of these entries.
Each of these represents a different individual or group which has some interest
in the Linux kernel, often a particular driver. Most of them have an "F" entry,
which indicates which files they're responsible for in the source code. Most
-have a "L" entry, which has a mailing list you can post questions, bug reports,
+have an "L" entry, which has a mailing list you can post questions, bug reports,
and patches to, as well as an individual maintainer ("M") or maintainers who are
known to have expertise and autonomy over this part of the kernel. Many of them
— but, hmm, not all — also have a tree ("T"), which is a dedicated
@@ -63,8 +63,8 @@ and then up again towards meta-meta trees like linux-staging, and eventually to
Linus' tree[^2]. Along the way it might receive feedback from other projects if it
has cross-cutting concerns, tracing out an ever growing and shrinking bubble of
inclusion among the trees, ultimately ending up in every tree. And that's
-*still* a implication — for example, an important bug fix may sidestep all
-of this entirely and get applied on top of a downstream distribution kernel,
+*still* a simplification — for example, an important bug fix may sidestep
+all of this entirely and get applied on top of a downstream distribution kernel,
ending up on end-user machines before it's made much progress upstream at all.
[^2]: That's not the only destination; for example, some patches will end up in the LTS kernels as well.
