[gnome-devel-docs] incorporate corrections from Michael Hill

[Allan Day <allanday src gnome org>]

commit 38c8dd14a795144c90a0c3960cc3cc11926c57df
Author: Allan Day <allanpday gmail com>
Date:   Wed Aug 20 10:02:52 2014 +0100

    incorporate corrections from Michael Hill

 hig3/C/buttons.page                 |    2 +-
 hig3/C/dialogs.page                 |    1 -
 hig3/C/index.page                   |    2 +-
 hig3/C/keyboard-input.page          |    7 +------
 hig3/C/menu-bars.page               |   10 +++++-----
 hig3/C/pointer-and-touch-input.page |    2 +-
 hig3/C/progress-bars.page           |    4 ++--
 hig3/C/selection-mode.page          |    2 +-
 hig3/C/text-fields.page             |    2 +-
 hig3/C/typography.page              |    2 +-
 10 files changed, 14 insertions(+), 20 deletions(-)
---
diff --git a/hig3/C/buttons.page b/hig3/C/buttons.page
index fe28c70..11d771f 100644
--- a/hig3/C/buttons.page
+++ b/hig3/C/buttons.page
@@ -46,7 +46,7 @@
 <section id="text-buttons">
 <title>Text buttons</title>
 
-<p>Label all buttons with imperative verbs, using <link xref="writing-style#capitalization">header 
capitalization</link>. For example, Save, Sort or Update Now. Provide an access key in the label that allows 
the user to directly activate the button from the keyboard.</p>
+<p>Label all buttons with imperative verbs, using <link xref="writing-style#capitalization">header 
capitalization</link>. For example, <gui>Save</gui>, <gui>Sort</gui> or <gui>Update Now</gui>. Provide an 
access key in the label that allows the user to directly activate the button from the keyboard.</p>
 
 <p>Use an ellipsis (…) at the end of the label if the action requires further input from the user before it 
can be carried out. For example, <gui>Save As…</gui> or <gui>Find…</gui>. Do not add an ellipsis to commands 
like <gui>Properties</gui> or <gui>Preferences</gui>, as these open windows that do not require further 
input.</p>
 
diff --git a/hig3/C/dialogs.page b/hig3/C/dialogs.page
index 4c6c16c..9b1568e 100644
--- a/hig3/C/dialogs.page
+++ b/hig3/C/dialogs.page
@@ -145,7 +145,6 @@
 <item><p>Use <link xref="view-switchers">view switchers</link> or <link xref="tabs">tabs</link> to break up 
controls and information.</p></item>
 <item><p>Avoid stacking dialog windows on top of one another. Only one dialog window should be displayed at 
a time.</p></item>
 <item><p>When an affirmative button is included, label it with its actual action. <gui>Print</gui> is a 
better label than <gui>OK</gui> or <gui>Done</gui>, for example.</p></item>
-<item><p>When opening a dialog, provide initial keyboard focus to the component that you expect users to 
operate first.</p></item>
 <item><p>Do not enable the <gui>OK</gui> or equivalent button until all fields that require input have been 
attended to by the user.</p></item>
 <item><p>When opening a dialog, provide initial keyboard focus to the component that you expect users to 
operate first. This focus is especially important for users who must use a keyboard to navigate your 
application.</p></item>
 </list>
diff --git a/hig3/C/index.page b/hig3/C/index.page
index cddfe4e..1647571 100644
--- a/hig3/C/index.page
+++ b/hig3/C/index.page
@@ -33,7 +33,7 @@
 <item><p><link xref="essentials">Essentials</link> - these pages include overarching guidance on thematic 
topics. They include sections on recommended design principles, as well as guidance on themes like writing 
style and artwork.</p></item>
 <item><p><link xref="patterns">Patterns</link> - design patterns make up the core of the HIG. Each pattern 
is a particular arrangement of user interface elements which can be used to construct an application design. 
The patterns allow key design decisions to be abstracted away from the nitty gritty of individual user 
interface elements.</p></item>
 <item><p><link xref="ui-elements">Interface elements</link> - guidance on the various interface elements, 
such as buttons, switches, and sliders, that you can use in your application.
-If you have never read the Human Interface Guidelines before, it is recommended that you start with the 
Basics section, in particular the design principles page, before continuing to learn about the design 
patterns.</p></item>
+If you have never read the Human Interface Guidelines before, it is recommended that you start with the 
essentials section, in particular the design principles page, before continuing to learn about the design 
patterns.</p></item>
 </list>
 
 </section>
