X-Git-Url: https://jxself.org/git/?p=open-adventure.git;a=blobdiff_plain;f=notes.adoc;h=c1b5c849603b61edc93074c9b4db53ae8749a3dd;hp=8fbbbd54ef9708380dc170a90c215e4c47301f19;hb=d5d6a3e02d344ed4097a38f54ccf6757e627a1f6;hpb=c8cac18f42ab4e5e060d632fcde29c8c74354b53

diff --git a/notes.adoc b/notes.adoc
index 8fbbbd5..c1b5c84 100644
--- a/notes.adoc
+++ b/notes.adoc
@@ -58,6 +58,9 @@ Bug fixes:
   incorrect most places it appeared and has been replaced by "A crystal 
   bridge spans the fissure." (timeless present).
 
+* Under odd circumstances (dropping rug or vase outdoors) the game could
+  say "floor" when it should say "ground" (or "dirt", or something).
+
 By default, advent issues "> " as a command prompt.  This feature
 became common in many variants after the original 350-point version,
 but was never backported into Crowther & Woods's main line before now.
@@ -73,6 +76,9 @@ Unrecognized words are no longer truncated to 5 characters and
 uppercased when they are echoed. The "-o" (oldstyle) option restores
 this behavior.
 
+Typing a numeric liteteral to the command prompt no longer triggers a
+fatal error. This change is reverted by the oldstyle option. 
+
 A "seed" command has been added.  This is not intended for human use
 but as a way for game logs to set the PRNG (pseudorandom-number generator) so
 that random events (dwarf & pirate appearances, the bird's magic word)
@@ -101,8 +107,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,8 +119,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
-confined to exception cases that are very difficult to reach). This is
+with coverage tools (there is effectively 100% code coverage). This is
 what you are running when you do "make check".
 
 The move to modern C entailed some structural changes.  The most