GNOME.org
 

[gnome-devel-docs] Fix various typos.

commit a77420790289850f434265ebd5c54b58cf047742
Author: Sebastian Rasmussen <sebras gmail com>
Date:   Sat Feb 2 14:04:21 2019 +0100

    Fix various typos.
    
    Thank you aspell.

 accessibility-devel-guide/C/gtest.xml                 | 2 +-
 hig/C/icon-design.page                                | 2 +-
 hig/C/icons-and-artwork.page                          | 2 +-
 hig/C/in-app-notifications.page                       | 2 +-
 hig/C/info-bars.page                                  | 2 +-
 hig/C/pointer-and-touch-input.page                    | 2 +-
 hig/C/progress-spinners.page                          | 2 +-
 hig/C/switches.page                                   | 2 +-
 hig/C/writing-style.page                              | 2 +-
 platform-demos/C/photo-wall/CREDITS                   | 2 +-
 platform-demos/C/samples/aboutdialog.c                | 2 +-
 platform-demos/C/samples/buttonbox.js                 | 2 +-
 platform-demos/C/samples/fontchooserwidget.js         | 2 +-
 platform-demos/C/samples/scale.c                      | 2 +-
 platform-demos/C/samples/tooltip.c                    | 2 +-
 platform-demos/C/samples/tooltip.js                   | 2 +-
 platform-demos/C/samples/tooltip.py                   | 2 +-
 platform-demos/C/samples/tooltip.vala                 | 2 +-
 platform-demos/C/weatherAutotools.js.page             | 2 +-
 platform-overview/C/tech-eds.page                     | 2 +-
 programming-guidelines/C/databases.page               | 2 +-
 programming-guidelines/C/file-system.page             | 2 +-
 programming-guidelines/C/parallel-installability.page | 2 +-
 programming-guidelines/C/tooling.page                 | 2 +-
 style-guide/C/style-principles.page                   | 2 +-
 25 files changed, 25 insertions(+), 25 deletions(-)
---
diff --git a/accessibility-devel-guide/C/gtest.xml b/accessibility-devel-guide/C/gtest.xml
index 5405918e..d4f63a35 100644
--- a/accessibility-devel-guide/C/gtest.xml
+++ b/accessibility-devel-guide/C/gtest.xml
@@ -794,7 +794,7 @@ Accerciser and the GNOME Accessibility Architecture
 </screenshot>
 
 <para>
-<application>Accerciser</application> is an interactive Python accessibility explorer for the GNOME Desktop. 
It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct   
  information to assistive technologies and automated test frameworks. <application>Accerciser</application> 
has a simple plugin framework which you can use     to create custom views of accessibility information. Full 
documentation can be found <ulink url="http://library.gnome.org/devel/accerciser/stable";>in the Official 
Accerciser Manual</ulink>. For a demonstration of <application>Accerciser</application> and 
<application>PyATSPI</application> (Python-wrappered access and usage of AT-SPI), see <ulink 
url="http://live.gnome.org/Accessibility/PythonPoweredAccessibility";>this article</ulink>. For an excellent 
walkthrough from the author, see the article titled <ulink 
url="http://www.linuxjournal.com/article/9991";>Make Your Application Accessible with Accercise
 r</ulink

.

+<application>Accerciser</application> is an interactive Python accessibility explorer for the GNOME Desktop. 
It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct   
  information to assistive technologies and automated test frameworks. <application>Accerciser</application> 
has a simple plugin framework which you can use     to create custom views of accessibility information. Full 
documentation can be found <ulink url="http://library.gnome.org/devel/accerciser/stable";>in the Official 
Accerciser Manual</ulink>. For a demonstration of <application>Accerciser</application> and 
<application>PyATSPI</application> (Python-wrapped access and usage of AT-SPI), see <ulink 
url="http://live.gnome.org/Accessibility/PythonPoweredAccessibility";>this article</ulink>. For an excellent 
walkthrough from the author, see the article titled <ulink 
url="http://www.linuxjournal.com/article/9991";>Make Your Application Accessible with Accerciser<
 /ulink>.
 </para>
 <note>
 <para>