diff --git a/hig3/C/keyboard-input.page b/hig3/C/keyboard-input.page
index 31350c6..4e29d86 100644
--- a/hig3/C/keyboard-input.page
+++ b/hig3/C/keyboard-input.page
@@ -72,7 +72,7 @@
 
 <list>
 <item><p>Use the standard GNOME shortcut keys (see below) if your application supports those functions. This 
ensures consistency between GNOME applications and aids discoverability.
-Do not assign system-level shortcut keys. These use the Super (sometimes knows as the windows key) key as a 
modifier.</p></item>
+Do not assign system-level shortcut keys. These use the Super key (sometimes knows as the windows key) as a 
modifier.</p></item>
 <item><p>Only assign shortcut keys to the most commonly-used actions in your application. Do not try to 
assign a keyboard shortcut to everything.</p></item>
 <item><p>Do not use the standard GNOME application shortcut keys for different functions. This helps to 
reinforce consistency between all GNOME applications.</p></item>
 <item><p>Use Ctrl+letter in preference to other combinations when choosing new shortcut keys and 
Shift+Ctrl+letter for functions that reverse or extend another function. For example, 
<keyseq><key>Ctrl</key><key>Z</key></keyseq> and <keyseq><key>Shift</key><key>Ctrl</key><key>Z</key></keyseq> 
for <gui>Undo</gui> and <gui>Redo</gui>.</p></item>
@@ -154,11 +154,6 @@ Do not assign system-level shortcut keys. These use the Super (sometimes knows a
 <td><p><keyseq><key>Alt</key><key>F10</key></keyseq></p></td>
 <td><p>Maximize the focused window</p></td>
 </tr>
-<tr>
-<td><p><gui>Maximize</gui></p></td>
-<td><p><keyseq><key>Alt</key><key>F10</key></keyseq></p></td>
-<td><p>Maximize the focused window</p></td>
-</tr>
 </tbody>
 </table>
 
diff --git a/hig3/C/menu-bars.page b/hig3/C/menu-bars.page
index 214d216..d5fcdbe 100644
--- a/hig3/C/menu-bars.page
+++ b/hig3/C/menu-bars.page
@@ -24,7 +24,7 @@
 
 <title>Menu bars</title>
 
-<p>A menubar incorporates a strip of drop-down menus. It is typically located at the top of a primary 
window, below a window title bar.</p>
+<p>A menu bar incorporates a strip of drop-down menus. It is typically located at the top of a primary 
window, below a window title bar.</p>
 
 <p>The menubar is normally visible at all times and is always accessible from the keyboard, so make all the 
commands available in your application available on the menubar.</p>
 
@@ -79,7 +79,7 @@
 <tr>
 <td><p><gui>New</gui></p></td>
 <td><p><keyseq><key>Ctrl</key><key>N</key></keyseq></p></td>
-<td><p>Creates a new document. Open a new primary window, with the title <gui>Document name</gui>, 
containing a blank document. How this window is displayed, e.g. as a tab or a separate window, is up to the 
window manager.</p>
+<td><p>Creates a new document. Open a new primary window, with the title <gui>Document name</gui>, 
containing a blank document. How this window is displayed, eg: as a tab or a separate window, is up to the 
window manager.</p>
 <p>If your application can create a number of different types of document, you can make the <gui>New</gui> 
item a submenu, containing a menu item for each type. Label these items <gui>New</gui> document type, make 
the first entry in the submenu the most commonly used document type, and give it the 
<keyseq><key>Ctrl</key><key>N</key></keyseq> shortcut.</p>
 <p>Note: A blank document will not necessarily be completely blank. For example, a document created from a 
template may already contain some data.</p></td>
 </tr>
@@ -272,7 +272,7 @@
 </tr>
 <tr>
 <td><p><gui>Redo <em>action</em></gui></p></td>
-<td><p><keyseq><key>Ctrl</key><key>Ctrl</key><key>Z</key></keyseq></p></td>
+<td><p><keyseq><key>Shift</key><key>Ctrl</key><key>Z</key></keyseq></p></td>
 <td><p>Performs the next action in the undo history list, after the user has moved backwards through the 
list with the <gui>Undo</gui> command. Move the user one step forwards again, restoring the document to the 
state it was in after that action was originally performed.</p>
 <p>Note: provide a separate <gui>Undo</gui> and <gui>Redo</gui> menu item even if your application only 
supports one level of undo.</p></td>
 </tr>
@@ -281,8 +281,8 @@
 
 </section>
 
-<section id="selected-date-manipulation-menu-items">
-<title>Selected date manipulation menu items</title>
+<section id="selected-data-manipulation-menu-items">
+<title>Selected data manipulation menu items</title>
 
 <table>
 <thead>
diff --git a/hig3/C/pointer-and-touch-input.page b/hig3/C/pointer-and-touch-input.page
index ef9e989..f831b88 100644
--- a/hig3/C/pointer-and-touch-input.page
+++ b/hig3/C/pointer-and-touch-input.page
@@ -132,7 +132,7 @@
 <tr>
 <td><media type="image" mime="image/png" src="figures/touch/tap-and-hold.svg"/></td>
 <td><p>Press and hold for a second or two.</p></td>
-<td><p>Secondary action. Select the item and lists actions that can be fItem opens - photo is shown full 
size, application launches, song starts playing.</p></td>
+<td><p>Secondary action. Select the item and list actions that can be performed.</p></td>
 </tr>
 <tr>
 <td colspan="3"><p><em style="strong">Drag</em></p></td>
diff --git a/hig3/C/progress-bars.page b/hig3/C/progress-bars.page
index dcb8cb7..55a566a 100644
--- a/hig3/C/progress-bars.page
+++ b/hig3/C/progress-bars.page
@@ -49,8 +49,8 @@
 <list>
 <item><p>Accuracy is preferable for progress bars. Where possible, use a time-remaining progress bar, 
followed by typical-time. Try to avoid using indeterminate progress bars.</p></item>
 <item><p>Ensure that time-remaining and typical-time progress bars measure an operation's total time or 
total work, not just that of a single step.</p></item>
-<item><p>For time-remaining progress bars, update time-remaining progress bars when changes occur that will 
cause the operation to finish more quickly or more slowly.</p></item>
-<item><p>For typical-time progress bars, if your application overestimates the completed amount of work, the 
length of the bar can indicate "almost complete" until the operation is complete. If your application 
underestimates how much work is complete, fill the remaining portion of the bar when the operation is 
complete.</p></item>
+<item><p>Update time-remaining progress bars when changes occur that will cause the operation to finish more 
quickly or more slowly.</p></item>
+<item><p>When using a typical-time progress bar, if your application overestimates the completed amount of 
work, the length of the bar can indicate "almost complete" until the operation is complete. If your 
application underestimates how much work is complete, fill the remaining portion of the bar when the 
operation is complete.</p></item>
 </list>
 
 </section>
diff --git a/hig3/C/selection-mode.page b/hig3/C/selection-mode.page
index a7366e4..c6a918e 100644
--- a/hig3/C/selection-mode.page
+++ b/hig3/C/selection-mode.page
@@ -17,7 +17,7 @@
 
 <p>Selection mode is a design pattern for allow actions to be performed on items of content. It is typically 
used in conjunction with lists and grids.</p>
 
-<p>When selection mode is active, check boxes allow items to be selected, and an action bar is shown at the 
bottom of the view. This contains the various actions that can be made on selected content items.</p>
+<p>When selection mode is active, check boxes allow items to be selected, and an action bar is shown at the 
bottom of the view. This contains the various actions that can be performed on selected content items.</p>
 
 <section id="when-to-use">
 <title>When to use</title>
diff --git a/hig3/C/text-fields.page b/hig3/C/text-fields.page
index b7087a5..a191da7 100644
--- a/hig3/C/text-fields.page
+++ b/hig3/C/text-fields.page
@@ -24,7 +24,7 @@
 
 <title>Text fields</title>
 
-<p>A text entry field is an interface element for entering or editing text. They are a basic element with a 
variety of uses, including search entry, settings and preferences, or account configuration and setup. A text 
entry field can be prefilled with text, and can include additional buttons or icons.</p>
+<p>A text entry field is an interface element for entering or editing text. It is a basic element with a 
variety of uses, including search entry, settings and preferences, or account configuration and setup. A text 
entry field can be prefilled with text, and can include additional buttons or icons.</p>
 
 <media type="image" mime="image/svg" src="figures/ui-elements/text-fields.svg"/>
 
diff --git a/hig3/C/typography.page b/hig3/C/typography.page
index b53dfc6..43a0002 100644
--- a/hig3/C/typography.page
+++ b/hig3/C/typography.page
@@ -16,7 +16,7 @@
 
 <title>Typography</title>
 
-<p>Text is an important part of any user interface. Text size, positioning, weight all contribute to the 
ability for text to convey information effectively, and also play an important role in creating a beautiful 
appearance.</p>
+<p>Text is an important part of any user interface. Text size, positioning and weight all contribute to the 
ability for text to convey information effectively, and also play an important role in creating a beautiful 
appearance.</p>
 
 <section id="default-fonts">
 <title>Default Fonts</title>