docs: style fixes

docs/source/examples/working_with_pow_files.rst

@@ -71,28 +71,27 @@ If you need to write more complex actions, you can leverage multiline commands:
     <https://en.wikipedia.org/wiki/Here_document>`_
 
 
-Keep things tidy
-----------------
+Keeping Things Tidy
+-------------------
 
-Sometimes things grow, and keep things tidy it's the only way to mantain the
-hole thing.
+Sometimes things grow, and keeping things tidy is the only way to mantain the
+whole thing.
 
-You can distribute your endpoints among several pow files. And you can keep the
-hole thing documented in one html server with kapow.
+You can distribute your endpoints in several pow files.  And you can keep the
+whole thing documented in one html file, served with *Kapow!*.
 
 .. code-block:: console
     :linenos:
 
     $ cat index.pow
-    #!/bin/bash
+    #!/usr/bin/env bash
 
     kapow route add / - <<-'EOF'
-        cat howto.html | kapow set /response/body
+    	cat howto.html | kapow set /response/body
     EOF
 
     source ./info_stuff.pow
     source ./other_endpoints.pow
 
-As you can see the pow files can be imported into another pow files using
-source. In fat a pow file it's a regular shell file.
-
+As you can see, the `pow` files can be imported into another `pow` file using
+source.  In fact, a `pow` file is just a regular shell script.