From 4b82a2e4181bc6b6dfb96f0e806c6b1e67a0565c Mon Sep 17 00:00:00 2001 From: pancho horrillo Date: Mon, 24 Feb 2020 15:13:53 +0100 Subject: [PATCH] docs: style fixes --- .../examples/working_with_pow_files.rst | 21 +++++++++---------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/docs/source/examples/working_with_pow_files.rst b/docs/source/examples/working_with_pow_files.rst index 257625e..a7fe193 100644 --- a/docs/source/examples/working_with_pow_files.rst +++ b/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: `_ -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.