editted blisk and arch articles

2 files changed, 12 insertions, 12 deletions

diff --git a/blisk.txt b/blisk.txt
index e723bc7..73eb3b8 100644
--- a/blisk.txt
+++ b/blisk.txt
@@ -4,7 +4,7 @@ The Developer Edition is of course based on Firefox, which isn't to every develo
 
 To say Firefox is slower than Chromium is, in my experience, sometimes true, sometimes not. The two tend to be a bit like race horses that are neck and neck, one occasionally inching ahead of the other only to be overtaken again a month later. 
 
-The problem is, for those releases where Firefox is noticeably slower it can be painful to move back to Chromium, which lacks tools I use everyday, like Responsive Design Mode or the pixel-based measurement tools.
+The problem is, for those releases where Firefox is noticeably slower, it can be painful to move back to Chromium, which lacks tools I use everyday, like Responsive Design Mode or the pixel-based measurement tools.
 
 Enter Blisk. Blisk is a customized build of Chromium that bolts on nearly everything you'll find in Firefox Developer Edition and half a dozen very useful tools you won't. In fact once you try Blisk there's a good chance you'll never use anything else for web development.
 
@@ -20,12 +20,12 @@ The downside to emulation of course is that you're not going to get, for example
 
 Another fantastically useful tool in Blisk is the built-in code "analytics" view, which checks your code through various syntax checkers and also looks at performance and cross-browser compatibility. It means you find bugs sooner than if you have to remember to run those tools on your own. It also makes it easier to diagnose the problem
 
-Blisk has a few features I haven't used extensively that might be handy in some workflows, including integration with a cloud-based back end that allows you to, among other things, quickly screenshot problem views and save the image to your Blisk account for sharing with team members. There's also a video recording tool if you need to demonstrate a bug in animation.
+Blisk has a few features I haven't used extensively that might be handy in some workflows, including integration with a cloud-based back end that allows you to, among other things, quickly screenshot problem views and save the images to your Blisk account for sharing with team members. There's also a video recording tool if you need to demonstrate a bug in animation.
 
 Blisk is also planning to integrate with outside services that would make it possible, for instance, to screenshot a bug and file it to your team's Bugzilla tracker. The integration isn't baked in yet, but it makes Blisk worth keeping an eye on even if you don't jump on it right now.
 
 While Blisk has some very useful stuff, it's not yet available for my main development platform -- Linux. Thankfully, while Blisk does add some extras like the synced scrolling and code checking, I've found that most of its features can be replicated in Chrome proper with a few add-ons. If you're a fellow Linux user or you just don't want a dedicated development browser, there are Chromium add-ons that can do some of these things without needing to install Blisk. For instance <a href="http://re-view.emmet.io/">Emmet Re:view</a> offers a similar take on the built-in Chrome device emulator.
 
-The auto-refresh feature is harder to get. It will require a tool like <a href="https://www.browsersync.io/docs"<>Browsersync</a>, which turn requires you first install Node.js. On the plus side Browsersync will work in any browser.
+The auto-refresh feature is harder to get. It will require a tool like <a href="https://www.browsersync.io/docs"<>Browsersync</a>, which in turn requires you first install Node.js. On the plus side Browsersync will work in any browser.
 
 Still, while you can get close to Blisk, it's unquestionably easier to just download Blisk and get to work.
diff --git a/whyarch.txt b/whyarch.txt
index 9c56d33..6b6f01c 100644
--- a/whyarch.txt
+++ b/whyarch.txt
@@ -1,29 +1,29 @@
-Dig through the annals of Linux coverage and you'll find a surprising amount of coverage of some pretty obscure distros. Flashy new distros like Elementary OS and Solus garner attention for their slick interfaces and anything shipping with a MATE desktop gets coverage by simple virtual of using MATE. 
+Dig through the annals of Linux journalism and you'll find a surprising amount of coverage of some pretty obscure distros. Flashy new distros like Elementary OS and Solus garner attention for their slick interfaces, and anything shipping with a MATE desktop gets coverage by simple virtue of using MATE. 
 
-Thanks to television shows like Mr Robot I full expect coverage of even Kali Linux to be on the uptick soon.
+Thanks to television shows like Mr Robot I fully expect coverage of even Kali Linux to be on the uptick soon.
 
 In all that coverage though there's one very widely used distro that's almost totally ignored -- Arch Linux.
 
