[gnome-devel-docs] tutorials <javascript>: Adds <keyseq> to chapter one

[Tiffany Antopolski <antopolski src gnome org>]

commit c842d426972dd8b10eaeb0ad2278813adbaf28f8
Author: Taryn Fox <jewelfox fursona net>
Date:   Tue Aug 14 11:04:00 2012 -0400

    tutorials <javascript>: Adds <keyseq> to chapter one

 platform-demos/C/hellognome.js.page |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/platform-demos/C/hellognome.js.page b/platform-demos/C/hellognome.js.page
index 439bf0c..af8f3f3 100644
--- a/platform-demos/C/hellognome.js.page
+++ b/platform-demos/C/hellognome.js.page
@@ -117,7 +117,7 @@ const HelloGNOME = new Lang.Class ({
 ]]></code>
     <p>Here's some code you will more or less copy-and-paste for every JavaScript application you build. It creates a new Application, and then binds its activate and startup signals to functions that make the window show itself and build its user interface, respectively.</p>
     <p>What does that mean? Well, everything in a GNOME application sends out a signal when something important happens. A button might send out the clicked signal when you click on it, for instance. Our job is to connect the signals to functions which handle them, and make the things that we want to have happen occur. We do this using each object's connect method, which takes two arguments: The signal we want to handle, and the Lang.bind function, which we have to use to tell connect which function we want to have handle the signal.</p>
-    <p>In this case, we want _onActivate to handle the activate signal, and _onStartup to handle the startup signal. _onActivate just tells the window to present itself; so basically, whenever you <key>Alt</key> <key>Tab</key> to the application it appears, like you would expect it to. _onStartup calls _buildUI, which is the function that creates our user interface and is the next part that we will look at.</p>
+    <p>In this case, we want _onActivate to handle the activate signal, and _onStartup to handle the startup signal. _onActivate just tells the window to present itself; so basically, whenever you <keyseq><key>Alt</key> <key>Tab</key></keyseq> to the application it appears, like you would expect it to. _onStartup calls _buildUI, which is the function that creates our user interface and is the next part that we will look at.</p>
     <note style="tip"><p>When you copy and paste the above code for your own applications, be sure to change the name to a unique one each time.</p></note>
   </section>