[gnome-devel-docs] hig3: assorted typo and US spelling fixes

[Michael Hill <mdhill src gnome org>]

commit 631814495298a4923eaaa30460fddf91c2b52f23
Author: Michael Hill <mdhill gnome org>
Date:   Mon Aug 18 21:10:14 2014 -0400

    hig3: assorted typo and US spelling fixes

 hig3/C/check-boxes.page       |    2 +-
 hig3/C/design-principles.page |    8 ++++----
 hig3/C/dialogs.page           |    2 +-
 hig3/C/grids.page             |    2 +-
 hig3/C/header-bars.page       |    2 +-
 hig3/C/icons-and-artwork.page |   12 ++++++------
 hig3/C/keyboard-input.page    |    4 ++--
 hig3/C/lists.page             |    2 +-
 hig3/C/menu-bars.page         |    8 ++++----
 hig3/C/menus.page             |    4 ++--
 hig3/C/notifications.page     |    2 +-
 hig3/C/progress-bars.page     |    8 ++++----
 hig3/C/search.page            |    2 +-
 hig3/C/selection-mode.page    |    2 +-
 hig3/C/sidebar-lists.page     |    4 ++--
 hig3/C/sliders.page           |    2 +-
 hig3/C/switches.page          |    2 +-
 hig3/C/tabs.page              |    2 +-
 hig3/C/text-fields.page       |    2 +-
 hig3/C/toolbars.page          |    2 +-
 hig3/C/typography.page        |    4 ++--
 hig3/C/visual-layout.page     |    6 +++---
 22 files changed, 42 insertions(+), 42 deletions(-)
---
diff --git a/hig3/C/check-boxes.page b/hig3/C/check-boxes.page
index e9b73af..bae0853 100644
--- a/hig3/C/check-boxes.page
+++ b/hig3/C/check-boxes.page
@@ -24,7 +24,7 @@
 
 <title>Check boxes</title>
 
-<p>Check boxes are used to show or change a setting. Its two states, set and unset, are shown by the 
presence or absence of a checkmark in the labelled box.</p>
+<p>Check boxes are used to show or change a setting. Its two states, set and unset, are shown by the 
presence or absence of a checkmark in the labeled box.</p>
 
 <media type="image" mime="image/png" src="figures/check-boxes.png"/>
 
diff --git a/hig3/C/design-principles.page b/hig3/C/design-principles.page
index 6ffe6d3..16b0fba 100644
--- a/hig3/C/design-principles.page
+++ b/hig3/C/design-principles.page
@@ -107,18 +107,18 @@
 <section id="name-and-icon">
 <title>Give your application an instructive name and an attractive icon</title>
 
-<p>Your application’s name and <link xref="icons-and-artwork#application-icons">icon</link> are two of the 
most expressive things about it, so design them in order to communicate its function and identity. Make sure 
that people will understand the purpose of your application from its name. Ensure that you have a beautiful, 
recognisable application icon, to give your application an attractive and distinctive visual identity.</p>
+<p>Your application’s name and <link xref="icons-and-artwork#application-icons">icon</link> are two of the 
most expressive things about it, so design them in order to communicate its function and identity. Make sure 
that people will understand the purpose of your application from its name. Ensure that you have a beautiful, 
recognizable application icon, to give your application an attractive and distinctive visual identity.</p>
 
 <p>Avoid obscure cultural references, inside jokes and acronyms in your application name, and ensure that 
you provide a hi-resolution version of your application icon.</p>
 
 </section>
 
 <section id="emotion">
-<title>Use emotion and humour (sparingly)</title>
+<title>Use emotion and humor (sparingly)</title>
 
-<p>Used effectively, emotion and humour can lift the experience provided by your application, and help to 
develop a positive relationship with your users. Be careful not to over-use these techniques though - it is 
far more effective to pick a small number of moments to use emotion, rather than spraying them throughout 
your user interface.</p>
+<p>Used effectively, emotion and humor can lift the experience provided by your application, and help to 
develop a positive relationship with your users. Be careful not to over-use these techniques though - it is 
far more effective to pick a small number of moments to use emotion, rather than spraying them throughout 
your user interface.</p>
 
