Miscellaneous docs changes.

Author: briandominick

README.adoc

@@ -7,12 +7,17 @@
 :append_or_impose: Prepend items with `+` to indicate they should be appended to existing labels. Items without `+` will only be used for issues with no `tags` designated.
 ifdef::env-github[]
 :icons: font
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
 endif::[]
 
 
 == Overview
 
-_Issuer_ lets you define all your work tickets in one place as YAML, apply defaults, and post them to GitHub Issues in bulk.
+_Issuer_ lets you define all your GitHub Issues work tickets in one place as YAML, apply defaults, and post them to GitHub Issues in bulk.
 
 === Features
 
@@ -28,6 +33,22 @@ Future plans include extending this capability to *Jira*, *GitLab* Issues, GitHu
 
 toc::[]
 
+=== Who Is This For?
+
+This tool is oriented as much for _project managers_ as it is for _software developers_, but the target audience is probably *people who manage software development cycles*, especially using Git tools.
+
+So if you are a project manager, _product_ manager, technical writer or other role that participates in the _planning_ of _any_ kind of project.
+
+[NOTE]
+Ironically, issuer does not require be installed on your local workstation.
+The only direct use of Git would be if you commit and share the batch-configuration file with your team.
+
+This tool is great at creating "`stub`" issues for entire teams, based on user-story documents, task lists, or other planning documents.
+Once you convert such documents to our special YAML-based definition format (IMYML), use `issuer` to post them to your GitHub Issues system via GitHub's API.
+
+Individual issue entries can be as basic or as detailed as you wish.
+They may consist of as little as just a title (summary) line, or that plus an assignee responsible for filling out the rest and add metadata.
+Or they can be complete with labels, milestones, a type designation, and a complete explanation of the issue.
 
 == Installation
 
@@ -453,7 +474,7 @@ Logs are simply kept for easy reversal of mis-postings.
 I developed the 0.1.0 version of this application after trying to use GitHub Copilot to automatically bulk-create issue tickets, which it promises to be able to do but failed me pretty hard at it.
 
 That facility seems like a perfectly inappropriate use of generative AI.
-It accepted my plan request and pre-drafted ticket content, but then it wanted me to manually add labels and milestones to them, as well as manually click *create* on each one -- even though I had already taken the time to plan and instruct the milestones and labels and the contents were fullly prepared.
+It accepted my plan request and pre-drafted ticket content, but then it wanted me to manually add labels and milestones to them, as well as manually click *create* on each one -- even though I had already taken the time to plan and instruct the milestones and labels and the contents were fully prepared.
 
 Additionally, I find myself using different issue-management systems (Jira, GitLab Issues, etc), so I wanted a more platform-agnostic way to handle this problem.
 With that in mind, I have left the Ruby API and the IMYML model fairly "`generic`" for extensibility.
@@ -462,7 +483,7 @@ I will probably adapt the API to other systems in future releases, and I welcome
 === Methodology Confession
 
 I should note up front that this is the closest I have come to "`vibe coding`" anything bigger than a local script, let alone shippable production code.
-Nevertheless, I intervened to make substantial and specific changes at least 100 times, and I rearranged major aspects of the codebase.
+Nevertheless, I intervened to make substantial and specific changes at least 100 times before the 0.1.0 release alone, and I rearranged major aspects of the codebase.
 
 I designed the IMYML format and the CLI up front, then I let Claud 4 (via GH Copilot) draft most of the code.
 It committed lots of rookie mistakes during this process, and it even confessed to "`cargo-cult programming`" when I pointed out it was introduing some anti-patterns.