[gnome-devel-docs] Fixed several typos in strings

[Daniel Mustieles GarcÃa <dmustieles src gnome org>]

commit d0450786bf0e2113d815a54a203852db0431f23a
Author: Daniel Mustieles <daniel mustieles gmail com>
Date:   Sun Sep 30 11:29:12 2012 +0200

    Fixed several typos in strings

 platform-demos/C/textview.js.page |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/platform-demos/C/textview.js.page b/platform-demos/C/textview.js.page
index bf84a7f..49df7fb 100644
--- a/platform-demos/C/textview.js.page
+++ b/platform-demos/C/textview.js.page
@@ -25,12 +25,12 @@
   <media type="image" mime="image/png" src="media/textviewpenguinchat.png"/>
   <p>A TextView is really (or at least usually) a nested set of three objects.</p>
   <list>
-    <item><p>At the bottom is a <link href="http://www.roojs.org/seed/gir-1.2-gtk-3.0/gjs/Gtk.TextBuffer.html";>TextBuffer.</link> This holds the text itself.</p></item>
-    <item><p>In the middle is the <link href="http://www.roojs.org/seed/gir-1.2-gtk-3.0/gjs/Gtk.TextView.html";>TextView,</link> which is a widget that lets you see and edit the text in the buffer. It automatically resizes itself depending on how much text there is.</p></item>
-    <item><p>Since the automatic resizing can make a TextView unwieldy, you normally place it inside of a <link xref="scrolledwindow.js">ScrolledWindow.</link> Despite the name, it's not an actual window in terms of having a title bar and an X button; it's a widget you put on the application you're making, which acts like a window onto a more manageable chunk of a TextView. If the text in the buffer is too big to fit, scrollbars will appear.</p></item>
+    <item><p>At the bottom there is a <link href="http://www.roojs.org/seed/gir-1.2-gtk-3.0/gjs/Gtk.TextBuffer.html";>TextBuffer</link>. This holds the text itself.</p></item>
+    <item><p>In the middle there is the <link href="http://www.roojs.org/seed/gir-1.2-gtk-3.0/gjs/Gtk.TextView.html";>TextView</link>, which is a widget that lets you see and edit the text in the buffer. It automatically resizes itself depending on how much text there is.</p></item>
+    <item><p>Since the automatic resizing can make a TextView unwieldy, you normally place it inside of a <link xref="scrolledwindow.js">ScrolledWindow</link>. Despite the name, it's not an actual window in terms of having a title bar and an X button; it's a widget you put on the application you're making, which acts like a window onto a more manageable chunk of a TextView. If the text in the buffer is too big to fit, scrollbars will appear.</p></item>
   </list>
   <p>If you want to change what text is displayed in the TextView, you act on the TextBuffer, since it's what actually holds the text. The same goes for if you want to see what text someone typed in. This sample application lets you talk to a (make-believe) penguin, and checks the TextBuffer to see if you typed the word "fish" anywhere in it.</p>
-  <note><p>Real-life penguin populations are declining fast, because climate change is melting the ice that they live on and killing the fish that they eat. If you'd like to play a (somewhat silly) GNOME game based on this premise, take a look at <link href="http://pingus.seul.org/";>Pingus.</link></p></note>
+  <note><p>Real-life penguin populations are declining fast, because climate change is melting the ice that they live on and killing the fish that they eat. If you'd like to play a (somewhat silly) GNOME game based on this premise, take a look at <link href="http://pingus.seul.org/";>Pingus</link>.</p></note>
     <links type="section" />
 
   <section id="imports">