Index: trunk/doc/user/06_feature/gpmi/History
===================================================================
--- trunk/doc/user/06_feature/gpmi/History	(revision 8728)
+++ trunk/doc/user/06_feature/gpmi/History	(revision 8729)
@@ -1,10 +1,10 @@
 History
 ~~~~~~~
 As of October 2006, PCB has native support for external (or dynamic
-loadable) HIDs. This project is plugin that provides scripting features.
+loadable) HIDs. This project is a plugin that provides scripting features.
 
-For a long time I believe that good applications should be scriptable,
-and real good ones should not restrict scripting to one or two languages.
+For a long time I have believed that good applications should be scriptable,
+and really good ones should not restrict scripting to one or two languages.
 For this reason I have been working on GPMI with various other developers
 for years. GPMI provides a general way to split up big applications in
 smaller, usually dynamic loadable parts, and encourages that some of these
@@ -14,19 +14,19 @@
 plugins and support plugins that do all the high-level job for the user.
 
 PCB is an old and big software, with a stable user base. Restructuring the
-whole source to "GPMIize" it is no option. Instead, a nice compromise is
+whole source to "GPMIize" it is not an option. Instead, a nice compromise is
 implementing this functionality in a plugin that pcb can load for the users
 who are interested in such extras.
 
-From 2006 to 2009 spring the project was on hold, because I was nagging
+From 2006 to spring 2009 the project was on hold, because I was nagging
 PCB developers to add support for customizable dialog boxes. In late March
 2009, PCB developers pointed out that the interface I was waiting for had been
 there for who-knows-how-long. With the help of DJ Delorie I extended the
 action handling of PCB to remember action contexts, which was another showstopper.
-After all obstacles removed, I allocated a 24 hour coding session where I
-finished the exporter functionality, added action binding, dialog box handling
+After all obstacles were removed, I allocated a 24 hour coding session where I
+finished the exporter functionality, added action binding, dialog box handling,
 and layout manipulation functions.
 
 During the summer of 2015 I merged pcb-gpmi into pcb-rnd and made it
-the default scirpting engine for pcb-rnd.
+the default scripting engine for pcb-rnd.
 
Index: trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.desc
===================================================================
--- trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.desc	(revision 8728)
+++ trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.desc	(revision 8729)
@@ -1 +1 @@
-Create and animate an anlog clock on a dedicated UI layer.
+Create and animate an analog clock on a dedicated UI layer.
Index: trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.name
===================================================================
--- trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.name	(revision 8728)
+++ trunk/doc/user/06_feature/gpmi/rosetta/90_clock/ID.name	(revision 8729)
@@ -1 +1 @@
-animated clock on an UI layer
+animated clock on a UI layer
Index: trunk/doc/user/06_feature/gpmi/rosetta/index.html
===================================================================
--- trunk/doc/user/06_feature/gpmi/rosetta/index.html	(revision 8728)
+++ trunk/doc/user/06_feature/gpmi/rosetta/index.html	(revision 8729)
@@ -51,6 +51,11 @@
  <td><a href="35_export_drill/index.html">drill list exporter</a>
  <td> awk lua tcl
  <td>Create a new exporter that prints a list of drills in x,y,dia table in CSV, TSV or text format
+<tr>
+ <td>90
+ <td><a href="90_clock/index.html">animated clock on a UI layer</a>
+ <td> awk
+ <td>Create and animate an analog clock on a dedicated UI layer.
 </table>
 
 
Index: trunk/doc/user/06_feature/gpmi/scripting_intro.html
===================================================================
--- trunk/doc/user/06_feature/gpmi/scripting_intro.html	(revision 8728)
+++ trunk/doc/user/06_feature/gpmi/scripting_intro.html	(revision 8729)
@@ -7,7 +7,7 @@
 <body>
 <H1> Scripting intro </H1>
 This document is an introduction to GPMI for pcb-rnd users. It focuses on
-scripting pcb-rnd and doesn't discusses GPMI deeper than the minimum necessary.
+scripting pcb-rnd and doesn't discuss GPMI deeper than the minimum necessary.
 GPMI is more generic than shown here.
 <p>
 The scope of the document is to describe the relations between pcb-rnd, 
@@ -39,7 +39,7 @@
 new export facility, just sits there, interacting with pcb-rnd (creating
 menus, actions, etc). Most script plugins do this.
 <p>
-When pcb-rnd executable is compiled, the core, the default GUI and exporter HIDs
+When the pcb-rnd executable is compiled, the core, the default GUI and exporter HIDs
 and buildins are compiled into the executable. Later on 
 <p>
 The <i>GPMI hid</i> is an <i>optional plugin</i> that, by compile-time choice
@@ -131,7 +131,7 @@
 which in turns loads other package(s) into the GPMI hid.
 <p>
 Packages are loaded only once and are globally accessible for multiple modules.
-<td><img src="gpmi_flow_load.png" alt="[same diagram as before, with pacakge load flow highlighted]"></table>
+<td><img src="gpmi_flow_load.png" alt="[same diagram as before, with package load flow highlighted]"></table>
 
 <H3> 2.3. Binding events, registering actions, creating menus </H3>
 <table border=0 width="100%"><tr><td valign=top>