[gnome-devel-docs] tutorials: fixed validation errors using latest yelp-check.

[Tiffany Antopolski <antopolski src gnome org>]

commit c6aeed5f3b4482cb4f21085925c0fd66a10589e2
Author: Tiffany Antopolski <tiffany antopolski gmail com>
Date:   Sun Apr 8 00:44:38 2012 -0400

    tutorials: fixed validation errors using latest yelp-check.

 platform-demos/C/bug-filing.page      |    1 -
 platform-demos/C/helloWorld.js.page   |    2 +-
 platform-demos/C/help.vala.page       |    3 ++-
 platform-demos/C/message-board.c.page |    4 +---
 platform-demos/C/translate.page       |    2 +-
 platform-demos/C/weatherApp.js.page   |    2 +-
 6 files changed, 6 insertions(+), 8 deletions(-)
---
diff --git a/platform-demos/C/bug-filing.page b/platform-demos/C/bug-filing.page
index 94b4f4a..b1c981c 100644
--- a/platform-demos/C/bug-filing.page
+++ b/platform-demos/C/bug-filing.page
@@ -4,7 +4,6 @@
 
   <info>
     <link type="guide" xref="index#get-involved"/>
-    <link type="seealso" xref="commandline"/>
     <revision pkgversion="3.4" version="0.1" date="2012-02-06" status="candidate"/>
     <credit type="editor copyright">
       <name>Tiffany Antopolski</name>
diff --git a/platform-demos/C/helloWorld.js.page b/platform-demos/C/helloWorld.js.page
index 6c85c8d..f59ab44 100644
--- a/platform-demos/C/helloWorld.js.page
+++ b/platform-demos/C/helloWorld.js.page
@@ -55,7 +55,7 @@ Gtk.init(null, 0);
 var mywindow = new Gtk.Window({type: Gtk.WindowType.TOPLEVEL});
 mywindow.title = "Hello World!";
 mywindow.connect("destroy", function(){Gtk.main_quit()});
-</code>
+]]></code>
     <p>After importing Gtk, we need to initialize it. After that, we can start building our first window. We do this by creating a variable called mywindow and assigning it a new Gtk.Window of type TOPLEVEL.</p> <p>After setting up our first window we'll give the window a property called title. The title can be any string you want it to be. To be on the safe side, it's best to stick to UTF-8 encoding.</p> <p>The next thing we need to do for our application is connect the close button that's automatically generated along with the window to the close functionality. That happens with the method connect(). When the close button is pressed it gives out the signal "destroy", so in this part we're connecting the "destroy" signal to function(){Gtk.main_quit()}, which does the actual closing.</p><p>Now we have a window that has a title and a working "close" button. Let's add the actual "Hello, world" text.</p>
     </section>
     
diff --git a/platform-demos/C/help.vala.page b/platform-demos/C/help.vala.page
index 1f8bb51..c034b5a 100644
--- a/platform-demos/C/help.vala.page
+++ b/platform-demos/C/help.vala.page
@@ -2,6 +2,7 @@
       type="topic" style="task"
       id="help.vala">
   <info>
+    <link type="guide" xref="beginner.vala#tutorials" />
     <revision version="0.1" date="2012-02-20" status="stub"/>
 
     <credit type="author copyright">
@@ -13,6 +14,6 @@
     <desc></desc>
   </info>
 
-  <title>Connecting the Help</title>
+  <title>vii. Connecting the Help</title>
 
 </page>
diff --git a/platform-demos/C/message-board.c.page b/platform-demos/C/message-board.c.page
index aa1bd83..b6d3c94 100644
--- a/platform-demos/C/message-board.c.page
+++ b/platform-demos/C/message-board.c.page
@@ -34,9 +34,7 @@
 
 <media type="video" mime="video/ogg" src="media/message-board.ogv"/>
 
-<comment>
-<e:links type="section" xmlns:e="http://projectmallard.org/experimental/"/>
-</comment>
+<links type="section"/>
 
 <section id="create">
   <title>Create a project in Anjuta</title>
diff --git a/platform-demos/C/translate.page b/platform-demos/C/translate.page
index f2f99e0..b62ec91 100644
--- a/platform-demos/C/translate.page
+++ b/platform-demos/C/translate.page
@@ -28,7 +28,7 @@
  There are <link href="http://l10n.gnome.org/module/gnome-devel-docs/";>many languages</link> for which translations are still needed.
 </p>
 <p>
-To start translating you will need to <link href="http:l10n.gnome.org">create an account</link> and join the <link href="http://l10n.gnome.org/teams/";>translation team</link> for your language. This will give you the ability to upload new translations.
+To start translating you will need to <link href="http://l10n.gnome.org";>create an account</link> and join the <link href="http://l10n.gnome.org/teams/";>translation team</link> for your language. This will give you the ability to upload new translations.
 </p>
 
 <p>
diff --git a/platform-demos/C/weatherApp.js.page b/platform-demos/C/weatherApp.js.page
index 9aa1990..f59cdf6 100644
--- a/platform-demos/C/weatherApp.js.page
+++ b/platform-demos/C/weatherApp.js.page
@@ -36,7 +36,7 @@
     <title>Planning the graphical user interface</title>
     <p> Structuring an application for GNOME 3 means you will be using <link href="http://developer.gnome.org/platform-overview/stable/gtk";>GTK+</link>. The most important thing is to remember that the main window will only accept one widget. You must plan your structure accordingly (this example is using Gtk.Grid). A useful method is to draw out the main window and place every widget needed inside that box. By looking at an image of your future application it is easier to tell what are the relations between widgets. For example Gtk.Grid places your widgets in relation to other widgets, so after the first widget is in place, placing widgets can be done in relation to any widget on the grid. </p>
   </section>
-  <section id ="Asynchronous">
+  <section id ="asynchronous">
     <title>Asynchronous calls</title>
     <p> With many programming languages, all operations are run synchronously - you tell the program to do something, and it will wait until that action completes before proceeding. This is however bad for
     graphical user interfaces, as then the whole application will be frozen while the program waits for