[gnome-devel-docs] Fix typos in platform-demos

From: David King <davidk src gnome org>
To: commits-list gnome org
Cc:
Subject: [gnome-devel-docs] Fix typos in platform-demos
Date: Thu, 2 Apr 2015 14:13:25 +0000 (UTC)
commit 5123847ece4991fc727a9f897ac3d6acaecf4d79
Author: Anders Jonsson <anders jonsson norsjovallen se>
Date:   Thu Apr 2 15:45:20 2015 +0200

    Fix typos in platform-demos
    
    https://bugzilla.gnome.org/show_bug.cgi?id=747243

 platform-demos/C/02_welcome_to_the_grid.js.page |    4 ++--
 platform-demos/C/buttonbox.py.page              |    4 ++--
 platform-demos/C/checkbutton.vala.page          |    2 +-
 platform-demos/C/entry.py.page                  |    2 +-
 platform-demos/C/gmenu.py.page                  |    4 ++--
 platform-demos/C/guitar-tuner.js.page           |    2 +-
 platform-demos/C/menubar.py.page                |    6 +++---
 platform-demos/C/menubar.vala.page              |    4 ++--
 platform-demos/C/photo-wall.c.page              |    4 ++--
 platform-demos/C/radiobutton.py.page            |    2 +-
 platform-demos/C/samples/dialog.vala            |    2 +-
 platform-demos/C/samples/entry.vala             |    2 +-
 platform-demos/C/samples/menubar.c              |    2 +-
 platform-demos/C/samples/scale.vala             |    2 +-
 platform-demos/C/samples/statusbar.c            |    2 +-
 platform-demos/C/samples/textview.vala          |    2 +-
 platform-demos/C/samples/toolbar.vala           |    2 +-
 platform-demos/C/samples/toolbar_builder.vala   |    2 +-
 platform-demos/C/samples/tooltip.vala           |    2 +-
 platform-demos/C/separator.py.page              |    2 +-
 platform-demos/C/weatherAutotools.js.page       |    4 ++--
 21 files changed, 29 insertions(+), 29 deletions(-)
