Clarity

Author: hackerb9

README.md

@@ -37,8 +37,7 @@ files in ASCII (plain text) or in a _“tokenized”_ format where the
 keywords — such as `FOR`, `IF`, `PRINT`, `REM` — are converted to a
 single byte. The Model 100 automatically tokenizes an ASCII program
 when it is `LOAD`ed so that it can be `RUN` or `SAVE`d. The tokenized
-format saves space and loads faster, but where it is tokenized can
-matter.
+format saves space and loads faster.
 
 ### The problem
 
@@ -90,14 +89,14 @@ The primary two filename extensions are:
     tokenizers like this, one was expected to know that ASCII BASIC
     files had to be renamed to .DO before downloading to a Model 100.
 
-
 BASIC programs that use `PEEK`, `POKE`, or `CALL` typically only work
 on one specific model of portable computer, even when the BASIC
-language and tokenization is identical. The only two models which have
-the same memory map are the Model 100 and and Tandy 102. Using POKE or
-CALL on the wrong model can crash badly, possibly losing files. To
-avoid this, when sharing BASIC programs over the network, filename
-extensions can indicate which model a program will work on:
+language and tokenization is identical. (The only two models which
+have the same memory map are the Model 100 and and Tandy 102.) Using
+POKE or CALL on the wrong model can crash badly, possibly losing
+files. To avoid this, when sharing BASIC programs over the network,
+filename extensions are sometimes used to indicate which model a
+program will work on:
 
   * `.100` An ASCII BASIC file that includes POKEs or CALLs specific
 	  to the Model 100 or Tandy 102.
@@ -198,6 +197,8 @@ $ tokenize PROG.DO
 Tokenizing 'PROG.DO' into 'PROG.BA'
 ```
 
+<details><summary>Click to see more examples</summary><ul>
+
 #### Example 2: Overwrite or rename
 
 ``` bash
@@ -240,6 +241,7 @@ from, debug, and improve it._
 
 </ul>
 
+</ul></details>
 
 ### Running m100-tokenize and friends manually
 
@@ -381,17 +383,21 @@ program (currently) works only for the former, not the latter.
 
 The three Radio-Shack portables (Models 100, 102 and 200), the Kyocera
 Kyotronic-85, and the Olivetti M10 all share the same tokenized BASIC.
-That means one .BA program _might_ work for any of them, presuming the
-program do not rely on CALL, PEEK, or POKE. However, the NEC family of
-portables -- the PC-8201, PC-8201A, and PC-8300 -- run N82 BASIC which
-has a different tokenization format.
+That means one tokenize .BA file _might_ work for any of those,
+presuming the program does not use CALL, PEEK, or POKE. However, the
+NEC family of portables -- the PC-8201, PC-8201A, and PC-8300 -- run
+N82 BASIC, which has a different tokenization format. A tokenized N82
+BASIC file cannot run on an M100 computer and vice versa, even for
+programs which share the same ASCII BASIC source code.
 
 ### Checksum differences are not a compatibility problem
 
 The .BA files generated by `tokenize` aim to be exactly the same, byte
 for byte, as the output from tokenizing on a Model 100 using `LOAD`
-and `SAVE`. There are some bytes, however, which can and do change but
-do not matter.
+and `SAVE`. There are some bytes, however, which can change and should
+be ignored when testing if two tokenized programs are identical. 
+
+<details><summary>Click to read details on line number pointers...</summary><ul>
 
 A peculiar artifact of the [`.BA` file format][fileformat] is that it
 contains pointer locations offset by where the program happened to be
@@ -419,6 +425,8 @@ described below.
 
 [fileformat]: http://fileformats.archiveteam.org/wiki/Tandy_200_BASIC_tokenized_file "Reverse engineered file format documentation"
 
+</ul></details> <!-- Line number pointers -->
+
 ## Why Lex?
 
 This program is written in