Fix some more links

01-01-welcome.html

@@ -65,13 +65,6 @@ <h2>How to exploit this User Guide</h2>
         in its own Chapter.</p>
 
 
-    <p>The number of the current Section and Chapter appears at the top corner of
-        each page, with the page number printed at the bottom corner. For example,
-        this is page one of Section 1, Chapter 1, so if it appeared in the Index, it
-        would be referred to as <a href="01-01-welcome.html">1.1.01</a>, whereas the first page
-        of Chapter 8 in Section 5 would be referred to as <a href="5/569.html">5.8.01</a>.</p>
-
-
     <p>However, the printed word can never convey the look and feel of a
         programming technique, which is why everything that you read in these pages
         can also be demonstrated and analysed on screen, at the touch of a button!
@@ -113,39 +106,29 @@ <h2>How to exploit this User Guide</h2>
     <p>Printed examples of AMOS Professional programs appear in
         special type, and
         they are indented on the page like this:</p>
-    <pre>
-E&gt;AMOS=1
-  Print AMOS
-</pre>
+<code class="prefix edit">
+AMOS=1
+Print AMOS
+</code>
 
     <p>AMOS Professional provides over seven hundred command words
-        ready to be
-        exploited in your own programming routines, and many of them are
-        staggeringly
-        powerful. Because these command words are so important, they are
-        printed in
-        prominent type throughout this User Guide. When they appear in the main
-        body
-        of the text, they are printed in capital letters. For example the
-        simple
-        command word for printing items appears as PRINT. Where a command word
-        is
-        introduced for the first time in the User Guide, it is indented on the
-        page
-        and printed in large bold type, along with a summary of its use. For
+        ready to be exploited in your own programming routines, and many of them are
+        staggeringly powerful. Because these command words are so important, they are
+        printed in prominent type throughout this User Guide. When they appear in the main
+        body of the text, they are printed in capital letters. For example the
+        simple command word for printing items appears as PRINT. Where a command word
+        is introduced for the first time in the User Guide, it is indented on the
+        page and printed in large bold type, along with a summary of its use. For
         example:</p>
 
     <p><b>PRINT</b><br>
         <i>instruction: print items on screen</i><br>
         <b>Print</b> items</p>
 
     <p>Everything else is fully explained as it is introduced, or is
-        completely
-        self-explanatory. Now that AMOS Professional has been introduced to
-        you, and
-        before introducing AMOS Professional to your Amiga, here are a few
-        words of
-        welcome from some of the key players in the team.</p>
+        completely self-explanatory. Now that AMOS Professional has been introduced to
+        you, and before introducing AMOS Professional to your Amiga, here are a few
+        words of welcome from some of the key players in the team.</p>
 </section>
 
 <section id="02-a-few-words-of-welcome">

04-01-the-editor.html

@@ -678,7 +678,7 @@ <h2 class="menu-line">AMOS</h2>
             Each extension has its own title screen, and the list can be examined via the [Prey] and [Next]
             buttons. Click on [Cancel] to return to the Editor Screen. You are free to create your own
             extensions for use with the AMOS Professional system, and more information on this topic
-            can be found in <a href="14/1424.html">Appendix D</a> of this User Guide.</P>
+            can be found in <a href="14-appendix-d-extensions.html">Appendix D</a> of this User Guide.</P>
 
         <P><b>[Load Accessory]</b><BR>
 
@@ -900,7 +900,7 @@ <h2 class="menu-line">Editor</h2>
 
             This option is used to load a machine language routine directly into the selected
             procedure. This procedure will now be closed and its existing contents will be replaced by the new code.
-            Please see <a href="14/1401.html">Appendix A</a> for full details.</p>
+            Please see <a href="14-appendix-a-machine-code.html">Appendix A</a> for full details.</p>
 
         <p><b>[Windows]</b><BR>
 
@@ -1533,12 +1533,12 @@ <h2 class="menu-line">Config</h2>
         <P>[Menu Messages]<BR>
             This option allows you to change the default text of the menu messages to your own wording,
             or into a non-English language. Menus are explained in <a href="06-05-menus.html">Chapter 6.5</a>, and the menu editor is