---
diff --git a/platform-demos/C/02_welcome_to_the_grid.js.page b/platform-demos/C/02_welcome_to_the_grid.js.page
index 0a8810b..6f73f24 100644
--- a/platform-demos/C/02_welcome_to_the_grid.js.page
+++ b/platform-demos/C/02_welcome_to_the_grid.js.page
@@ -125,7 +125,7 @@ const WelcomeToTheGrid = new Lang.Class({
     <p>This code looks awfully complicated, but it's not. Here's what those numbers mean:</p>
     <list type="numbered">
       <item><p>The <em>first</em> number is what left-to-right position to put things in, starting from 0. 
Any widget that uses a 0 here goes all the way to the left.</p></item>
-      <item><p>The <em>second</em> number is what top-to-botton position to put a given widget in, starting 
from 0. The Label goes beneath the Image, so we give the Image a 0 and the Label a 1 here.</p></item>
+      <item><p>The <em>second</em> number is what top-to-bottom position to put a given widget in, starting 
from 0. The Label goes beneath the Image, so we give the Image a 0 and the Label a 1 here.</p></item>
       <item><p>The <em>third</em> and <em>fourth</em> numbers are how many columns and rows a widget should 
take up. We'll see how these work in a minute.</p></item>
     </list>
 
@@ -205,7 +205,7 @@ app.application.run (ARGV);
     <p>There are at least three ways we can get around that last one. First, we can set a margin_left or 
margin_right on one of the Labels:</p>
     <media type="image" mime="image/png" src="media/02_jsgrid_05.png"/>
 
-    <p>Second, we can set the Grid's column_homogenous property to true.</p>
+    <p>Second, we can set the Grid's column_homogeneous property to true.</p>
     <code mime="application/javascript"><![CDATA[
         // Create the Grid
         this._grid = new Gtk.Grid ({
diff --git a/platform-demos/C/buttonbox.py.page b/platform-demos/C/buttonbox.py.page
index 1cfc97d..bc8ca75 100644
--- a/platform-demos/C/buttonbox.py.page
+++ b/platform-demos/C/buttonbox.py.page
@@ -33,11 +33,11 @@
   </section>
 
   <section id="methods">
-    <title>Uselful methods for a ButtonBox widget</title>
+    <title>Useful methods for a ButtonBox widget</title>
     <list>
       <item><p>The layout of the ButtonBox are set with <code>set_layout(layout)</code>, where 
<code>layout</code> can be <code>Gtk.ButtonBoxStyle.SPREAD</code> (buttons are evenly spread across the box), 
<code>Gtk.ButtonBoxStyle.EDGE</code> (buttons are placed at the edges of the box), 
<code>Gtk.ButtonBoxStyle.START</code> (buttons are grouped towards the start of the box), 
<code>Gtk.ButtonBoxStyle.END</code> (buttons are grouped towards the end of the box), 
<code>Gtk.ButtonBoxStyle.CENTER</code> (buttons are centered in the box).</p></item>
       <item><p><code>set_child_secondary(button, is_secondary)</code> sets whether <code>button</code> 
should appear in a secondary group of children. A typical use of a secondary child is the help button in a 
dialog. This group appears after the other children if the style is <code>START</code>, <code>SPREAD</code> 
or <code>EDGE</code>, and before the other children if the style is <code>END</code>. If the style is 
<code>START</code> or <code>END</code>, then the secondary children are aligned at the other end of the 
button box from the main children. For the other styles, they appear immediately next to the main 
children.</p></item>
-      <item><p><code>set_child_non_homogeneous(button, is_non_homogeneous)</code> sets whether the child is 
exempted from homogeous sizing. Default value is <code>False</code>.</p></item>
+      <item><p><code>set_child_non_homogeneous(button, is_non_homogeneous)</code> sets whether the child is 
exempted from homogeneous sizing. Default value is <code>False</code>.</p></item>
       <item><p><code>set_spacing(spacing)</code> sets the spacing, in pixels, between the buttons of the 
box.</p></item>
     </list>
   </section>
diff --git a/platform-demos/C/checkbutton.vala.page b/platform-demos/C/checkbutton.vala.page
index cd16910..7bbde85 100644
--- a/platform-demos/C/checkbutton.vala.page
+++ b/platform-demos/C/checkbutton.vala.page
@@ -15,7 +15,7 @@
       <years>2012</years>
     </credit>
 
-    <desc>Create widgets with a disrete toggle button</desc>
+    <desc>Create widgets with a discrete toggle button</desc>
   </info>
 
   <title>CheckButton</title>
diff --git a/platform-demos/C/entry.py.page b/platform-demos/C/entry.py.page
index 5e86d77..0f9fc12 100644
--- a/platform-demos/C/entry.py.page
+++ b/platform-demos/C/entry.py.page
@@ -38,7 +38,7 @@
 
   <section id="methods">
     <title>Useful methods for an Entry widget</title>
-    <p>In line 14 the signal <code>"activate"</code> is connected to the callback function 
<code>cb_activate()</code> using <code><var>widget</var>.connect(<var>signal</var>, <var>callback 
function</var>)</code>. See <link xref="signals-callbacks.py"/> for a more detailed explanation. Some of the 
signals that a Gtk.Entry widget can emit are: <code>"activate"</code> (emitted when the user activates the 
Entry key); <code>"backspace"</code> (emitted when the user activates the Backspace or Shift-Backspace keys); 
<code>"copy-clipboard"</code> (Ctrl-c and Ctrl-Insert); <code>"paste-clipboard"</code> (Ctrl-v and 
Shift-Insert); <code>"delete-from-cursor"</code> (Delete, for deleting a character; Ctrl-Delete, for deleting 
a word); <code>"icon-press"</code> (emitted when the user clicks an activable icon); 
<code>"icon-release"</code> (emitted on the button release from a mouse click over an activable icon);  
<code>"insert-at-cursor"</code> (emitted when the user initiates the inserti
 on of a fixed string at the cursor); <code>"move-cursor"</code> (emitted when the user initiates a cursor 
movement); <code>"populate-popup"</code> (emitted before showing the context menu of the entry; it can be 
used to add items to it).</p>
+    <p>In line 14 the signal <code>"activate"</code> is connected to the callback function 
<code>cb_activate()</code> using <code><var>widget</var>.connect(<var>signal</var>, <var>callback 
function</var>)</code>. See <link xref="signals-callbacks.py"/> for a more detailed explanation. Some of the 
signals that a Gtk.Entry widget can emit are: <code>"activate"</code> (emitted when the user activates the 
Entry key); <code>"backspace"</code> (emitted when the user activates the Backspace or Shift-Backspace keys); 
<code>"copy-clipboard"</code> (Ctrl-c and Ctrl-Insert); <code>"paste-clipboard"</code> (Ctrl-v and 
Shift-Insert); <code>"delete-from-cursor"</code> (Delete, for deleting a character; Ctrl-Delete, for deleting 
a word); <code>"icon-press"</code> (emitted when the user clicks an activatable icon); 
<code>"icon-release"</code> (emitted on the button release from a mouse click over an activatable icon);  
<code>"insert-at-cursor"</code> (emitted when the user initiates the ins
 ertion of a fixed string at the cursor); <code>"move-cursor"</code> (emitted when the user initiates a 
cursor movement); <code>"populate-popup"</code> (emitted before showing the context menu of the entry; it can 
be used to add items to it).</p>
     <list>
       <item><p><code>get_buffer()</code> and <code>set_buffer(buffer)</code>, where <code>buffer</code> is a 
Gtk.EntryBuffer object, can be used to get and set the buffer for the entry.</p></item>
       <item><p><code>get_text()</code> and <code>set_text("some text")</code> can be used to get and set the 
content for the entry.</p></item>
diff --git a/platform-demos/C/gmenu.py.page b/platform-demos/C/gmenu.py.page
index 8edd1be..19d8c84 100644
--- a/platform-demos/C/gmenu.py.page
+++ b/platform-demos/C/gmenu.py.page
@@ -51,7 +51,7 @@ action = Gio.SimpleAction.new("name", parameter_type)</code>
       <p>where <code>"name"</code> is the name of the action and <code>parameter_type</code> is the type of 
the parameters that the action receives when being activated. This can be <code>None</code>, or 
<code>GLib.VariantType.new('s')</code> if the parameter is of type <code>str</code>, or instead of 
<code>'s'</code> a character as described <link 
href="http://developer.gnome.org/glib/unstable/glib-GVariantType.html";>here</link>. To create a new 
<em>stateful</em> (i.e. not stateless) action, use</p>
       <code>
 action = Gio.SimpleAction.new_stateful("name", parameter_type, initial_state)</code>
-      <p>where <code>initial_state</code> is defined as a GVariant - for instance 
<code>Glib.Variant.new_string('start')</code>; for a list of possiblities see <link 
href="http://developer.gnome.org/glib/unstable/glib-GVariant.html";>here</link>.</p></item>
+      <p>where <code>initial_state</code> is defined as a GVariant - for instance 
<code>Glib.Variant.new_string('start')</code>; for a list of possibilities see <link 
href="http://developer.gnome.org/glib/unstable/glib-GVariant.html";>here</link>.</p></item>
       <item><p><code>set_enabled(True)</code>  sets the action as enabled; an action must be enabled in 
order to be activated or in order to have its state changed from outside callers. This should only be called 
by the implementor of the action. Users of the action should not attempt to modify its enabled 
flag.</p></item>
       <item><p><code>set_state(state)</code>, where <code>state</code> is a GVariant, sets the state of the 
action, updating the 'state' property to the given value. This should only be called by the implementor of 
the action; users of the action should instead call <code>change_state(state)</code> (where 
<code>state</code> is as above) to request the change.</p></item>
     </list>
@@ -67,7 +67,7 @@ menu.append_item(about)</code>
       </item>
       <item><p>We can also add a whole subsection in a menu using <code>insert_section(position, label, 
section)</code>, <code>append_section(label, section)</code>, or <code>prepend_section(label, 
section)</code>, where <code>label</code> is the title of the subsection.</p></item>
       <item><p>To add a submenu that will expand and collapse, use <code>insert_submenu(position, label, 
section)</code>, <code>append_submenu(label, section)</code>, or <code>prepend_submenu(label, 
section)</code>, where <code>label</code> is the title of the subsection.</p></item>
-      <item><p>To remove an item from the menu, use <code>remove(postion)</code>.</p></item>
+      <item><p>To remove an item from the menu, use <code>remove(position)</code>.</p></item>
       <item><p>To set a label for the menu, use <code>set_label(label)</code>.</p></item>
     </list>
 
diff --git a/platform-demos/C/guitar-tuner.js.page b/platform-demos/C/guitar-tuner.js.page
index 8037e50..b730af1 100644
--- a/platform-demos/C/guitar-tuner.js.page
+++ b/platform-demos/C/guitar-tuner.js.page
@@ -121,7 +121,7 @@ function playSound(frequency){
   });
 }]]></code>
    <p>The first thing we need to do is decide what tunes we want to make when we push a button. The 
frequencies list takes care of that. After that we get to actually making the sounds with the function 
playSound. For function playSound we give as an input a frequency (that we just defined in the frequencies 
variable). First thing we need to construct is a pipeline, a source and a sink. For the source we set the 
frequency. To the pipeline we add both the source and the sink and then we tell it to keep playing. As a last 
thing we use the const Mainloop to get the pipeline to stop after a 500ms.</p>
-   <p>Now we have the method of playing a tune when clicking a button. Next well make the conncetions 
between pushing a button and playing the correct sound from that button.</p>
+   <p>Now we have the method of playing a tune when clicking a button. Next well make the connections 
between pushing a button and playing the correct sound from that button.</p>
   </section>
   <section id="connecting">
    <title>Connecting buttons to playSound</title>
diff --git a/platform-demos/C/menubar.py.page b/platform-demos/C/menubar.py.page
index e82002b..81042e2 100644
--- a/platform-demos/C/menubar.py.page
+++ b/platform-demos/C/menubar.py.page
@@ -16,7 +16,7 @@
       <email its:translate="no">tiffany antopolski gmail com</email>
       <years>2012</years>
     </credit>
-    <credit type="author coyright">
+    <credit type="author copyright">
       <name>Marta Maria Casetti</name>
       <email its:translate="no">mmcasetti gmail com</email>
       <years>2012</years>
@@ -124,7 +124,7 @@ self.add_action(new_action)</code>
 
     <p>Some actions, such as "copy" and "paste" deal with the window, not the application. Window actions 
should be created as part of the window class.</p>
 
-    <p>The complete example files contain both application actions and window actions.  The window actions 
are the ones usually included in the <link xref="gmenu.py">application menu</link> also.  It is not good 
practice to include window actions in the applcation menu. For demonstration purposes, the complete example 
files which follow include XML in the UI file which creates the application menu which includes a "New" and 
"Open" item, and these are hooked up to the same actions as the menubar items of the same name.</p>
+    <p>The complete example files contain both application actions and window actions.  The window actions 
are the ones usually included in the <link xref="gmenu.py">application menu</link> also.  It is not good 
practice to include window actions in the application menu. For demonstration purposes, the complete example 
files which follow include XML in the UI file which creates the application menu which includes a "New" and 
"Open" item, and these are hooked up to the same actions as the menubar items of the same name.</p>
   </section>
 
   <section id="choices">
@@ -173,7 +173,7 @@ self.add_action(shape_action)</code>
 
   <section id="translatable"><title>Translatable strings</title>
    <p>
-   Since GNOME applications are being translated into <link href="http://l10n.gnome.org/languages/";>many 
languages</link>, it is important that the strings in your application are translable.  To make a label 
translatable, simple set <code>translatable="yes"</code>:
+   Since GNOME applications are being translated into <link href="http://l10n.gnome.org/languages/";>many 
languages</link>, it is important that the strings in your application are translatable.  To make a label 
translatable, simple set <code>translatable="yes"</code>:
    </p>
 
      <code mime="application/xml"><![CDATA[<attribute name="label" 
translatable="yes">Quit</attribute>]]></code>
diff --git a/platform-demos/C/menubar.vala.page b/platform-demos/C/menubar.vala.page
index ef2188a..ed7fb07 100644
--- a/platform-demos/C/menubar.vala.page
+++ b/platform-demos/C/menubar.vala.page
@@ -145,7 +145,7 @@ void quit_cb (SimpleAction action, Variant? parameter) {
 
   <p>
    The complete example files contain both application actions and
-   window applications.  The window actions are the ones usually included in the <link 
xref="gmenu.vala">application menu</link> also.  It is not good practice to include window actions in the 
applcation menu. For demonstration purposes, the complete example files which follow include XML in the UI 
file which creates the application menu which includes a "New" and "Open" item, and these are hooked up to 
the same actions as the menubar items of the same name.
+   window applications.  The window actions are the ones usually included in the <link 
xref="gmenu.vala">application menu</link> also.  It is not good practice to include window actions in the 
application menu. For demonstration purposes, the complete example files which follow include XML in the UI 
file which creates the application menu which includes a "New" and "Open" item, and these are hooked up to 
the same actions as the menubar items of the same name.
   </p>
 
 
@@ -178,7 +178,7 @@ void quit_cb (SimpleAction action, Variant? parameter) {
 
   <section id="translatable"><title>Translatable strings</title>
    <p>
-   Since GNOME applications are being translated into <link href="http://l10n.gnome.org/languages/";>many 
languages</link>, it is important that the strings in your application are translable.  To make a label 
translatable, simple set <code>translatable="yes"</code>:
+   Since GNOME applications are being translated into <link href="http://l10n.gnome.org/languages/";>many 
languages</link>, it is important that the strings in your application are translatable.  To make a label 
translatable, simple set <code>translatable="yes"</code>:
    </p>
    <p>
      <code mime="application/xml"><![CDATA[<attribute name="label" 
translatable="yes">Quit</attribute>]]></code>
diff --git a/platform-demos/C/photo-wall.c.page b/platform-demos/C/photo-wall.c.page
index 7019725..4889365 100644
--- a/platform-demos/C/photo-wall.c.page
+++ b/platform-demos/C/photo-wall.c.page
@@ -41,7 +41,7 @@
 <section id="intro">
   <title>Introduction</title>
   <p>
-    Clutter is a library for creating dynamic user interfaces using OpenGL for hardware acceleration. This 
example demonstates a small, but central, part of the Clutter library to create a simple but attractive image 
viewing program.
+    Clutter is a library for creating dynamic user interfaces using OpenGL for hardware acceleration. This 
example demonstrates a small, but central, part of the Clutter library to create a simple but attractive 
image viewing program.
   </p>
   <p>
     To help us reach our goal we will be utilising a few other common pieces of GLib as well. Most 
importantly, we'll use one <code>GPtrArray</code>, a dynamic array of pointers, to hold the file path names. 
We will also use <code>GDir</code>, a utility for working with directories, to access our image directory and 
gather file paths.
@@ -276,7 +276,7 @@ load_image_path_names()
     }
 }]]></code>
   <list>
