--- a/gallery/Overview.html	Tue Jul 10 14:05:46 2012 -0400
+++ b/gallery/Overview.html	Wed Jul 11 00:14:55 2012 -0400
@@ -7,7 +7,7 @@
     <script type="text/javascript" class='remove'>
         var respecConfig = {
               specStatus: "ED",
-              shortName: "gallery-api",
+              shortName: "gallery",
               editors: [{
                         name: "송정기(Jungkee Song)", 
                         url: "", 
@@ -41,14 +41,14 @@
 
     <section id='sotd'>
       <p>
-        This document recasted the previous pure JavaScript APIs version as an API built using Web Intents, while refining the metadata format based on related media data definitions and practical web-based media services.
+        This document recasts the previous pure JavaScript APIs version as an API built using Web Intents, while refining the metadata format based on related media data definitions and practical web-based media services.
       </p>
     </section>
 
     <section class="informative">
       <h2>Introduction</h2>
       <p>
-        On account of a number of media applications and services accessed from various devices, users tend to maintain their media data in multiple sources including local stroage of devices and web-based media gallleries. For instance, users upload subset of their photos to several different social media galleries with different metadata. For another example, users collect their favorite audio and video resources in several different media galleries which provide inconsistent metadata attributes one another.
+        On account of a number of media applications and services accessed from various devices, users tend to maintain their media data in multiple sources including local storage of devices and web-based media galleries. For instance, users upload subset of their photos to several different social media galleries with different metadata. For another example, users collect their favourite audio and video resources in several different media galleries which provide inconsistent metadata attributes one another.
       </p>
       <p class="note">
               A terminology, <b>media object</b>, is used hereunder to denote <b>media data</b> that contain a media content and its related metadata. (See <a>Media</a> dictionary)
@@ -57,7 +57,7 @@
         This specification enables a Web application to have access to a selected subset of user's media objects, obtained from arbitrary services not known to the Web application. The interactions, brokered using Web Intents [[WEBINTENTS]] are designed in order to maximise the user's security and privacy. Media objects may be sourced from a plurality of sources — both online and local to the user's device — so long as those sources are registered as Intent services with the user agent. It defines a common media object format which services use to provide data to Web applications in a consistent and interoperable manner.
       </p>
       <p>
-        For a Pick Media Intent request, user permission can be naturally asked by a necessary user authentication process that a service implementer MAY provide. Also, users can determine the result media objects to bring to the client with the searching and selecting functionalities that a service implemeter MAY provide.
+        For a Pick Media Intent request, user permission can be naturally asked by a necessary user authentication process that a service implementer MAY provide. Also, users can determine the result media objects to bring to the client with the searching and selecting functionalities that a service implementer MAY provide.
       </p>
       <p>
         A set of <a href="#security-and-privacy-considerations">Security and Privacy Considerations</a> are
@@ -352,7 +352,7 @@
           <dt>unsigned long? likeCount</dt>
           <dd>
             <p>
-              The count of the vote in favor of the media resource.
+              The count of the vote in favour of the media resource.
             </p>
           </dd>
           <dt>float? rating</dt>
@@ -373,7 +373,7 @@
               The frame size of the resource (e.g., width and height of 720 and 480 in px is represented as 720*480+px).
             </p>
             <p class="note">
-              If the usage of this property is frequent, a seperate dictionary can be defined refering to frameSize property defined in [<a href="http://www.w3.org/TR/2012/REC-mediaont-10-20120209/#core-property-lists">Ontology for Media Resources 1.0</a>]
+              If the usage of this property is frequent, a separate dictionary can be defined referring to frameSize property defined in [<a href="http://www.w3.org/TR/2012/REC-mediaont-10-20120209/#core-property-lists">Ontology for Media Resources 1.0</a>]
             </p>
           </dd>
           <dt>unsigned long? samplingRate</dt>
@@ -421,7 +421,7 @@
       </section>
 
       <section>
-        <h2>The <a>MeidaError</a> dictionary</h2>
+        <h2>The <a>MediaError</a> dictionary</h2>
         <p>
           If the <a>media service</a> encounters an error then it MUST return an error 
           (through <code>postFailure()</code>) using the <a>MediaError</a> dictionary.
@@ -462,7 +462,7 @@
       var limit = window.intent.extra.limit;     // maximum number of objects to return
 
       // do search relevant media objects based on the extras
-      var mediaObjectArray = searchMediaobjects(keyword, filters, limit);
+      var mediaObjectArray = searchMediaObjects(keyword, filters, limit);
       
       if (mediaObjectArray) {
           window.intent.postResult(mediaObjectArray);