-            examined in <a href="13/1322.html">Chapter 13.3</a>.</P>
+            examined in <a href="13-03-menu-editor.html">Chapter 13.3</a>.</P>
 
         <P>[Dialog messages]<BR>
             Similarly, the wording of the AMOS Professional dialogue boxes can be changed. The whole
             of <a href="09-01-amos-interface.html">Section 9</a> of this User Guide is devoted to dialogue boxes, buttons and icons,
-            and <a href="13/1346.html">Chapter 13.7</a> explains how to create your own resources.</P>
+            and <a href="13-07-resource-creator.html">Chapter 13.7</a> explains how to create your own resources.</P>
 
         <P>[Test-Time Messages]<BR>
             The information messages and error messages that appear when a program is tested can also

04-02-help.html

@@ -170,15 +170,7 @@ <h3>The AMOS Professional Monitor</h3>
     <p>This feature is used to get inside your programs, examine any AMOS professional routine,
         discover exactly what is happening, why it is happening and make a full report on screen.
         The Monitor not only offers help, it provides an instant diagnosis! All is explained in
-        <a href="12-01-the-monitor.html">Chapter 12.1</a>.</P>
-
-    <h3>Continuing Support</h3>
-
-    <p>It has always been our policy to provide as much help and support to AMOS users as
-        possible,and AMOS Professional programmers are offered this assistance too. Future Support is dealt
-        with in <a href="...14/1468.html">Appendix I</a>, at the back of this User Guide, and you may well want to join the
-        network of world-wide clubs and groups offering a huge range of help and support to AMOS
-        Professional programmers. The services of the AMOS PD Library are detailed in <a href="14/1467.html">Appendix H</a>.</P>
+        <a href="12-01-monitor.html">Chapter 12.1</a>.</P>
 </section>
 
 

05-09-memory-banks.html

@@ -600,7 +600,7 @@ <h2>Automatic bank grabbing</h2>
 
     <p>
         No loading and saving are necessary, everything is handled by AMOS Professional, and your
-        working life is made that much easier! An example of this technique is featured in <a href="13/1346.html">Chapter 13.7</a>.</p>
+        working life is made that much easier! An example of this technique is featured in <a href="13-02-object-editor.html#05-the-grabber">Chapter 13.2</a>.</p>
 </section>
 
 <section id="12-creating-your-own-utilities">

06-03-screen-effects.html

@@ -302,7 +302,7 @@ <h3 class="command" id="i-rainbow">RAINBOW</h3>
         Please note that normally only one rainbow at a time can be displayed at a particular scan line,
         and the one with the lowest identification number will be drawn in front of any others
         However, experienced Amiga users will be able to start more than one rainbow at the same line,
-        using the Copper. See <a href="14/1442.html">Appendix F</a> for an explanation of this technique.</p>
+        using the Copper. See <a href="14-appendix-f-copper-lists.html">Appendix F</a> for an explanation of this technique.</p>
 
     <h3 class="command" id="i-rainbow-del">RAINBOW DEL</h3>
     <p><i>instruction: delete a rainbow</i><br>
@@ -354,7 +354,7 @@ <h2>The copper list</h2>
         created by programming the copper, but the copper list is notoriously difficult to manipulate,
         and many competent programmers have failed to master its mysteries.</p>
 
-    <p>A full discussion of the copper lists may be found in <a href="14/1442.html">Appendix F</a> of this User Guide.</p>
+    <p>A full discussion of the copper lists may be found in <a href="14-appendix-f-copper-lists.html">Appendix F</a> of this User Guide.</p>
 </section>
 
 

07-01-hardware-sprites.html

@@ -361,12 +361,9 @@ <h2>The Sprite Palette</h2>
 
     <p>
         As has been explained, the hardware sprites used to create computed sprites will vary during
