diff --git a/Divorce-Your-Linux-Admin.rst b/Divorce-Your-Linux-Admin.rst
index 7797f48..1b9264d 100644
--- a/Divorce-Your-Linux-Admin.rst
+++ b/Divorce-Your-Linux-Admin.rst
@@ -70,11 +70,11 @@
 a Unix-base (FreeBSD 4.4), they only partly implemented the shell
 tools everyone had come to know and love.  The ``homebrew`` project
 got spun up to allow any OSX user to install the command line
-applications they knew and loved from Unix.  ``homebrew`` is
-essentially a userland package management system which can be run and
-modified without superuser power.  Many of these packages (these days,
-perhaps all, I haven't checked) actually download a pre-compiled
-version under ``/usr/local``.
+applications they knew from Unix.  ``homebrew`` is essentially a
+userland package management system which can be run and modified
+without superuser power.  Many of these packages (these days, perhaps
+all, I haven't checked) actually download a pre-compiled version under
+``/usr/local``.
 
 This ended up being pretty popular with advanced Mac users.  So much
 so, that a derivative project, ``linuxbrew``, got spun up to take the
@@ -181,7 +181,7 @@
   4) When you're all done installing and configuring your
      ``linuxbrew`` environment, you just ``tar`` it off somewhere
      safe.  You can then untar it onto any other Linux machine (with
-     a reasonably current kernel) so long as you do so at the *same
+     a reasonably similar kernel) so long as you do so at the *same
      directory location under which it was built*.
 
      This lends itself nicely to automated deploys via tools like
@@ -225,7 +225,7 @@
       environment.  But this badly broke the ``emacs`` build which had
       fits because the way the OS was allocating memory.  The fix is
       to use the above argument to give the container full access to
-      all the system call.  You do *not* want to do this in normal
+      all the system calls.  You do *not* want to do this in normal
       container operations.  This is strictly for building things.
       More information on this here:
 
@@ -308,7 +308,7 @@
            brew doctor       # Check to make sure things look OK
 
     5) Now we can start installing our desired packages.  Note that
-       we are now using *the ``linuxbrew`` compiler chain*, NOT the
+       we are now using *the* ``linuxbrew`` *compiler chain*, NOT the
        system tools::
 
            brew install coreutils bash bc gnu-sed awk flex bison tree htop the_silver_searcher gnu-which less # also installs python2
@@ -328,7 +328,7 @@
 You should now be able to install and use this tool tree on a
 docker, VM, or physical Linux instance by doing this::
 
-    tar -xzvf /shared/full-linuxbrew.tar.gz /opt/TundraWare/tools
+    tar -xzvf /shared/full-linuxbrew.tar.gz -C /
     export PATH="/opt/TundraWare/tools/bin:/opt/TundraWare/tools/sbin:$PATH"