[gnome-devel-docs] Fix typos in hig manual

[David King <davidk src gnome org>]

commit ac8e287479b09255a24a63a08e1f79de09383d69
Author: Anders Jonsson <anders jonsson norsjovallen se>
Date:   Thu Mar 26 00:56:52 2015 +0100

    Fix typos in hig manual
    
    https://bugzilla.gnome.org/show_bug.cgi?id=746786

 hig/C/button-menus.page      |    2 +-
 hig/C/icons-and-artwork.page |    2 +-
 hig/C/keyboard-input.page    |    4 ++--
 hig/C/lists.page             |    2 +-
 hig/C/menus.page             |    2 +-
 hig/C/notifications.page     |    2 +-
 hig/C/popovers.page          |    2 +-
 hig/C/progress-bars.page     |    2 +-
 hig/C/progress-spinners.page |    2 +-
 hig/C/tabs.page              |    2 +-
 10 files changed, 11 insertions(+), 11 deletions(-)
---
diff --git a/hig/C/button-menus.page b/hig/C/button-menus.page
index 75e0d5c..df0b0d3 100644
--- a/hig/C/button-menus.page
+++ b/hig/C/button-menus.page
@@ -29,7 +29,7 @@
 <p>Menus provide a clear and consistent way to present diverse sets of actions and settings. At the same 
time, a popover with embedded controls, like buttons, sliders, spin buttons, lists and text entries, can 
provide a more effective interface for many tasks.</p>
 
 <list>
-<item><p>Evaluate each function within a button menu, in order to decide whether it would be better served 
by a different <link xref="ui-elements">user interface element</link>. While simple actions or settings can 
be effectively represented by menu items, others cannot. In particular, sliders, spin buttons, switches and 
text entries provide functionality that cannot be easily reproduced with a menu. Likewise, some entries might 
be better represented as icons rather than text - in which case, buttons could be more appropropriate than a 
menu.</p></item>
+<item><p>Evaluate each function within a button menu, in order to decide whether it would be better served 
by a different <link xref="ui-elements">user interface element</link>. While simple actions or settings can 
be effectively represented by menu items, others cannot. In particular, sliders, spin buttons, switches and 
text entries provide functionality that cannot be easily reproduced with a menu. Likewise, some entries might 
be better represented as icons rather than text - in which case, buttons could be more appropriate than a 
menu.</p></item>
 <item><p>If a menu button contains a small number of items that can be more effectively represented as a 
group of controls, a popover containing different interface elements can be a more interesting and efficient 
user interface. However, this approach can easily become over-complex for larger and more diverse button 
menus.</p></item>
 <item><p>A menu button can be combined with a small number of other interface elements, such as buttons, 
sliders and switches (see example below). This can enable some menu items to be presented in a more 
space-efficient manner, or to provide interactions that are not possible with a standard menu. However, be 
careful not to mix too many types of control or make the menu too complex in the process.</p></item>
 </list>
diff --git a/hig/C/icons-and-artwork.page b/hig/C/icons-and-artwork.page
index 2b547fc..f1e998b 100644
--- a/hig/C/icons-and-artwork.page
+++ b/hig/C/icons-and-artwork.page
@@ -91,7 +91,7 @@
 <section id="custom-symbolic-icons">
 <title>Custom Symbolic Icons</title>
 
-<p>Symbolic icons have a simple form and are drawn within a 16x16 pixel grid. They are then programatically 
scaled and colored within the user interface itself.</p>
+<p>Symbolic icons have a simple form and are drawn within a 16x16 pixel grid. They are then programmatically 
scaled and colored within the user interface itself.</p>
 
 <list>
 <item><p>Identify a single property when looking for an appropriate metaphor for an icon, and focus on what 
distinguishes the idea you want to communicate. For example, when describing an action to be performed on an 
image, it isn’t necessary to repeat the idea of an image in every icon. Instead, focus on what is distinct 
about each action (for example: rotate, tag, align).</p></item>
diff --git a/hig/C/keyboard-input.page b/hig/C/keyboard-input.page
index 0991b14..f290ed5 100644
--- a/hig/C/keyboard-input.page
+++ b/hig/C/keyboard-input.page
@@ -77,7 +77,7 @@
 </tr>
 <tr>
 <td><p><key>F6</key> and <keyseq><key>Shift</key><key>F6</key></keyseq></p></td>