-        the course of your program, so it is vital that the three colours used by each pair of hardware</p>
-
-
-    <p>
+        the course of your program, so it is vital that the three colours used by each pair of hardware
         sprites are exactly the same. A procedure is provided to accomplish this, and it may be found
-        along with a host of other useful procedures, in <a href="14/1419.html">Appendix C</a>.</p>
+        along with a host of other useful procedures, in <a href="14-appendix-c-pal-and-ntsc.html" class="wrong-link">Appendix C</a>.</p>
 
     <h3 class="command" id="i-get-sprite-palette">GET SPRITE PALETTE</h3>
     <p><i>instruction: grab sprite colours into screen</i><br>

07-06-amal.html

@@ -401,7 +401,7 @@ <h3 class="command" id="amals-if">If</h3>
     <h2>Generating movement patterns</h2>
     <p>
         Elaborate movement patterns can be recorded directly into the AMAL memory bank, using the
-        AMAL Editor. This superb accessory is fully detailed in <a href="13/1335.html">Chapter 13.5</a>. To create less ambitious
+        AMAL Editor. This superb accessory is fully detailed in <a href="13-05-amal-editor.html">Chapter 13.5</a>. To create less ambitious
         movement patterns, AMAL loops can be used to great effect.</p>
 
     <p>
@@ -449,7 +449,7 @@ <h3 class="command" id="amali-play">PLay</h3>
         records a sequence of mouse movements and enters them directly into the AMAL memory
         bank. Once patterns have been defined in this way, they can be assigned to any Object on the
         screen, and that Object will reproduce your original patterns perfectly. the AMAL Editor is fully
-        explained in <a href="13/1335.html">Chapter 13.5</a>.</p>
+        explained in <a href="13-05-amal-editor.html">Chapter 13.5</a>.</p>
 
 
     <p>
@@ -1467,7 +1467,7 @@ <h2>The AMAL Editor</h2>
     <p>
         As a final reminder, the AMAL Editor is a vital accessory program for AMOS Professional
         programmers wishing to create detailed or complex movement patters. It is fully explained in
-        <a href="13/1335.html">Chapter 13.5</a>.</p>
+        <a href="13-05-amal-editor.html">Chapter 13.5</a>.</p>
 
 
 </section>

08-02-samples.html

@@ -31,7 +31,7 @@ <h1>Samples</h1>
         "live" sound effects and musical tones to be called up. If you have access to a hard drive or CD-
         ROM, the AMOS Professional Double Buffered Sampling system offers full exploitation of
         sampled sound. There is even a built-in "recording studio" ready to be used, and you can enjoy
-        the facilities of this Sample Bank Maker accessory, which is featured in <a href="13/1342.html">Chapter 13.6</a> of this User
+        the facilities of this Sample Bank Maker accessory, which is featured in <a href="13-06-sample-bank-maker.html">Chapter 13.6</a> of this User
         Guide.</p>
 
     <p>

09-04-interface-resources.html

@@ -32,7 +32,7 @@ <h1>Interface Resources</h1>
 
     <p>
         Each Interface program has access to a set of special resources held in an appropriate memory
-        bank. These resources can be created with the Resource Bank Maker, which has <a href="13/1346.html">Chapter 13.7</a>
+        bank. These resources can be created with the Resource Bank Maker, which has <a href="13-07-resource-creator.html">Chapter 13.7</a>
         devoted to it. Once defined, resources can be installed for use with the AMOS Professional
         Interface.</p>
 

10-06-arexx.html

@@ -112,6 +112,7 @@ <h2>Using AREXX</h2>
 <section id="02-arexx-compatible-instructions">
     <h2>AREXX-Compatible Instructions</h2>
 
+    <h3 class="command" id="i-arexx-open">AREXX OPEN</h3>
     <p>
         <i>instruction: open an AREXX communication port</i><br>
         <b>Arexx</b> Open "PORT_NAME"</p>
@@ -160,14 +161,14 @@ <h3 class="command" id="fn-arexx-exist">AREXX EXIST</h3>
         AREXX is activated, it opens up two communications ports "AREXX" and "REXX", so the
         following example can be used for a test:</p>
 