-<p>Be welcoming when your application is used for the first time. Using humour when things go wrong is 
another effective technique.</p>
+<p>Be welcoming when your application is used for the first time. Using humor when things go wrong is 
another effective technique.</p>
 
 </section>
 
diff --git a/hig3/C/dialogs.page b/hig3/C/dialogs.page
index 2902583..79160fc 100644
--- a/hig3/C/dialogs.page
+++ b/hig3/C/dialogs.page
@@ -26,7 +26,7 @@
 
 <p>Dialogs are secondary windows that appear over a primary, parent window. They are used to present 
additional information or controls, including preferences, properties, or to present messages or 
questions.</p>
 
-<p>GTK+ provides a number of stock dialogs that you can be used, such as for printing or color selection.</p>
+<p>GTK+ provides a number of stock dialogs that can be used, such as for printing or color selection.</p>
 
 <p>There are three basic types of dialog design.</p>
 
diff --git a/hig3/C/grids.page b/hig3/C/grids.page
index 43e1cc6..eb8a9d4 100644
--- a/hig3/C/grids.page
+++ b/hig3/C/grids.page
@@ -20,7 +20,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<p>Since the grid view utilises an image for each item it presents, it is best suited to content that has a 
visual component, such as documents or photos. If content items don't have a visual component, a <link 
xref="lists">list view</link> might be more appropriate.</p>
+<p>Since the grid view utilizes an image for each item it presents, it is best suited to content that has a 
visual component, such as documents or photos. If content items don't have a visual component, a <link 
xref="lists">list view</link> might be more appropriate.</p>
 
 <p>Grids and lists can be combined, to offer different views of the same content. This can be useful if 
content items have additional metadata associated with them, such as creation dates or authorship.</p>
 
diff --git a/hig3/C/header-bars.page b/hig3/C/header-bars.page
index 44c444d..f427165 100644
--- a/hig3/C/header-bars.page
+++ b/hig3/C/header-bars.page
@@ -27,7 +27,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<p>Header bars are recommended for all application windows. They provide a number of advantages over the 
traditional combination of title bars, menu bar and toolbar, including a smaller vertical footprint, and 
dynamic navigation and mode changes (such as with <link xref="selection-mode">selection mode</link>).</p>
+<p>Header bars are recommended for all application windows. They provide a number of advantages over the 
traditional combination of title bar, menu bar and toolbar, including a smaller vertical footprint, and 
dynamic navigation and mode changes (such as with <link xref="selection-mode">selection mode</link>).</p>
 
 <p>Header bars are incompatible with menu bars. If your application already incorporates a menu bar, you 
should evaluate the alternatives suggested in these guidelines. See the <link xref="menu-bars">menu bar 
guidelines</link> for more details on this.</p>
 
diff --git a/hig3/C/icons-and-artwork.page b/hig3/C/icons-and-artwork.page
index 1385ad5..3d0b3f0 100644
--- a/hig3/C/icons-and-artwork.page
+++ b/hig3/C/icons-and-artwork.page
@@ -20,17 +20,17 @@
 <p>Icons play an important role in user interfaces: selecting the correct icon is therefore vital to making 
sure that your application is usable. An identifying icon is also an essential part of any application, and 
is a crucial part of its identity.</p>
 
 <section id="using-icons">
-<title>Using Icons in Your User Intereface</title>
+<title>Using Icons in Your User Interface</title>
 
 <p>There are many situations when it is necessary to decide between using an icon and a text label, 
particularly for buttons. Icons have the advantage of being smaller, and not requiring translation. At the 
same time, the incorrect use of an icon can make your interface hard - or even impossible - to understand.</p>
 
 <list>
-<item><p>Only use icons whose meaning is commonly recognized. If a commonly recognised icon is not 
available, it might be better to use a text label instead.</p>
+<item><p>Only use icons whose meaning is commonly recognized. If a commonly recognized icon is not 
available, it might be better to use a text label instead.</p>
 <list>
