Fix errors in section-headers

Author: jmdyck

docs/07-structured-objects.md

@@ -733,7 +733,7 @@ occurs.
 3. What actually gets inserted into the structure being built are the 
 elements of the structure returned by the `FORM`-like evaluation.
 
-### 7.7.3 Examples [1]
+### 7.7.3. Examples [1]
 
     <SET ZOP '![2 3 4]>$
     ![2 3 4!]

docs/09-functions.md

@@ -161,7 +161,7 @@ However, the desired effect could be achieved by
 
     <DEFINE OK (A B "AUX" (D <TUPLE !.A>) (C <REST .D>)) ...>
 
-## 9.3 "AUX" [1]
+## 9.3. "AUX" [1]
 
 `"AUX"` (or `"EXTRA"` -- they're totally equivalent) are `STRING`s 
 which, placed in an argument `LIST`, serve to dynamically allocate 

docs/10-looping.md

@@ -174,7 +174,7 @@ last value returned by *loopf*. If any of the *si* structures is
 empty, to that *loopf* is never invoked, *finalf* is applied to **no** 
 arguments; if *finalf* is a `FALSE`, `MAPF` returns `#FALSE ()`.
 
-### 10.2.2 MAPR [1]
+### 10.2.2. MAPR [1]
 
     <MAPR finalf loopf s1 s2 ... sN>
 

docs/11-input-output.md

@@ -134,7 +134,7 @@ This `SUBR` is especially useful in conjunction with (section 11.2.8)
 those elements of a `CHANNEL` which specify the number of characters
 per output line and the current position on an input line.
 
-## CHANNEL (the TYPE)
+## 11.2. CHANNEL (the TYPE)
 
 I/O channels are dynamically assigned in MDL, and are represented by
 an object of `TYPE` `CHANNEL`, which is of `PRIMTYPE` `VECTOR`. The
@@ -298,6 +298,10 @@ following:
 
 *element-number: type interpretation*
 
+#### 11.2.8.1 Output CHANNELs
+
+The contents of a CHANNEL used for output are as follows:
+
 | element-number | type     | interpretation                    |
 |----------------|----------|-----------------------------------|
 |   -1           | `LIST`   | transcript channel(s) (see below) |
@@ -439,7 +443,7 @@ such. *channel* is optional, `.OUTCHAN` by default, and its slots for
 current character position (number 14) and current line number (16)
 are not updated. `IMAGE` returns *fix*.
 
-## 11.5 Dumped I/O
+## 11.5. Dumped I/O
 
 ### 11.5.1. Output: GC-DUMP
 
@@ -725,7 +729,7 @@ the `CHANNEL` given to `READSTRING` is open in `"READ"` mode to a
 pseudo-terminal, reading also stops if and when no more characters
 are available, that is, when `READCHR` would return `-1`.
 
-## 11.8.1. ECHOPAIR
+### 11.8.1. ECHOPAIR
 
     <ECHOPAIR terminal-in:channel terminal-out:channel>
 

docs/14-data-type-declarations.md

@@ -380,7 +380,7 @@ to date several instances of the full `DECL`.
 
 ## 14.5. Global DECLs
 
-### 15.4.1. GDECL and MANIFEST
+### 14.5.1. GDECL and MANIFEST
 
 There are two ways to declare `GVAL`s for the `DECL`-checking
 mechanism. These are through the `FSUBR` `GDECL` ("global

docs/15-lexical-blocking.md

@@ -280,7 +280,7 @@ ATOM. If there is no such `ATOM`, `REMOVE` returns `#FALSE ()`. Also,
 removes *atom* from its `OBLIST`, if it is on one. It returns *atom*
 if it was on an `OBLIST`; otherwise it returns `#FALSE ()`.
 
-### 15.7.6 INSERT
+### 15.7.6. INSERT
 
     <INSERT string-or-atom oblist>
 

docs/19-compiled-programs.md

@@ -104,7 +104,7 @@ is written, so that the code is not duplicated on disk. A purified
 `RSUBR` must use `RGLOC` ("relative GLOC") instead of `GLOC`. `RGLOC`
 produces objects of `TYPE` `LOCR` instead of `LOCD`.
 
-# 19.5. TYPE-C and TYPE-W
+## 19.5. TYPE-C and TYPE-W
 
 In order to handle user `NEWTYPE`s reasonably, the internal `TYPE`
 codes for them have to be able to be different from one MDL run to

docs/22-storage-management.md

@@ -187,7 +187,7 @@ re-use. The "copying" algorithm maps the inferior process's address
 space into MDL's own, replacing old garbagey with the new compact
 storage, and the inferior process is destroyed.
 
-## 22.5 GC
+## 22.5. GC
 
     <GC min:fix exh?:false-or-any ms-freq:fix>
 
@@ -361,7 +361,7 @@ useful for unlinking `RSUBR`s. `SUBSTITUTE` returns *old* as a favor:
 unless you hang onto *old* at that point, it will be
 garbage-collected.
 
-## 22.9.2 PURIFY
+### 22.9.2. PURIFY
 
     <PURIFY any-1 ... any-N>