M README → README

@@ -28,6 +28,8 @@ i know how impossible they all are firsthand, i have 6+ years
   of painful, painful experience. i wrote zoa to use on my personal
 systems, because i hate the primary config management tools a lot. 
 
+               also, i <3 shell :D
+
 
 
              ~~ zoa doesn't pretend ~~
@@ -39,8 +41,8 @@ an exercise to the user.
 
       zoa doesn't pretend. zoa is not idempotent. zoa
       is not declarative. it assumes your state changes
-      over time, and zoa makes it easy to track those
-      changes. you won't have to look at horrible docs
+      over time, and zoa makes it easy to keep up with those
+      changes. you won't have to look at horrible doc websites
       or commit a week to learning a god
                                        damned
                                         stupid
@@ -56,24 +58,23 @@ 
       zoa adheres to standards, and uses well-known
       distro conventions.
 
-      because it's easy. and simple. and honestly,
-      it's not very big.
-
-    chef & ansible & puppet pretend that you can
-    work around bad packaging & applications
-    with config management!
-
-      zoa doesn't! if a package is packaged poorly
-      or an application sucks to install, it will
-      equally suck in zoa. sorry.
+      zoa is easy. and simple. and honestly,
+      quite a smol guy
 
     the other tools want to do a lot - search across
     your nodes, deploy via their tooling, automate
-    testing, etc
-  
+    testing, manage AWS resources?!?!?  
+
       zoa is only concerned with _managing configuration_
 
+      _on servers_
+
       and nothing else. forever.
+
+    the other tools break constantly because they
+    try to do everything.
+
+      zoa breaks rarely because it does almost nothing.