-<td><p>Give focus to the next/preivous pane in a GtkPaned window</p></td>
+<td><p>Give focus to the next/previous pane in a GtkPaned window</p></td>
 </tr>
 <tr>
 <td><p><key>F8</key></p></td>
@@ -263,7 +263,7 @@
 <section id="application-shortcuts">
 <title>Standard application shortcuts</title>
 
-<p>This section details common application keyboard shortcuts. With the exception of applicaiton shortcuts, 
these shortcuts only need to be followed when the corresponding action is included in your application. 
Standard shortcuts can be assigned to other actions if the standard action is not available.</p>
+<p>This section details common application keyboard shortcuts. With the exception of application shortcuts, 
these shortcuts only need to be followed when the corresponding action is included in your application. 
Standard shortcuts can be assigned to other actions if the standard action is not available.</p>
 
 <p>This section also provides guidance on standard menu items in a <link xref="menu-bars">menu bar</link>, 
should one be used.</p>
 
diff --git a/hig/C/lists.page b/hig/C/lists.page
index 529fbe7..a258440 100644
--- a/hig/C/lists.page
+++ b/hig/C/lists.page
@@ -31,7 +31,7 @@
 
 <p>Standard lists are most common list type, and should generally be used in favor of tables.</p>
 
-<p>In standard lists, each row is divided by separators, and changing the sort order is acheived by using a 
control outside the list itself.</p>
+<p>In standard lists, each row is divided by separators, and changing the sort order is achieved by using a 
control outside the list itself.</p>
 
 <section id="styles">
 <title>Styles</title>
diff --git a/hig/C/menus.page b/hig/C/menus.page
index cbba78d..50f3fca 100644
--- a/hig/C/menus.page
+++ b/hig/C/menus.page
@@ -45,7 +45,7 @@
 <p>Organize similar menu items into groups using dividers - this will make them easier to understand and 
quicker to use. When creating groups:</p>
 
 <list>
-<item><p>Order groups and group items logically, either by importance, task order, or expected frequency of 
use. Items at the top and bottom of the menu are more noticable and easily targetted, so reserve these 
locations for particularly important or interesting functionality.</p></item>
+<item><p>Order groups and group items logically, either by importance, task order, or expected frequency of 
use. Items at the top and bottom of the menu are more noticeable and easily targetted, so reserve these 
locations for particularly important or interesting functionality.</p></item>
 <item><p>Place single-item groups at the top or bottom of the menu, or group them together with other single 
items.</p></item>
 <item><p>Do not mix different types of menu item within each group - actions, check box and radio button 
items should be kept separate.</p></item>
 </list>
diff --git a/hig/C/notifications.page b/hig/C/notifications.page
index 3265cae..7622b15 100644
--- a/hig/C/notifications.page
+++ b/hig/C/notifications.page
@@ -76,7 +76,7 @@
 <list>
 <item><p>Notification actions should be related to the content of the notification, and should not provide 
generic actions for your application. This ensures that each notification has a clear focus and 
purpose.</p></item>
 <item><p>Only use notification actions when the functionality that they provide is commonly 
required.</p></item>
-<item><p>Actions shold not replace user interface controls elsewhere - it should be possible to take the 
same actions from your application’s windows.</p></item>
+<item><p>Actions should not replace user interface controls elsewhere - it should be possible to take the 
same actions from your application’s windows.</p></item>
 <item><p>It is not necessary to always use notification actions, and many notifications will not require 
them.</p></item>
 <item><p>Notification actions should not duplicate the default action. For example, a new email notification 
does not need to include an Open button, since the default action should already perform this 
action.</p></item>
 </list>
diff --git a/hig/C/popovers.page b/hig/C/popovers.page
index a37ef60..6065c05 100644
--- a/hig/C/popovers.page
+++ b/hig/C/popovers.page
@@ -39,7 +39,7 @@
 <list>
 <item><p>A popover is a generic container, and can include a wide variety of controls, such as buttons, 