-    <pre>
-E> If Arexx Exist("REXX")=0
-    Trap Exec "RexxMast" : Rem Load AREXX and trap an error
-    If Arexx Exist ("REXX")=0
-     Print "Sorry, AREXX cannot be opened!"
-    Endif
-   Endif
-</pre>
+<code class="prefix edit">
+If Arexx Exist("REXX")=0
+ Trap Exec "RexxMast" : Rem Load AREXX and trap an error
+ If Arexx Exist ("REXX")=0
+  Print "Sorry, AREXX cannot be opened!"
+ Endif
+Endif
+</code>
 
     <h3 class="command" id="i-arexx-wait">AREXX WAIT</h3>
     <p><i>instruction: wait for a message from an AREXX program</i><br>
@@ -195,14 +196,14 @@ <h3 class="command" id="fn-arexx">AREXX</h3>
         must be answered immediately with an appropriate return string. This function can be used in a
         loop, as an alternative to the AREXX WAIT command. For example:</p>
 
-    <pre>
-X> Do
-    If Arexx
-     Print "A message is waiting!"
-    Endif
-    Multi Wait
-   Loop
-</pre>
+<code class="prefix ex">
+Do
+  If Arexx
+   Print "A message is waiting!"
+  Endif
+  Multi Wait
+Loop
+</code>
 
     <h3 class="command" id="fn-arexx-dollar">AREXX$</h3>
     <p><i>function: get a message from an AREXX program</i><br>

13-01-configuration.html

@@ -293,7 +293,7 @@ <h2>Setting the Interpreter Configuration</h2>
 
     <p>
         [Allow "Kill Editor" to work]<br>
-        The KILL EDITOR command is explained at the beginning of <a href="14/1417.html">Appendix B</a>, and it is used to
+        The <a href="14-appendix-b-amos-professional-run-time.html#i-kill-editor">KILL EDITOR</a> command is used to
         remove the entire Editor. This frees up the whole of the memory space allocated to the Editor,
         which is re-loaded when the program is over.</p>
 
@@ -342,7 +342,7 @@ <h2>Setting the Interpreter Configuration</h2>
     <p>
         [Copper List Buffer size (K.Bytes)]<br>
         The available allocation ranges from 2k up to 32k. Full details of the Copper list are given in
-        <a href="14/1442.html">Appendix F</a>.</p>
+        <a href="14-appendix-f-copper-lists.html">Appendix F</a>.</p>
 
     <p>
         [Variable Name Buffer size (K.Bytes)]<br>

13-02-object-editor.html

@@ -700,7 +700,7 @@ <h2>Animation</h2>
         If you are using the PAL or SECAM television display systems, there are 16 individual movie
         "<b>frames</b>" displayed in the top half of the screen, that can take one image each. If you are using
         the NTSC system, there will be eight frames available. These alternative systems are fully
-        discussed in <a href="14/1419.html">Appendix C</a> of this User Guide.</p>
+        discussed in <a href="14-appendix-c-pal-and-ntsc.html">Appendix C</a> of this User Guide.</p>
 
     <p>
         Below these frames is your "<b>movie screen</b>", where the individual frames will be shown,

styles.css

@@ -62,4 +62,42 @@ div#cover {
     width: 90%;
     height: auto;
     border: none;
-}
+}
+
+code {
+    display: block;
+    font-family: monospace;
+    white-space: pre;
+}
+
+code.prefix {
+    margin-left: 2rem;
+    margin-top: -1rem;
+}
+
+code.prefix::before {
+    display: inline;
+    font-family: monospace;
+    font-weight: normal;
+    position: relative;
+    left: -2rem;
+    top: 1.4rem;
+}
+
+code.edit::before {
+    content: "E>";
+}
+
+code.disc::before {
+    content: "DP>";
+}
+
+
+code.direct::before {
+    content: "D>";
+}
+
+code.ex::before {
+    content: "X>";
+}
+