-Arch gets very little coverage for a several reasons, not the least of which is that it's somewhat different to install and requires that you feel comfortable with the command line to get it working. Worse, from the point of view of anyone trying to appeal to mainstream users, that difficulty is by design -- nothing keeps the noobs out like a daunting install process. 
+Arch gets very little coverage for a several reasons, not the least of which is that it's somewhat difficult to install and requires that you feel comfortable with the command line to get it working. Worse, from the point of view of anyone trying to appeal to mainstream users, that difficulty is by design -- nothing keeps the noobs out like a daunting install process. 
 
 It's a shame though because once the installation is complete, Arch is actually, in my experience anyway, far easier to use than any other Linux distro I've tried.
 
 But yes, installation is a pain. Hand partitioning, hand mounting and generating your own fstab files takes more time and effort than clicking "install" and merrily heading off to do something else. But the process of installing Arch teaches you a lot. It pulls back the curtain so you can see what's behind it. In fact it makes the curtain disappear entirely. In Arch you are the person behind the curtain.
 
-In addition to its reputation for being difficult to install, Arch is justly revered for its customizability, though this is somewhat misunderstood. There is no "default" desktop in Arch. What you want installed on top the base set of Arch packages is entirely up to you. 
+In addition to its reputation for being difficult to install, Arch is justly revered for its customizability, though this is somewhat misunderstood. There is no "default" desktop in Arch. What you want installed on top of the base set of Arch packages is entirely up to you. 
 
 While you can see this as infinite customizability, you can also see it as totally lacking in customization. For example, unlike say Ubuntu, there is almost no patching or customization happening in Arch. Arch developers simply pass on what upstream developers have released, end of story. For some this good, you can run "pure" GNOME for instance. But in other cases some custom patching can take care of bugs that upstream devs might not prioritize.
 
-The lack of a default set of applications and desktop system also does not make for tidy reviews, or reviews at all really since what I chose to install will be different than what you choose. I happen to chose a very minimal setup of bare Openbox, tint2 and dmenu. You might prefer the latest release of GNOME. We'd both be running Arch, but our experience of it would be totally different. This is of course true of any distro, but most others have a default desktop at least.
+The lack of a default set of applications and desktop system also does not make for tidy reviews, or reviews at all really since what I chose to install will be different than what you choose. I happened to choose a very minimal setup of bare Openbox, tint2 and dmenu. You might prefer the latest release of GNOME. We'd both be running Arch, but our experiences of it would be totally different. This is of course true of any distro, but most others have a default desktop at least.
 
 Still there are common elements that together can make the basis of an Arch review. There is, for example, the primary reason I switched -- Arch is a rolling release distro. This means two things. First, the latest kernels are delivered as soon as they're available and reasonably stable. This means I can test things that are difficult to test with other distros. The other big win for a rolling distro is that all updates are delivered when they're ready. Not only does this mean newer software sooner, it means there's no massive system updates that might break things.
 
-Many people feel that Arch is less stable because its rolling, but in my experience over the last nine months I would argue the opposite. 
+Many people feel that Arch is less stable because it's rolling, but in my experience over the last nine months I would argue the opposite. 
 
-I have yet to break anything with an update. I did once have to rollback because my /boot partition wasn't mounted when I updated and changes weren't written, but that was pure user error. Bugs that do surface (like some regressions related to the trackpad on a Dell XPS laptop I was testing) are fixed and updates available much faster than they would be with a non-rolling distro. In short, I've found Arch's rolling release updates to be far more stable than anything else I've been using along side it. The only caveat I have to add to that is read the wiki and pay close attention to what you're updating.
+I have yet to break anything with an update. I did once have to rollback because my /boot partition wasn't mounted when I updated and changes weren't written, but that was pure user error. Bugs that do surface (like some regressions related to the trackpad on a Dell XPS laptop I was testing) are fixed and updates are available much faster than they would be with a non-rolling distro. In short, I've found Arch's rolling release updates to be far more stable than anything else I've been using along side it. The only caveat I have to add to that is read the wiki and pay close attention to what you're updating.
 
-This brings us to the main reason I suspect that Arch's appeal is limited -- you have to pay attention to what you're doing. Blindly updating Arch is risky. But it's risky with any distro you've just been conditioned to think it's not because you have not choice.
+This brings us to the main reason I suspect that Arch's appeal is limited -- you have to pay attention to what you're doing. Blindly updating Arch is risky. But it's risky with any distro; you've just been conditioned to think it's not because you have no choice.
 
-Which leads me to the other major reason I embraced Arch -- the <a href="https://wiki.archlinux.org/index.php/Arch_Linux">Arch Philosophy</a>. The part in particular what I find appealing is this bit: "[Arch] is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems."
+Which leads me to the other major reason I embraced Arch -- the <a href="https://wiki.archlinux.org/index.php/Arch_Linux">Arch Philosophy</a>. The part in particular that I find appealing is this bit: "[Arch] is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems."
 
 As Linux moves further into the mainstream developers seem to feel a greater need to smooth over all the rough areas -- as if mirroring the opaque user experience of proprietary software were somehow the apex of functionality. Strange though it sounds in this day and age there are many of us who actually prefer to configure things ourselves. In this sense Arch may well be the last refuge of the DIY Linux user.