diff --git a/hig/C/icon-design.page b/hig/C/icon-design.page
index d39f62ff..eff34412 100644
--- a/hig/C/icon-design.page
+++ b/hig/C/icon-design.page
@@ -118,7 +118,7 @@
 <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>
 <item><p>Avoid using any perspective in symbolic icons, stick to a simple orthogonal view.</p></item>
-<item><p>When using unfilled strokes for an outline, try avoiding hairline (1px) and do at least a 2px 
stroke for the meain feature of the icon. </p></item>
+<item><p>When using unfilled strokes for an outline, try avoiding hairline (1px) and do at least a 2px 
stroke for the main feature of the icon. </p></item>
 <item><p>Symbolic icons are recolored at runtime to match the context, very much like a piece of text. While 
there are ways to “shade” parts of an icon by using opacity or creating duotone/pattern dithering, try 
avoiding these as much as possible.</p></item>
 <item><p>When a metaphor relies on the negative space, make sure it will work with the colors inverted. For 
example a camera lens spec/highlight will only work if lighter than the lens itself.</p></item>
 </list>
diff --git a/hig/C/icons-and-artwork.page b/hig/C/icons-and-artwork.page
index 7ff6391d..166b7496 100644
--- a/hig/C/icons-and-artwork.page
+++ b/hig/C/icons-and-artwork.page
@@ -65,7 +65,7 @@
 
 <list>
 <item><p>Think about 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>
-<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>
+<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 (i.e. a single line), and will not be recognizable without a corresponding “plus” add 
icon.</p></item>
 </list>
 
 </section>
diff --git a/hig/C/in-app-notifications.page b/hig/C/in-app-notifications.page
index e03cbf46..f7b0a904 100644
--- a/hig/C/in-app-notifications.page
+++ b/hig/C/in-app-notifications.page
@@ -30,7 +30,7 @@
 
 </section>
 
-<section id="guidelies">
+<section id="guidelines">
 <title>Guidelines</title>
 
 <list>
diff --git a/hig/C/info-bars.page b/hig/C/info-bars.page
index 02094553..ae396e12 100644
--- a/hig/C/info-bars.page
+++ b/hig/C/info-bars.page
@@ -30,7 +30,7 @@
 
 </section>
 
-<section id="guidelies">
+<section id="guidelines">
 <title>Guidelines</title>
 
 <list>
diff --git a/hig/C/pointer-and-touch-input.page b/hig/C/pointer-and-touch-input.page
index 4b3e4c33..32c1a14b 100644
--- a/hig/C/pointer-and-touch-input.page
+++ b/hig/C/pointer-and-touch-input.page
@@ -151,7 +151,7 @@
 <tr>
 <td><media type="image" mime="image/png" src="figures/touch/pinch-or-stretch.svg"/></td>
 <td><p>Touch surface with two fingers while bringing them closer or further apart.</p></td>
-<td><p>Changes the zoom level of the view (eg. Maps, Photos).</p></td>
+<td><p>Changes the zoom level of the view (e.g. Maps, Photos).</p></td>
 </tr>
 <tr>
 <td colspan="3"><p><em style="strong">Double tap</em></p></td>
diff --git a/hig/C/progress-spinners.page b/hig/C/progress-spinners.page
index a267244b..6a48291d 100644
--- a/hig/C/progress-spinners.page
+++ b/hig/C/progress-spinners.page
@@ -42,7 +42,7 @@
 <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 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 progress 
through sub-components of the task (eg. modules downloaded, or pages exported).</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 progress 
through sub-components of the task (e.g. modules downloaded, or pages exported).</p></item>
 </list>
 
 </section>
diff --git a/hig/C/switches.page b/hig/C/switches.page
index 611d22ac..5ed01e06 100644
--- a/hig/C/switches.page
+++ b/hig/C/switches.page
@@ -24,7 +24,7 @@
 <section id="when-to-use">
 <title>When to use</title>
 