-<item><p>Convention establishes which icons will be recognised. If you are in doubt, stick to icons which 
are frequently used in other applications.</p></item>
+<item><p>Convention establishes which icons will be recognized. If you are in doubt, stick to icons which 
are frequently used in other applications.</p></item>
 <item><p>Consider which icons will be meaningful in the specific context of your application - users of 
specialist tools will often be familiar with domain-specific symbols.</p></item>
 </list></item>
-<item><p>Remember that some icons are only meaningful alongside other icons of the same type. For example, a 
media icon for stop is simply a square, and may not be identified as a stop icon without other media controls 
(like play, pause, or skip) being visible close by. Likewise, the icon to remove an item from a list is a 
subtract symbol (ie. a single line), and will not be recognisable without a corresponding "plus" add 
icon.</p></item>
+<item><p>Remember that some icons are only meaningful alongside other icons of the same type. For example, a 
media icon for stop is simply a square, and may not be identified as a stop icon without other media controls 
(like play, pause, or skip) being visible close by. Likewise, the icon to remove an item from a list is a 
subtract symbol (ie. a single line), and will not be recognizable without a corresponding "plus" add 
icon.</p></item>
 </list>
 
 </section>
@@ -79,7 +79,7 @@
 
 <media type="image" mime="image/png" src="figures/icons/sizes.png"/>
 
-<p>While not as critical, there are still areas where application icons are presented as a small size. To 
keep the icon sharp and well defined, a specific rendering is required to sizes of 48x48px, 32x32px, 24x24px 
and 16x16px. Many GNOME icons also ship a 22x22px size for legacy reason, but that isn't required.</p>
+<p>While not as critical, there are still areas where application icons are presented at a small size. To 
keep the icon sharp and well defined, a specific rendering is required to sizes of 48x48px, 32x32px, 24x24px 
and 16x16px. Many GNOME icons also ship a 22x22px size for legacy reasons, but that isn't required.</p>
 
 <media type="image" mime="image/png" src="figures/icons/sizes-small-24.png"/>
 
@@ -92,7 +92,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 coloured within the user interface itself.</p>
+<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>
 
 <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 (eg. rotate, tag, align).</p></item>