-    <item><p>Lines 5 and 12: This opens our directory or, if an error occured, returns after printing an 
error message.</p></item>
+    <item><p>Lines 5 and 12: This opens our directory or, if an error occurred, returns after printing an 
error message.</p></item>
     <item><p>Lines 16&#x2012;25: The first line gets another file name from the <code>GDir</code> we opened 
earlier. If there was an image file (which we check by looking at its extension, ".png" or ".jpg") in the 
directory we proceed to prepend the image directory path to the filename and prepend that to the list we set 
up earlier. Lastly we attempt to get the next path name and reenter the loop if another file was 
found.</p></item>
   </list>
 </section>
diff --git a/platform-demos/C/radiobutton.py.page b/platform-demos/C/radiobutton.py.page
index 0179794..d550f2e 100644
--- a/platform-demos/C/radiobutton.py.page
+++ b/platform-demos/C/radiobutton.py.page
@@ -39,7 +39,7 @@
     <code>
 button1 = Gtk.RadioButton()
 button1.set_label("Button 1").</code>
-    <p>Yet another way to create a new RadioButton with a label is <code>button1 = 
Gtk.RadioButton.new_with_label(None, "Button 1")</code> (the first arguement is the group of the 
radiobuttons, which we can get with <code>get_group()</code>, the second argument is the label).</p>
+    <p>Yet another way to create a new RadioButton with a label is <code>button1 = 
Gtk.RadioButton.new_with_label(None, "Button 1")</code> (the first argument is the group of the radiobuttons, 
which we can get with <code>get_group()</code>, the second argument is the label).</p>
   </section>
 
   <section id="references">
