Documentation polishing.

diff --git a/history.adoc b/history.adoc
index 43bc350286a24892b1261285e09135c27e0d0e09..24f7fcf020ec652c189a7d91798216555c87ca94 100644 (file)
--- a/history.adoc
+++ b/history.adoc
@@ -23,9 +23,11 @@ in the 1995 release of Adventure 2.5, also known as 430-point Adventure
 
 The earliest port to C was by Jim Gillogly under an early Unix running
 at the Rand Corporation in 1977; this version was later, and still is,
-included in the BSD Games collection.  It was blessed by Crowther and
-Woods and briefly marketed in 1981 under the name "The Original
-Adventure".
+included in the BSD Games collection.  I have it from Don Woods directly
+that "[Jim Gillogly] was one of the first to request and receive a copy 
+of the source" but that Woods did not actually know of the BSD port
+until I brefed him on it in 2017.  (This contradicts some implications
+in third-party histories.)
 
 Many other people ported and extended the game in various directions.
 A notable version was the first game shipped for the IBM Personal

diff --git a/notes.adoc b/notes.adoc
index 8fbbbd54ef9708380dc170a90c215e4c47301f19..d06f170f7661d60b96f34e618bfe7980245684ec 100644 (file)
--- a/notes.adoc
+++ b/notes.adoc
@@ -101,8 +101,8 @@ necessarily pretty ugly by modern standards. Encryption and
 checksumming have been discarded - it's pointless to try
 tamper-proofing saves when everyone has the source code.
 
-A -r command-line been added. When it is given (with a file path
-argument) it is functionally equivalent to a RESTORE command.
+A -r command-line option has been added. When it is given (with a file
+path argument) it is functionally equivalent to a RESTORE command.
 
 == Translation ==
 
@@ -113,7 +113,7 @@ ugly and quite unreadable.
 Jason Ninneman and I have moved it to what is almost, but not quite,
 idiomatic modern C.  We refactored the right way, checking correctness
 against a comprehensive test suite that we built first and verified
-with coverage tools (we have over 95% coverage, with the remaining
+with coverage tools (we have over 98% coverage, with the remaining
 confined to exception cases that are very difficult to reach). This is
 what you are running when you do "make check".