Removing unused images, a tiny bit of styling

[ardour-manual] / include / generic-midi-binding-maps.html

diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html
index c8c49c2b7405b5dfe2e03a14f4e2e4426972da0f..94af9d5a6eacb86ef3b44a05e14d506d82f9e356 100644 (file)
--- a/include/generic-midi-binding-maps.html
+++ b/include/generic-midi-binding-maps.html
@@ -53,8 +53,7 @@
   <dfn>remote control ID</dfn>. This ID uniquely identifies a track or bus
   so that when messages arrive from elsewhere via MIDI or OSC , we can determine
    which track or bus they are intended to control. See
-   <a
-  href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">
+   <a href="@@controlling-track-ordering">
    remote control IDs</a> for more information.
    You just need to know that there is a "first track" and its remote control
    ID is 1, and so on.
@@ -201,7 +200,7 @@ bindings"&gt;
 </table>
 <p>Each of the specifications needs an address, which takes various forms too. For track-level controls (solo/gain/mute/recenable), the address is one the following:</p>
 <table class="dl">
-<tr><th>a number, eg. "1"
+<tr><th>a number, e.g. "1"
 </th>
 <td>identifies a track or bus by its remote control ID
 </td></tr>
@@ -303,7 +302,7 @@ bindings"&gt;
 <p>
   You can also bind a sysex or arbitrary message to any of the items
   that occur in Ardour's main menu (and its submenus). The <a
-  href="/appendix/menu-actions-list/">
+  href="@@list-of-menu-actions">
   list of actions</a> shows all available values of <em>action-name</em>.
 <p>
   To create a binding between an arbitrary MIDI message (we'll use a