diff --git a/platform-demos/C/samples/dialog.vala b/platform-demos/C/samples/dialog.vala
index fa1dc8c..d803d7c 100644
--- a/platform-demos/C/samples/dialog.vala
+++ b/platform-demos/C/samples/dialog.vala
@@ -58,7 +58,7 @@ public class MyWindow : Gtk.ApplicationWindow {
 /* This is the application. */
 public class MyApplication : Gtk.Application {
 
-       /* The constructore of the application. */
+       /* The constructor of the application. */
        internal MyApplication () {
                Object (application_id: "org.example.MyApplication");
        }
diff --git a/platform-demos/C/samples/entry.vala b/platform-demos/C/samples/entry.vala
index f188715..1ef893b 100644
--- a/platform-demos/C/samples/entry.vala
+++ b/platform-demos/C/samples/entry.vala
@@ -45,7 +45,7 @@ class MyApplication : Gtk.Application {
 
 }
 
-/* The main function creats and runs the application. */
+/* The main function creates and runs the application. */
 int main (string[] args) {
        return new MyApplication ().run (args);
 }
diff --git a/platform-demos/C/samples/menubar.c b/platform-demos/C/samples/menubar.c
index dd1722e..3b23ee9 100644
--- a/platform-demos/C/samples/menubar.c
+++ b/platform-demos/C/samples/menubar.c
@@ -188,7 +188,7 @@ state_callback (GSimpleAction *simple,
          GVariant      *parameter,
          gpointer       user_data)
 {
-   /* The two possibilies in this case for the "answer" variable are either
+   /* The two possibilities in this case for the "answer" variable are either
     * "on" or "off".
     */
    const gchar *answer = g_variant_get_string (parameter, NULL);
diff --git a/platform-demos/C/samples/scale.vala b/platform-demos/C/samples/scale.vala
index 3b99883..4f4d9d4 100644
--- a/platform-demos/C/samples/scale.vala
+++ b/platform-demos/C/samples/scale.vala
@@ -36,7 +36,7 @@ public class MyApplication : Gtk.Application {
        }
 
        /* Callback function for "value-changed" signal.
-        * The paramter refers to the scale which emitted the signal.
+        * The parameter refers to the scale which emitted the signal.
         * Since we are accessing the values of not one, but two scales,
         * we made the ranges instance variables, and ignore the
         * parameter.
diff --git a/platform-demos/C/samples/statusbar.c b/platform-demos/C/samples/statusbar.c
index 8819710..0cda794 100644
--- a/platform-demos/C/samples/statusbar.c
+++ b/platform-demos/C/samples/statusbar.c
@@ -20,7 +20,7 @@ push_item (GtkWidget *widget,
   char hold_output[20];
   
   /*This is a safer form of the standard sprintf () function. The output is 
-  gauranteed in this case to not exceed 20 characters, and the result is stored 
+  guaranteed in this case to not exceed 20 characters, and the result is stored
   into the 'hold_output' variable*/
   g_snprintf (hold_output, 20, "Item %d", count++);
   gtk_statusbar_push (GTK_STATUSBAR (status_bar), 
diff --git a/platform-demos/C/samples/textview.vala b/platform-demos/C/samples/textview.vala
index e9bcde7..a4c2d3a 100644
--- a/platform-demos/C/samples/textview.vala
+++ b/platform-demos/C/samples/textview.vala
@@ -2,7 +2,7 @@
 public class MyApplication : Gtk.Application {
        /* Override the 'activate' signal of GLib.Application. */
        protected override void activate () {
-               /* Create the window of this applicationt. */
+               /* Create the window of this application. */
                new MyWindow (this).show_all ();
        }
 }
diff --git a/platform-demos/C/samples/toolbar.vala b/platform-demos/C/samples/toolbar.vala
index 45d0252..23eeac5 100644
--- a/platform-demos/C/samples/toolbar.vala
+++ b/platform-demos/C/samples/toolbar.vala
@@ -9,7 +9,7 @@ class MyWindow : Gtk.ApplicationWindow {
        Gtk.ToolButton fullscreen_button;
        Gtk.ToolButton leave_fullscreen_button;
 
-       /* Contstructor */
+       /* Constructor */
        internal MyWindow (MyApplication app) {
                Object (application: app, title: "Toolbar Example");
 
diff --git a/platform-demos/C/samples/toolbar_builder.vala b/platform-demos/C/samples/toolbar_builder.vala
index b23a725..644151b 100644
--- a/platform-demos/C/samples/toolbar_builder.vala
+++ b/platform-demos/C/samples/toolbar_builder.vala
@@ -7,7 +7,7 @@ class MyWindow : Gtk.ApplicationWindow {
        Gtk.ToolButton fullscreen_button;
        Gtk.ToolButton leave_fullscreen_button;
 
-       /* Contstructor */
+       /* Constructor */
        internal MyWindow (MyApplication app) {
                Object (application: app, title: "Toolbar Example");
 
diff --git a/platform-demos/C/samples/tooltip.vala b/platform-demos/C/samples/tooltip.vala
index 0401ec2..ff0dd3e 100644
--- a/platform-demos/C/samples/tooltip.vala
+++ b/platform-demos/C/samples/tooltip.vala
@@ -9,7 +9,7 @@ class MyWindow : Gtk.ApplicationWindow {
        Gtk.ToolButton fullscreen_button;
        Gtk.ToolButton leave_fullscreen_button;
 
-       /* Contstructor */
+       /* Constructor */
        internal MyWindow (MyApplication app) {
                Object (application: app, title: "Toolbar with Tooltips Example");
 
diff --git a/platform-demos/C/separator.py.page b/platform-demos/C/separator.py.page
index 3f856e0..9f1cd5c 100644
--- a/platform-demos/C/separator.py.page
+++ b/platform-demos/C/separator.py.page
@@ -5,7 +5,7 @@
       type="guide" style="task"
       id="separator.py">
   <info>
-    <title type="text">Seperator (Python)</title>
+    <title type="text">Separator (Python)</title>
     <link type="guide" xref="beginner.py#ornaments"/>
     <link type="seealso" xref="grid.py"/>
     <link type="next" xref="scrolledwindow.py" />
diff --git a/platform-demos/C/weatherAutotools.js.page b/platform-demos/C/weatherAutotools.js.page
index 053de4e..e3f0e83 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 overwiev 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>
@@ -135,7 +135,7 @@ AC_INIT([Weather App], 1.0)
 AM_INIT_AUTOMAKE([1.10 no-define foreign])
 AC_CONFIG_FILES(Makefile)
 AC_OUTPUT]]></code>
-    <p>autohen.sh</p>
+    <p>autogen.sh</p>
     <code mime="text/sh" style="numbered"><![CDATA[
 #!/bin/sh
 # This will run autoconf, automake, etc. for us
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]