-<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>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 (i.e. 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, 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>
 
diff --git a/hig/C/writing-style.page b/hig/C/writing-style.page
index 74fbe01c..232c9413 100644
--- a/hig/C/writing-style.page
+++ b/hig/C/writing-style.page
@@ -51,7 +51,7 @@
 <item><p>Use the standard GNOME terms when referring to parts of the user interface, such as “pointer” and 
“window”. The HIG can be used as a reference in this regard.</p></item>
 <item><p>Avoid repetition where possible.</p></item>
 <item><p>Sentences should not be constructed from text in several controls, and each label should be treated 
as being self-contained. Sentences that run from one control to another will often not make sense when 
translated into other languages.</p></item>
-<item><p>Latin abbreviations such as “ie” or “eg” should be avoided, since they can't always be easily 
translated and can be unintelligible when read by screen readers. Instead, use full words like “for 
example”.</p></item>
+<item><p>Latin abbreviations such as “i.e.” or “e.g.” should be avoided, since they can't always be easily 
translated and can be unintelligible when read by screen readers. Instead, use full words like “for 
example”.</p></item>
 </list>
 
 </section>
diff --git a/platform-demos/C/photo-wall/CREDITS b/platform-demos/C/photo-wall/CREDITS
index c381ecce..1f69b96b 100644
--- a/platform-demos/C/photo-wall/CREDITS
+++ b/platform-demos/C/photo-wall/CREDITS
@@ -1,4 +1,4 @@
-This beautiful images images were pulled from Flickr and are licenced under a Creative Commons license.
+This beautiful images images were pulled from Flickr and are licensed under a Creative Commons license.
 
 Here are links to the original photos where you'll also find information pertaining to the photographer and 
the license.
 
diff --git a/platform-demos/C/samples/aboutdialog.c b/platform-demos/C/samples/aboutdialog.c
index cffb4805..82c21e48 100644
--- a/platform-demos/C/samples/aboutdialog.c
+++ b/platform-demos/C/samples/aboutdialog.c
@@ -26,7 +26,7 @@ about_cb (GSimpleAction *simple,
 
   about_dialog = gtk_about_dialog_new ();
 
-  /* Lists of authors/ documentators to be used later, they must be initialized
+  /* Lists of authors/ documenters to be used later, they must be initialized
    * in a null terminated array of strings.
    */
   const gchar *authors[] = {"GNOME Documentation Team", NULL};
diff --git a/platform-demos/C/samples/buttonbox.js b/platform-demos/C/samples/buttonbox.js
index 263974e0..a8ac1db0 100644
--- a/platform-demos/C/samples/buttonbox.js
+++ b/platform-demos/C/samples/buttonbox.js
@@ -7,7 +7,7 @@ const Gtk = imports.gi.Gtk;
 
 class ButtonBoxExample {
 
-    // Create the application itthis
+    // Create the application itself
     constructor() {
         this.application = new Gtk.Application({
             application_id: 'org.example.jsbuttonbox'
diff --git a/platform-demos/C/samples/fontchooserwidget.js b/platform-demos/C/samples/fontchooserwidget.js
index c510f31d..7cddd3e7 100644
--- a/platform-demos/C/samples/fontchooserwidget.js
+++ b/platform-demos/C/samples/fontchooserwidget.js
@@ -5,7 +5,7 @@ const Gtk = imports.gi.Gtk;
 
 class FontChooserWidgetExample {
 
-    // Create the application itthis
+    // Create the application itself
     constructor() {
         this.application = new Gtk.Application({ application_id: 'org.example.fontchooserwidget' });
 
diff --git a/platform-demos/C/samples/scale.c b/platform-demos/C/samples/scale.c
index c384c01c..5550f9ed 100644
--- a/platform-demos/C/samples/scale.c
+++ b/platform-demos/C/samples/scale.c
@@ -111,7 +111,7 @@ activate (GtkApplication *app,
 
 
   /* Create the Vertical scale. This time, we will see what happens 
-   * when the digits arent initially set.
+   * when the digits aren't initially set.
    */
   v_scale = gtk_scale_new (GTK_ORIENTATION_VERTICAL, vadjustment);
   gtk_widget_set_vexpand (v_scale, TRUE);
diff --git a/platform-demos/C/samples/tooltip.c b/platform-demos/C/samples/tooltip.c
index 7a136bba..5fd7e4c7 100644
--- a/platform-demos/C/samples/tooltip.c
+++ b/platform-demos/C/samples/tooltip.c
@@ -11,7 +11,7 @@ undo_tooltip_callback (GtkStatusIcon *status_icon,
   /* set the text for the tooltip */
   gtk_tooltip_set_text (tooltip, "Undo your last action");
    
-  /* set an icon fot the tooltip */
+  /* set an icon for the tooltip */
   gtk_tooltip_set_icon_from_stock(tooltip, "gtk-undo", GTK_ICON_SIZE_MENU);
 
   /* show the tooltip */
diff --git a/platform-demos/C/samples/tooltip.js b/platform-demos/C/samples/tooltip.js
index f03c2ef7..cff30537 100644
--- a/platform-demos/C/samples/tooltip.js
+++ b/platform-demos/C/samples/tooltip.js
@@ -129,7 +129,7 @@ class TooltipExample {
     _undoTooltipCallback(widget, x, y, keyboard_mode, tooltip) {
         // set the text for the tooltip
         tooltip.set_text("Undo your last action");
-        // set an icon fot the tooltip
+        // set an icon for the tooltip
         tooltip.set_icon_from_stock(Gtk.STOCK_UNDO, Gtk.IconSize.MENU);
         // show the tooltip
         return true;
diff --git a/platform-demos/C/samples/tooltip.py b/platform-demos/C/samples/tooltip.py
index 54de9332..01885894 100644
--- a/platform-demos/C/samples/tooltip.py
+++ b/platform-demos/C/samples/tooltip.py
@@ -77,7 +77,7 @@ class MyWindow(Gtk.ApplicationWindow):
     def undo_tooltip_callback(self, widget, x, y, keyboard_mode, tooltip):
         # set the text for the tooltip
         tooltip.set_text("Undo your last action")
-        # set an icon fot the tooltip
+        # set an icon for the tooltip
         tooltip.set_icon_from_stock("gtk-undo", Gtk.IconSize.MENU)
         # show the tooltip
         return True
diff --git a/platform-demos/C/samples/tooltip.vala b/platform-demos/C/samples/tooltip.vala
index ff0dd3ee..fb423f36 100644
--- a/platform-demos/C/samples/tooltip.vala
+++ b/platform-demos/C/samples/tooltip.vala
@@ -40,7 +40,7 @@ class MyWindow : Gtk.ApplicationWindow {
                /* set the text for the tooltip */
                tooltip.set_text ("Undo your last action");
                
-               /* set an icon fot the tooltip */
+               /* set an icon for the tooltip */
                tooltip.set_icon_from_stock("gtk-undo", Gtk.IconSize.MENU);
 
                /* show the tooltip */
diff --git a/platform-demos/C/weatherAutotools.js.page b/platform-demos/C/weatherAutotools.js.page
index 76941994..7841d501 100644
--- a/platform-demos/C/weatherAutotools.js.page
+++ b/platform-demos/C/weatherAutotools.js.page
@@ -30,7 +30,7 @@
 
   <section id ="autotools">
   <title>Autotools and necessary files</title>
-  <p>Having more than one file in your folder makes using autotools a bit tricky. You need the .desktop 
file, autogen.sh, Makefile.am, configure.ac and as a new file: myapp.sh.in file. Hacking the autotools file 
is a complicated field. More information can be found in many different sources, <link 
href="http://en.wikipedia.org/wiki/GNU_build_system";>the wikipedia article</link> provides a good overview on 
the subject.
+  <p>Having more than one file in your folder makes using autotools a bit tricky. You need the .desktop 
file, autogen.sh, Makefile.am, configure.ac and as a new file: myapp.sh.in file. Hacking the autotools file 
is a complicated field. More information can be found in many different sources, <link 
href="http://en.wikipedia.org/wiki/GNU_build_system";>the Wikipedia article</link> provides a good overview on 
the subject.
   </p>
     <list>
       <item><p>weatherapp.desktop</p></item>
diff --git a/platform-overview/C/tech-eds.page b/platform-overview/C/tech-eds.page
index 90325017..8db00a85 100644
--- a/platform-overview/C/tech-eds.page
+++ b/platform-overview/C/tech-eds.page
@@ -15,7 +15,7 @@
 
     <include href="cc-by-sa-3-0.xml" xmlns="http://www.w3.org/2001/XInclude"/>
 
-    <desc>Desktop-wide addressbook for contacts and calendar</desc>
+    <desc>Desktop-wide address book for contacts and calendar</desc>
   </info>
 
 <title>Evolution Data Server</title>
diff --git a/programming-guidelines/C/databases.page b/programming-guidelines/C/databases.page
index 58f69f89..9a418627 100644
--- a/programming-guidelines/C/databases.page
+++ b/programming-guidelines/C/databases.page
@@ -135,7 +135,7 @@
       GVDB is only available as a copy-and-paste library; fetch the most recent
       copy of the code from
       <link href="https://git.gnome.org/browse/gvdb";>GVDB git</link> and copy
-      it into your project. It is licenced under LGPLv2.1+.
+      it into your project. It is licensed under LGPLv2.1+.
     </p>
 
     <p>
diff --git a/programming-guidelines/C/file-system.page b/programming-guidelines/C/file-system.page
index 74b93d68..2b33107b 100644
--- a/programming-guidelines/C/file-system.page
+++ b/programming-guidelines/C/file-system.page
@@ -170,7 +170,7 @@
     </p>
 
     <p>
-      As a second line of defence, all projects which access the file system
+      As a second line of defense, all projects which access the file system
       should consider providing a mandatory access control profile, using a
       system such as <link href="http://apparmor.net/";>AppArmor</link> or
       <link href="http://selinuxproject.org/";>SELinux</link>, which limits the
diff --git a/programming-guidelines/C/parallel-installability.page 
b/programming-guidelines/C/parallel-installability.page
index 1ebeae40..ce7d3b35 100644
--- a/programming-guidelines/C/parallel-installability.page
+++ b/programming-guidelines/C/parallel-installability.page
@@ -12,7 +12,7 @@
       <years>2002</years>
       <!-- Heavily based off Havoc’s original article about parallel
            installability: http://ometer.com/parallel.html.
-           Licence CC-BY-SA 3.0 confirmed by e-mail with him. -->
+           License CC-BY-SA 3.0 confirmed by e-mail with him. -->
     </credit>
     <credit type="author copyright">
       <name>Philip Withnall</name>
diff --git a/programming-guidelines/C/tooling.page b/programming-guidelines/C/tooling.page
index 8938635d..015849c2 100644
--- a/programming-guidelines/C/tooling.page
+++ b/programming-guidelines/C/tooling.page
@@ -128,7 +128,7 @@
       <link 
href="http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_compiler_flags.m4";>
       <file>ax_compiler_flags.m4</file></link> to the <file>m4/</file> directory
       of your project. Note that it depends on the following autoconf-archive
-      macros which are GPL-licenced so potentially cannot be copied in-tree.
+      macros which are GPL-licensed so potentially cannot be copied in-tree.
       They may have to remain in autoconf-archive, with that as a build time
       dependency of the project:
     </p>
diff --git a/style-guide/C/style-principles.page b/style-guide/C/style-principles.page
index bcd16432..be9eee42 100644
--- a/style-guide/C/style-principles.page
+++ b/style-guide/C/style-principles.page
@@ -56,7 +56,7 @@
  <p>Write directly to your reader. It's fine to use "you" and "your" - there is no need to always write 
abstractly, or for the third person. That doesn't mean that every sentence should be addressed directly to 
the reader, though.</p>
  <p>Being direct also means cutting out waffle. Don't labor points (unless it's important to do so), don't 
over-describe things, and don't waste the user's time with introductory text. The most important information 
should go first - defer asides until later on.</p>
  <p>Prefer shorter sentences with fewer clauses, but keep your writing friendly and natural. Being a little 
terse is OK as long as the text flows well.</p>
- <p>You should also refrain from using flowery or excessively exuberant language. Trying to write in a 
poetic or learned manner can obscure the meaning of the content; too much enthusiasm can be offputting or 
patronizing.</p>
+ <p>You should also refrain from using flowery or excessively exuberant language. Trying to write in a 
poetic or learned manner can obscure the meaning of the content; too much enthusiasm can be off-putting or 
patronizing.</p>
 </section>
 
 <section id="sufficient">
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]