sliders, lists, switches and text fields. However, don’t mix too many different types of control within the 
same popover, and try to group controls of the same type together.</p></item>
 <item><p>Popovers can function as a container for a menu, or for a menu in combination with a small number 
of supplementary controls.</p></item>
-<item><p>If the purpose of a popover’s controls is ambigious, the popover can be given a heading.</p></item>
+<item><p>If the purpose of a popover’s controls is ambiguous, the popover can be given a heading.</p></item>
 <item><p><gui>Close</gui> or <gui>Done</gui> buttons are not usually required in a popover.</p></item>
 </list>
 
diff --git a/hig/C/progress-bars.page b/hig/C/progress-bars.page
index e06440f..146f93f 100644
--- a/hig/C/progress-bars.page
+++ b/hig/C/progress-bars.page
@@ -60,7 +60,7 @@
 <list>
 <item><p>Always consider what is most relevant and interesting for the user.</p></item>
 <item><p>It is often better to provide specific information rather than a unitless percentage. For example, 
<gui>13 of 19 images rotated</gui> or <gui>12.1 of 30 MB downloaded</gui> rather than <gui>13% 
complete</gui>.</p></item>
-<item><p>For long-running tasks, it can be desirable to show an estimate of the time remaining in the 
progress bar text. If other relevant information isn't available, this can be shown on its own. 
Alternatively, it can appear alongside text about task progress; however, be careful not to overwhelm the 
user with too much information when doing this, and use <link xref="typography">typographic 
conventions</link> to differente the most useful information.</p></item>
+<item><p>For long-running tasks, it can be desirable to show an estimate of the time remaining in the 
progress bar text. If other relevant information isn't available, this can be shown on its own. 
Alternatively, it can appear alongside text about task progress; however, be careful not to overwhelm the 
user with too much information when doing this, and use <link xref="typography">typographic 
conventions</link> to differentiate the most useful information.</p></item>
 <item><p>If the time remaining is an estimate, use the word <gui>about</gui>. For example: <gui>About 3 
minutes left</gui>.</p></item>
 </list>
 
diff --git a/hig/C/progress-spinners.page b/hig/C/progress-spinners.page
index 382a2af..3e6b100 100644
--- a/hig/C/progress-spinners.page
+++ b/hig/C/progress-spinners.page
@@ -35,7 +35,7 @@
 <list>
 <item><p>If an operation can vary in how long it takes, use a timeout to only show a progress spinner after 
three seconds have elapsed. A progress indication is not needed for lengths of time below this.</p></item>
 <item><p>Place progress spinners close to or within the user interface elements they relate to. If a button 
triggers a long-running operation, the spinner can be placed next to that button, for example. When loading 
content, the spinner should be placed within the area where that content will appear.</p></item>
-<item><p>Generally, only one progress spinner should be displayed at once. Avoid showing a large number of 
spinners simulatenously - this will often be visually overwhelming.</p></item>
+<item><p>Generally, only one progress spinner should be displayed at once. Avoid showing a large number of 
spinners simultaneously - this will often be visually overwhelming.</p></item>
 <item><p>A label can be shown next to a spinner if it is helpful to clarify the task which a spinner relates 
to.</p></item>
 <item><p>If a spinner is displayed for a long time, a label can indicate both the identity of the task and 
progress through it. This can take the form of a percentage, an indication of the time remaining or, or 
progress through sub-components of the task (eg. modules downloaded, or pages exported).</p></item>
 </list>
diff --git a/hig/C/tabs.page b/hig/C/tabs.page
index e372a16..eadb3bb 100644
--- a/hig/C/tabs.page
+++ b/hig/C/tabs.page
@@ -35,7 +35,7 @@
 
 <p>Use fixed tabs when a <link xref="dialogs">dialog window</link> contains too many controls (or too much 
information) to be comfortably presented at once.</p>
 
-<p>Dynamic tabs are primarily useful for browser or editor applications, where a user might want to use 
several locations or content items simulatenously.</p>
+<p>Dynamic tabs are primarily useful for browser or editor applications, where a user might want to use 
several locations or content items simultaneously.</p>
 
 </section>