From 34cb2a07c45fc97aa8247e159c7f6a3d457af865 Mon Sep 17 00:00:00 2001
From: Paul Davis <paul@linuxaudiosystems.com>
Date: Tue, 27 Sep 2016 14:56:10 -0500
Subject: [PATCH] text tweaks

---
 _manual/22_using-control-surfaces/06_Abelton_Push2.html | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/_manual/22_using-control-surfaces/06_Abelton_Push2.html b/_manual/22_using-control-surfaces/06_Abelton_Push2.html
index baee947..d7725be 100644
--- a/_manual/22_using-control-surfaces/06_Abelton_Push2.html
+++ b/_manual/22_using-control-surfaces/06_Abelton_Push2.html
@@ -62,12 +62,15 @@ menu_title: Ableton Push 2
     <dd>37 scales are available. Like Live, Ardour offers both
     "in-key" and "chromatic" pad layouts.</dd>
   </dl>
+
+  ... plus a variety of tasks related to transport control, selection,
+  import, click track control and more.
 </p>
 
 <h2>Musical Performance</h2>
 <p>
   Messages sent from the 8x8 pad grid and the "pitch bend bar" are
-  routed to a special MIDI port within Ardour called "Ableton Pads"
+  routed to a special MIDI port within Ardour called "Push 2 Pads"
   (no extra latency is incurred from this routing). Although you can
   manually connect this port to whatever you wish, the normal
   behaviour of Ardour's Push 2 support is to connect the pads to the
@@ -81,7 +84,7 @@ menu_title: Ableton Push 2
   If multiple MIDI tracks are selected at once, the first selected
   track will be used. Note that messages originating from all other
   controls on the Push 2 will <em>not</em> not be delivered to the
-  "Ableton Pads" port. This makes no difference in practice, because
+  "Push 2 Pads" port. This makes no difference in practice, because
   the other controls do not send messages that are useful for musical
   performance. 
 </p>
-- 
2.37.2