various doc fixes apply patch from gxt:

Here's the full patch:

 README.org | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.org b/README.org
index 7650cce..dad46c5 100644
--- a/README.org
+++ b/README.org
@@ -30,7 +30,7 @@ project from a single file, as in the case of this project, itself.
   Writing your project's README in org is nearly identical to writing
   (directly) in Markdown.  Org includes more expressive syntax to
   describe more flexible intents.  For example, org allows us to
-  conditionally render parts of a document based on the target extort
+  conditionally render parts of a document based on the target export
   format (e.g. Markdown, HTML, or "raw" text) and to specify which
   file code in a given source block is for/from.

@@ -111,7 +111,7 @@ following describe how to use them.
      ORG_GIT_TANGLE=ORG_GIT_EXPORT
    #+END_EXAMPLE

-   Edit it to another file or list as for [[Selecting Files to Export][setting ORG_GIT_EXPORT]].
+   Edit it to another file or list as for [[Selecting Files to Export][setting ~ORG_GIT_EXPORT~]].

    #+BEGIN_EXAMPLE sh
      ORG_GIT_TANGLE="docs/README.org examples/README.org"
@@ -224,7 +224,7 @@ To make and test your changes
    This sets up a couple of environment variables:
    * ~ORG_GIT_EXPORT~ a project root relative file path or a quoted, space separated list of these
    * ~ORG_GIT_TANGLE~ same
-   * ORG_GIT_FORMAT one or more (quoted, space separated) among ~md~, ~html~, and ~txt~.
+   * ~ORG_GIT_FORMAT~ one or more (quoted, space separated) among ~md~, ~html~, and ~txt~.

    The programs created by tangling this ~README.org~ each have these
    variables defined when running.  This program (the ~.env~ file) is
--

noop commit for testing

give explicit link descriptions so they render nicely in HTML

support tangle, add .env

Notwithstanding tests, this completes everything I've immediately
planned for this project.

noop change for hook testing

initial commit