diff --git a/hig3/C/keyboard-input.page b/hig3/C/keyboard-input.page
index 00ef81a..eacc135 100644
--- a/hig3/C/keyboard-input.page
+++ b/hig3/C/keyboard-input.page
@@ -360,12 +360,12 @@ Do not assign system-level shortcut keys. These use the Super (sometimes knows a
 <tr>
 <td><p><gui>Reload</gui></p></td>
 <td><p><keyseq><key>Ctrl</key><key>R</key></keyseq></p></td>
-<td><p>Reload the current document, updating content from the sourc if necessary</p></td>
+<td><p>Reload the current document, updating content from the source if necessary</p></td>
 </tr>
 <tr>
 <td><p><gui>Properties</gui></p></td>
 <td><p><keyseq><key>Alt</key><key>Enter</key></keyseq></p></td>
-<td><p>Display the selectd object's properties window.</p></td>
+<td><p>Display the selected object's properties window.</p></td>
 </tr>
 </tbody>
 </table>
diff --git a/hig3/C/lists.page b/hig3/C/lists.page
index dfaba91..3858641 100644
--- a/hig3/C/lists.page
+++ b/hig3/C/lists.page
@@ -127,7 +127,7 @@
 <item><p>Differentiate the different types of information using different alignments, <link 
xref="typography">text colors and weights</link>. Highlight the most important and relevant information by 
giving other information a lighter weight and/or color.</p></item>
 <item><p>Be careful not to overpopulate lists with different columns and elements, and ensure that you only 
use them to present essential information.</p></item>
 <item><p>As a rule of thumb, avoid using several lists in the same window, particularly primary 
windows.</p></item>
-<item><p>Do not use lists with less than about five items, unless the number of items may increase over 
time. For options lists, check boxes or radio buttons can be used as an alternative in this case.</p></item>
+<item><p>Do not use lists with fewer than about five items, unless the number of items may increase over 
time. For options lists, check boxes or radio buttons can be used as an alternative in this case.</p></item>
 <item><p>Ensure that lists are ordered to be helpful to those who are using them. Recent documents might be 
more useful than alphabetically ordered documents, or contacts that are online might be more interesting than 
those who are offline, for example.</p></item>
 <item><p>If you use icons in your list, <link xref="icons-and-artwork">use symbolic icons</link>. The lower 
visual footprint of these icons will mean that they do not visually overload or dominate your list.</p></item>
 <item><p>If the list is long, make it possible to search it using the standard <link xref="search">search 
design pattern</link>.</p></item>
diff --git a/hig3/C/menu-bars.page b/hig3/C/menu-bars.page
index 9bb6437..9e231e5 100644
--- a/hig3/C/menu-bars.page
+++ b/hig3/C/menu-bars.page
@@ -33,7 +33,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<p>Menu bars increase the vertical footprint of an application's user interface, introduce a large number of 
disclosure points, and function as a fixed set of inflexible options. For these reasons, <link 
xref="header-bars">header bars</link> and <link xref="header-bar-menus">header bar menus</link> are generally 
recommended over menu bars, along with other design patterns for exposing controls on demand, such as <link 
xref="selection-mode">selection mode</link>, <link xref="action-bars">action bars</link>, and <link 
xref="popovers">popovers"</link>.</p>
+<p>Menu bars increase the vertical footprint of an application's user interface, introduce a large number of 
disclosure points, and function as a fixed set of inflexible options. For these reasons, <link 
xref="header-bars">header bars</link> and <link xref="header-bar-menus">header bar menus</link> are generally 
recommended over menu bars, along with other design patterns for exposing controls on demand, such as <link 
xref="selection-mode">selection mode</link>, <link xref="action-bars">action bars</link>, and <link 
xref="popovers">popovers</link>.</p>
 
 <p>At the same time, menu bars can still be an appropriate choice, particularly for applications that 
already incorporate a header bar. Some platforms also incorporate space for a menu bar in their user 
environment, and a menu model can be desirable for cross-platform integration purposes.</p>
 
@@ -94,7 +94,7 @@
 </section>
 
 <section id="saved-state-operations">
-<title>Saved state operation menu itmes</title>
+<title>Saved state operation menu items</title>
 
 <table>
 <thead>
@@ -539,7 +539,7 @@
 
 <p>The difference between these commands and those on the <gui>View</gui> menu is that changes made with 
Format commands are persistent and saved as part of the document, for example as HTML or RTF tags.</p>
 
-<p>Items found on the Format will be very application-specific, but some common items are listed in the 
table below.</p>
+<p>Items found on the Format menu will be very application-specific, but some common items are listed in the 
table below.</p>
 
 <table>
 <thead>
@@ -573,7 +573,7 @@
 <tr>
 <td><p><gui>Italic</gui></p></td>
 <td><p><keyseq><key>Ctrl</key><key>I</key></keyseq></p></td>
-<td><p>Toggles the italicisation of the current text selection on or off. If some of the selection is 
currently italicised and some is not, this command should italicise the selected text.</p></td>
+<td><p>Toggles the italicisation of the current text selection on or off. If some of the selection is 
currently italicized and some is not, this command should italicise the selected text.</p></td>
 </tr>
 <tr>
 <td><p><gui>Underline</gui></p></td>
diff --git a/hig3/C/menus.page b/hig3/C/menus.page
index 05bc3fa..eb572a1 100644
--- a/hig3/C/menus.page
+++ b/hig3/C/menus.page
@@ -24,7 +24,7 @@
 
 <title>Menus</title>
 
-<p>A list of actions and/or options which is revealed by selecting a heading or button or, in the case of 
context menus, by using a secondary click or long press on an item of content.</p>
+<p>A menu is a list of actions and/or options which is revealed by selecting a heading or button or, in the 
case of context menus, by using a secondary click or long press on an item of content.</p>
 
 <media type="image" mime="image/png" src="figures/menu.png"/>
 
@@ -43,7 +43,7 @@
 <title>Guidelines</title>
 
 <list>
-<item><p>Do not have menus with less than three or more than about 12 top-level items. Dialog windows 
containing a List can be used as an alternative to menus in many situations, including this one.</p></item>
+<item><p>Do not have menus with fewer than three or more than about 12 top-level items. Dialog windows 
containing a List can be used as an alternative to menus in many situations, including this one.</p></item>
 <item><p>Label menu items with verbs for commands and adjectives for settings, according to the 
capitalization rules in the Writing Style guidelines.</p></item>
 <item><p>Make a menu item insensitive when its command is unavailable.</p></item>
 <item><p>Provide an <link xref="keyboard-input#access-keys">access key</link> for every menu item. You may 
use the same access key on different menus in your application, but avoid duplicating access keys on the same 
menu. Note that unlike other controls, once a menu is displayed, its access keys may be used by just typing 
the letter; it is not necessary to press the Alt key at the same time.</p></item>
diff --git a/hig3/C/notifications.page b/hig3/C/notifications.page
index 4992db4..2008cf8 100644
--- a/hig3/C/notifications.page
+++ b/hig3/C/notifications.page
@@ -43,7 +43,7 @@
 <td><p>Title</p></td><td><p>The heading for the notification.</p></td>
 </tr>
 <tr>
-<td><p>Body</p></td><td><p>An optional block of text which gives extra detail about the notification. The 
notification body can include multiple paragraphs. eg. A snippet from the beginning of an email.</p></td>
+<td><p>Body</p></td><td><p>An optional block of text which gives extra detail about the notification. The 
notification body can include multiple paragraphs. e.g. A snippet from the beginning of an email.</p></td>
 </tr>
 <tr>
 <td><p>Default Action</p></td><td><p>This is the action that is triggered when the notification is 
activated.</p></td>
diff --git a/hig3/C/progress-bars.page b/hig3/C/progress-bars.page
index 70b741e..fa0b779 100644
--- a/hig3/C/progress-bars.page
+++ b/hig3/C/progress-bars.page
@@ -26,7 +26,7 @@
 
 <p>Progress bars are visual indicators of the progress of a task being carried out by the application.</p>
 
-<p>There are three main types of progress bar: time-remaining, typical-time, and intermediate.</p>
+<p>There are three main types of progress bar: time-remaining, typical-time, and indeterminate.</p>
 
 <media type="image" mime="image/png" src="figures/progress-bars.png"/>
 
@@ -34,8 +34,8 @@
 <title>Guidelines</title>
 
 <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 intermediate progress bars.</p></item>
-<item><p>Ensure that a 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>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>
 </list>
 
 </section>
@@ -43,7 +43,7 @@
 <section id="time-remaining-progress-bar">
 <title>Time-remaining progress bar</title>
 
-<p>Time-remaining progress bars indicate how much time remains in an operation. They also include a text 
which states how much time remains before the operation will be complete. Time-remaining bars are the most 
useful type of progress bar.</p>
+<p>Time-remaining progress bars indicate how much time remains in an operation. They also include text which 
states how much time remains before the operation will be complete. Time-remaining bars are the most useful 
type of progress bar.</p>
 
 <p>Use a time-remaining bar if you can display an initial estimate of an operation's remaining time and then 
periodically display updated estimates. Each updated estimate should be based on changes that have occurred 
and that will cause the operation to finish more quickly or more slowly. If the operation will finish more 
slowly, your application can display an updated estimate that is greater than the estimate previously 
displayed.</p>
 
diff --git a/hig3/C/search.page b/hig3/C/search.page
index d61e3e7..6c5d2d5 100644
--- a/hig3/C/search.page
+++ b/hig3/C/search.page
@@ -32,7 +32,7 @@
 <section id="search-bar">
 <title>The search bar</title>
 
-<p>The standard pattern for search in GNOME 3 utilises a special search bar which slides down from beneath 
the header bar.
+<p>The standard pattern for search in GNOME 3 utilizes a special search bar which slides down from beneath 
the header bar.
 
 In primary windows, the search bar is typically hidden until it is activated by the user. There are three 
common ways to activate search in this context:</p>
 
diff --git a/hig3/C/selection-mode.page b/hig3/C/selection-mode.page
index 64a3bfe..9bedf45 100644
--- a/hig3/C/selection-mode.page
+++ b/hig3/C/selection-mode.page
@@ -30,7 +30,7 @@
 <item><p>It is helpful for users to be able to perform actions on content items without opening 
them.</p></item>
 </list>
 
-<p>If it is more typical for users to perform actions on single content items, you might want to consider 
another design pattern, such as a context menu. Likewise, if there is only one action that can be performed 
on content items, a varient of selection mode can be used (an overlaid button could allow the action to be 
performed on items directly, rather than requiring them to be selected first, for example).</p>
+<p>If it is more typical for users to perform actions on single content items, you might want to consider 
another design pattern, such as a context menu. Likewise, if there is only one action that can be performed 
on content items, a variant of selection mode can be used (an overlaid button could allow the action to be 
performed on items directly, rather than requiring them to be selected first, for example).</p>
 
 </section>
 
diff --git a/hig3/C/sidebar-lists.page b/hig3/C/sidebar-lists.page
index 9a4f792..b0f7b5b 100644
--- a/hig3/C/sidebar-lists.page
+++ b/hig3/C/sidebar-lists.page
@@ -15,7 +15,7 @@
 
 <media type="image" mime="image/png" src="figures/sidebar.png"/>
 
-<p>A sidebar list allows different views to be switched between. Those views can contain groups of content 
items, single content items, or sets of controls. The sidebar divides the window in two, with content being 
shown on the opposite pane to the siderbar.</p>
+<p>A sidebar list allows different views to be switched between. Those views can contain groups of content 
items, single content items, or sets of controls. The sidebar divides the window in two, with content being 
shown on the opposite pane to the sidebar.</p>
 
 <p>Sidebar lists can be used in primary windows, either as a permanent fixture or an element that is shown 
on demand. They can also be used in dialog windows.</p>
 
@@ -30,7 +30,7 @@
 
 <list>
 <item><p>When content items have a narrow width, and don't require an immersive experience. A sidebar would 
be inappropriate for browsing videos for this reason, but is well-suited to contacts.</p></item>
-<item><p>When content items are dynamic. For messaging applications, where new content items appear or old 
ones are updated, a sidebar list provides the ability for someone to view one item while simulataneously 
being aware of updates to the overall message list.</p></item>
+<item><p>When content items are dynamic. For messaging applications, where new content items appear or old 
ones are updated, a sidebar list provides the ability for someone to view one item while simultaneously being 
aware of updates to the overall message list.</p></item>
 <item><p>When it is possible to filter a collection of content, and there are a large number of 
filters.</p></item>
 </list>
 
diff --git a/hig3/C/sliders.page b/hig3/C/sliders.page
index 8107d30..d4a05c1 100644
--- a/hig3/C/sliders.page
+++ b/hig3/C/sliders.page
@@ -36,7 +36,7 @@
 <p>Use a slider when:</p>
 
 <list>
-<item><p>The range of values is fixed and orderded, and when adjusting the value relative to its current 
value is more important than choosing an absolute value.</p></item>
+<item><p>The range of values is fixed and ordered, and when adjusting the value relative to its current 
value is more important than choosing an absolute value.</p></item>
 <item><p>It is useful for the user to control the rate of change of the value in real time.</p></item>
 </list>
 
diff --git a/hig3/C/switches.page b/hig3/C/switches.page
index 217ae00..22460d4 100644
--- a/hig3/C/switches.page
+++ b/hig3/C/switches.page
@@ -21,7 +21,7 @@
 
 <p>Switches should be used for controlling services or hardware that have a clear on/off logic. They are 
particularly appropriate when those services or hardware do not activate immediately (ie. there is a delay 
between the switch being operated and it having an effect), or when they affect the operation of the 
application in a significant way.</p>
 
-<p>When the control does not turn a function on or off, or when a function does not clearly have an on/off 
nature, a <link xref="check-boxes">check box</link> is a more appropriate option. For example, and alarm 
might be controlled using a switch, since it can be turned on or off. However, a check box is a better choice 
for an option to repeat that alarm on a daily basis, since alarm repetition is a configuration option, rather 
than starting or stopping a particular piece of functionality.</p>
+<p>When the control does not turn a function on or off, or when a function does not clearly have an on/off 
nature, a <link xref="check-boxes">check box</link> is a more appropriate option. For example, an alarm might 
be controlled using a switch, since it can be turned on or off. However, a check box is a better choice for 
an option to repeat that alarm on a daily basis, since alarm repetition is a configuration option, rather 
than starting or stopping a particular piece of functionality.</p>
 
 <p>When in doubt, use switches for important configuration options, and check boxes for minor 
sub-options.</p>
 
diff --git a/hig3/C/tabs.page b/hig3/C/tabs.page
index f6daa1c..e39d6e6 100644
--- a/hig3/C/tabs.page
+++ b/hig3/C/tabs.page
@@ -24,7 +24,7 @@
 
 <title>Tabs</title>
 
-<p>Tabs provide a way to break down a window into a series of views. They come two primary forms: fixed and 
dynamic. Fixed tabs provide a immutable set of defined views that are built into a user interface, primarily 
dialog windows. Dynamic tabs allow a user to view multiple documents or locations within an application's 
primary window.</p>
+<p>Tabs provide a way to break down a window into a series of views. They come in two primary forms: fixed 
and dynamic. Fixed tabs provide an immutable set of defined views that are built into a user interface, 
primarily dialog windows. Dynamic tabs allow a user to view multiple documents or locations within an 
application's primary window.</p>
 
 <media type="image" mime="image/png" src="figures/tabs.png"/>
 
diff --git a/hig3/C/text-fields.page b/hig3/C/text-fields.page
index ce91ef5..8de8868 100644
--- a/hig3/C/text-fields.page
+++ b/hig3/C/text-fields.page
@@ -51,7 +51,7 @@
 <list>
 <item><p>An icon at the beginning of the entry can be used to indicate its purpose - replacing the need for 
the entry to be labelled. Search entry fields are the classic example of this, where a search icon is placed 
on the left side of the entry field.</p></item>
 <item><p>If the text to be entered is case sensitive, a warning icon can be shown inside the text field if 
caps lock is on. This is typically shown on the right side of the entry.</p></item>
-<item><p>If it is a common for the text field to be cleared, a clear icon button can be placed inside the 
field, at the right side.</p></item>
+<item><p>If it is common for the text field to be cleared, a clear icon button can be placed inside the 
field, at the right side.</p></item>
 <item><p>If you place an icon in a text entry field (either as an indicator or a button), use its symbolic 
variant from the GNOME Symbolic Icon Theme.</p></item>
 </list>
 
diff --git a/hig3/C/toolbars.page b/hig3/C/toolbars.page
index de5d392..e5c945a 100644
--- a/hig3/C/toolbars.page
+++ b/hig3/C/toolbars.page
@@ -42,7 +42,7 @@
 
 <list>
 <item><p>Only include controls for the most important functions. Having too many toolbar controls reduces 
their efficiency by making them harder to find, and too many rows of toolbars reduces the amount of screen 
space available to the rest of the application.</p></item>
-<item><p>Utilise conventions for toolbars to increase familiarity. For example, the main toolbar in an 
office application will nearly always have New, Open and Save as its first three toolbar buttons. Similarly, 
the first few buttons in a browser application should always include Back, Forward, Stop and Reload, in that 
order.</p></item>
+<item><p>Utilize conventions for toolbars to increase familiarity. For example, the main toolbar in an 
office application will nearly always have New, Open and Save as its first three toolbar buttons. Similarly, 
the first few buttons in a browser application should always include Back, Forward, Stop and Reload, in that 
order.</p></item>
 <item><p>Place only the most commonly-used application functions on your toolbars. Don't just add buttons 
for every menu item.</p></item>
 <item><p>If you are using a <link xref="menu-bars">menu bar</link>, ensure that it includes all the 
functions that appear on you toolbar, either directly (i.e. an equivalent menu item) or indirectly (e.g. in 
the <guiseq><gui>Options</gui><gui>Settings</gui></guiseq> dialog).</p></item>
 <item><p>Toolbars shouldn't include buttons for <gui>Help</gui>, <gui>Close</gui> or <gui>Quit</gui>, as 
these are rarely used and the space is better used for more useful controls. Similarly, only provide buttons 
for <gui>Undo</gui>, <gui>Redo</gui> and the standard clipboard functions if there is space on the toolbar to 
do so without sacrificing more useful, application-specific controls.</p></item>
diff --git a/hig3/C/typography.page b/hig3/C/typography.page
index 58bdef3..6c47bcd 100644
--- a/hig3/C/typography.page
+++ b/hig3/C/typography.page
@@ -29,12 +29,12 @@
 <section id="variants-sizes-weights">
 <title>Variants, Sizes and Weights</title>
 
-<p>Different text weights and colours can and should be used to distinguish different kinds of information. 
At the same time, too many variants, sizes, and weights can make text harder to read and isn't an efficient 
or elegant way to convey information. Make an effort to minimize the range of font variants, sizes and 
weights.</p>
+<p>Different text weights and colors can and should be used to distinguish different kinds of information. 
At the same time, too many variants, sizes, and weights can make text harder to read and isn't an efficient 
or elegant way to convey information. Make an effort to minimize the range of font variants, sizes and 
weights.</p>
 
 <list>
 <item><p>Use smaller and/or lighter text for less important information, and heavier/darker text to attract 
attention to important text.</p></item>
 <item><p>Avoid the use of italic or oblique faces, as these are visually more complex, and can be 
distracting.</p></item>
-<item><p>Never capitalise every letter in a word or sentence. Shouting at your users isn't nice.</p></item>
+<item><p>Never capitalize every letter in a word or sentence. Shouting at your users isn't nice.</p></item>
 <item><p>Do not use graphical backdrops or "watermarks" behind text. These interfere with the contrast 
between the text and its background.</p></item>
 </list>
 
diff --git a/hig3/C/visual-layout.page b/hig3/C/visual-layout.page
index 4138567..e1181d0 100644
--- a/hig3/C/visual-layout.page
+++ b/hig3/C/visual-layout.page
@@ -26,16 +26,16 @@
 
 <title>Visual layout</title>
 
-<p>The visual layout of controls, information and content affects how easy it is to understand your 
application, as well as how beautiful it is. It is important to recognise that visual design has a strong 
impact on how much work is involved in using an application - poor layout results in users having to put 
inadditional effort, while good layout requires less effort.</p>
+<p>The visual layout of controls, information and content affects how easy it is to understand your 
application, as well as how beautiful it is. It is important to recognise that visual design has a strong 
impact on how much work is involved in using an application - poor layout results in users having to put in 
additional effort, while good layout requires less effort.</p>
 
-<p>Following these visual layout guidelines will help you to produce an application that is both beautiful, 
easy to understand, and efficient to use.</p>
+<p>Following these visual layout guidelines will help you to produce an application that is beautiful, easy 
to understand, and efficient to use.</p>
 
 <section id="general-guidelines">
 <title>General guidelines</title>
 
 <list>
 <item><p>An alignment point is an imaginary vertical or horizontal line through your window that touches the 
edge of one or more labels or controls in the window. Minimize the number of these - the fewer there are, the 
cleaner and simpler your layout will appear, and the easier it will be for people to understand.</p></item>
-<item><p>Align content and controls in your layout exactly. The eye is very sensitive to aligned and 
unaligned objects. If visual elements do not lines up, it will be hard for someone to scan them. Elements 
that do not quite line up will be distracting.</p></item>
+<item><p>Align content and controls in your layout exactly. The eye is very sensitive to aligned and 
unaligned objects. If visual elements do not line up, it will be hard for someone to scan them. Elements that 
do not quite line up will be distracting.</p></item>
 <item><p>Be consistent. Use the same amounts of spacing throughout.</p></item>
 <item><p>Organize related controls and information into groups, and use spacing to differentiate them. This 
makes an interface far easier to read and understand.</p>
 <list>