Reorganize control surfaces generic midi

_manual/23_using-control-surfaces/03_generic-midi.html

@@ -0,0 +1,18 @@
+---
+layout: default
+title: Generic Midi Surface Control
+---
+
+<p>
+  Generic Midi allows synthesizers and other devices communicate with
+  Ardour. MIDI devices can send commands relating to playback (such as
+  play or stop), performance (such as volume, play, stop, and almost any
+  other function (such as Edit, or Undo).
+</p>
+<p>
+  Many MIDI control surfaces use predefined MIDI protocols such as the
+  "Mackie Control Protocol". In such cases it is best to use Ardour's
+  implementation of that protocol as it is likely more feature complete.
+</p>
+
+{% children %}

_manual/23_using-control-surfaces/03_generic-midi/01_midi-binding-maps.html

@@ -1,11 +1,11 @@
 ---
 layout: default
-title: MIDI Binding Maps
+title: Generic MIDI Binding Maps
 ---
 
 <p>
   Ardour 2.X supported
-  <a href="/using-control-surfaces/midi-learn/"><dfn>MIDI learning</dfn></a> 
+  <a href="/using-control-surfaces/generic-midi/midi-learn/"><dfn>MIDI learning</dfn></a>
   for more or less any control. This was a nice feature that quite a few other
   DAWs are providing by now, but it didn't allow Ardour to work "out of the
   box" with sensible defaults for existing commercial MIDI
@@ -56,11 +56,10 @@ title: MIDI Binding Maps
   Ardour has had the concept of identifying each track and bus with a
   <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. Ardour has a 
+   which track or bus they are intended to control. See
    <a
-  href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">number 
-   of ways of assigning remote control IDs</a>, but they don't really matter 
-   very much when creating MIDI binding maps, so we won't discuss that here. 
+  href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">
+   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.
 </p>
@@ -137,7 +136,7 @@ bindings"&gt;
   offsets rather than values. These accept Continuous Controller messages
   but treat them as offsets. These are good for banked controls as they are
   always at the right spot to start adjusting. (
-   <a href="/using-control-surfaces/midi-binding-maps/working-with-encoders/">
+   <a href="/using-control-surfaces/generic-midi/working-with-encoders/">
    Learn more about working with encoders
    </a>)
 </p>

_manual/23_using-control-surfaces/03_generic-midi/02_midi-learn.html

@@ -1,6 +1,6 @@
 ---
 layout: default
-title: MIDI Learn
+title: Generic MIDI Learn
 ---
 
 <h2>Philosophy</h2>

_manual/23_using-control-surfaces/03_generic-midi/03_working-with-encoders.html

@@ -1,7 +1,6 @@
 ---
 layout: default
-title: Working With Encoders in Ardour
-menu_title: Working With Encoders
+title: Generic MIDI and Encoders
 ---
 
 <p>