Author: Jake Bauer <firstname.lastname@example.org>
Date: Sun, 7 Jun 2020 02:16:21 -0400
Reword/rearrange a few words in latest blog post for readability
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/pages/blog/why-email-is-the-best-discussion-platform.md b/pages/blog/why-email-is-the-best-discussion-platform.md
@@ -64,8 +64,8 @@ to sell it (if they don't already sell it themselves).
Not to mention the various other issues such as text-only content being far
better for accessibility than what the web can offer, most of the web-based
-packages being very much bloated where pages take seconds to load and megabytes
-of bandwidth, and the fact that web browsers are very resource-hungry pieces of
+packages being very bloated where pages take seconds to load and megabytes of
+bandwidth, and the fact that web browsers are very resource-hungry pieces of
software which can be difficult for those with fewer resources (e.g. people with
second-hand equipment in third world countries) to run as fast as how Silicon
Valley thinks everyone's computer runs.
@@ -95,10 +95,10 @@ email allows for this freedom.
Another great thing about email is that it can be used for patches in addition
to discussion. [Sending patches via email](https://git-send-email.io) is as
-simple and straightforward as using something like Pull Requests and, just like
-with Pull Requests, the discussion can be had in the same thread as a submitted
-patch and patches can be applied to a repository without needing to use a
-different piece of software or even open a web browser.
+simple and straightforward as using something like Pull Requests. Just like with
+Pull Requests, the discussion can be had in the same thread as a submitted patch
+and patches can be applied to a repository all without needing to open a web
+browser or use a different piece of software.
Unfortunately, email has a reputation of being hard to use because of what I
think is an unwillingness to learn a new paradigm after having become used to