[gnome-devel-docs] minor fixes

[Allan Day <allanday src gnome org>]

commit 3d0cef5afb9bfbc04c8e95e1cac650ab2d3680ee
Author: Allan Day <allanpday gmail com>
Date:   Tue Aug 19 23:25:53 2014 +0100

    minor fixes

 hig3/C/essentials.page              |    9 +++++----
 hig3/C/index.page                   |    2 +-
 hig3/C/patterns.page                |    2 +-
 hig3/C/pointer-and-touch-input.page |   10 ++++------
 4 files changed, 11 insertions(+), 12 deletions(-)
---
diff --git a/hig3/C/essentials.page b/hig3/C/essentials.page
index abff473..a062c7d 100644
--- a/hig3/C/essentials.page
+++ b/hig3/C/essentials.page
@@ -19,6 +19,10 @@
 
 <table>
 <tr>
+<td><p><link xref="design-principles"><em style="strong">Design principles</em></link></p></td>
+<td><p>General design guidelines and advice.</p></td>
+</tr>
+<tr>
 <td><p><link xref="application-basics"><em style="strong">Application basics</em></link></p></td>
 <td><p>Basic application behavior and characteristics.</p></td>
 </tr>
@@ -26,10 +30,7 @@
 <td><p><link xref="compatibility"><em style="strong">Compatibility</em></link></p></td>
 <td><p>Using the HIG for cross-platform or GNOME 2 style applications.</p></td>
 </tr>
-<tr>
-<td><p><link xref="design-principles"><em style="strong">Design principles</em></link></p></td>
-<td><p>General design guidelines and advice.</p></td>
-</tr>
+
 </table>
 
 </section>
diff --git a/hig3/C/index.page b/hig3/C/index.page
index d7a3b1c..cddfe4e 100644
--- a/hig3/C/index.page
+++ b/hig3/C/index.page
@@ -41,7 +41,7 @@ If you have never read the Human Interface Guidelines before, it is recommended
 <section id="version">
 <title>Version</title>
 
-<p>This is version 3.14 of the GNOME Human Interface Guidelines, and is compatible with the GTK+ version of 
the same number.</p>
+<p>This is version 3.14 of the GNOME Human Interface Guidelines, and is compatible with GTK+ and GNOME 
3.14.</p>
 
 <!-- In future releases, can insert details of changes here. -->
 
diff --git a/hig3/C/patterns.page b/hig3/C/patterns.page
index d8d95e4..15371e1 100644
--- a/hig3/C/patterns.page
+++ b/hig3/C/patterns.page
@@ -16,7 +16,7 @@
 
 <p>Once you have decided which patterns to use, the <link xref="ui-elements">user interface elements 
pages</link> provide details of individual elements that you can use to fill out your design.</p>
 
-<links type="topic" style="2column" groups="application-menus header-bars header-bar-menus search 
view-switchers selection-mode dialogs sidebars notifications"/>
+<links type="topic" style="2column" groups="application-menus primary-windows header-bars header-bar-menus 
grids lists selection-mode search view-switchers sidebar-lists dialogs notifications action-bars"/>
 
 <media type="image" mime="image/svg" src="figures/patterns/patterns.svg"/>
 
diff --git a/hig3/C/pointer-and-touch-input.page b/hig3/C/pointer-and-touch-input.page
index 1ef66d2..ef9e989 100644
--- a/hig3/C/pointer-and-touch-input.page
+++ b/hig3/C/pointer-and-touch-input.page
@@ -26,15 +26,13 @@
 <section id="primary-and-secondary-buttons">
 <title>Primary and secondary buttons</title>
 
-<p>Mice and touchpads often have two main buttons. One of these acts as the primary button, and the other 
acts as the secondary button.</p>
+<p>Mice and touchpads often have two main buttons. One of these acts as the primary button, and the other 
acts as the secondary button. Typically, the left button is used as the primary button and the right button 
is used as the secondary button. However, this order is user-configurable and does not translate to 
touchscreen input. These guidelines therefore refer to primary and secondary action, rather than left and 
right.</p>
 
-<p>Use the primary button for selecting items and activating controls. The secondary button can be used for 
accessing additional options, typically through a context menu.</p>
+<p>Use the primary action for selecting items and activating controls. The secondary action can be used for 
accessing additional options, typically through a context menu.</p>
 
-<p>Do not depend on input from the middle or right mouse buttons. As well as being physically more difficult 
to click, some pointing devices and many assistive technology devices only support or emulate the left mouse 
button. Some assistive technologies may not even emulate the mouse at all, but generate keyboard events 
instead.</p>
+<p>Do not depend on input from secondary or other additional buttons. As well as being physically more 
difficult to click, some pointing devices and many assistive technology devices only support or emulate the 
primary button.</p>
 
-<p>Press and hold should be used to simulate the secondary button on single button pointer devices. 
Therefore, do not use press and hold for other purposes.</p>
-
-<note><p>Typically, the left button is used as the primary button and the right button is used as the 
secondary button. However, this order is user-configurable. These guidelines therefore refer to primary and 
secondary, rather than left and right.</p></note>
+<p>Press and hold should be used to simulate the secondary button on single button pointing devices. 
Therefore, do not use press and hold for other purposes.</p>
 
 </section>