svn commit: rev 55310 - forrest/trunk/src/documentation/content/xdocs/docs

[cr...@apache.org]

Author: crossley
Date: Thu Oct 21 23:23:49 2004
New Revision: 55310

Modified:
   forrest/trunk/src/documentation/content/xdocs/docs/plugins.xml
Log:
Fix some typos and add some punctuation.


Modified: forrest/trunk/src/documentation/content/xdocs/docs/plugins.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/docs/plugins.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/docs/plugins.xml	Thu Oct 21 23:23:49 2004
@@ -59,20 +59,20 @@
       extend the functionality of Forrest. They will typically consist of a 
       sitemap, zero or more stylesheets and zero or more schema's.</p>
 
-      <p>The plugins sitemap is mounted by Forrests sitemap after the project 
+      <p>The plugins sitemap is mounted by Forrest's sitemap after the project 
       specific sitemap but before the Forrest default matchers. This allows 
       individual projects to override/extend functionality provided in either 
       a plugin or Forrest whilst plugins are only able to override/extend the 
       default Forrest behaviour.</p>
 
       <p>Forrest is easily extensible through the existing sitemap.xmap files, 
-      however the more features we add the more complex the sitemap becomes. It 
+      however the more features we add, the more complex the sitemap becomes. It 
       is already quite difficult to understand the default sitemap.xmap files, 
       and this will only get worse as new features find their way into the 
       core.</p>
 
       <p>By adopting a plugin model we can keep the core of Forrest tightly 
-      focused on the basic functionality whilst still facilitating extensions 
+      focused on the basic functionality, whilst still facilitating extensions 
       to suit individual projects needs.</p>
     
       <section>
@@ -90,7 +90,7 @@
         <p>An IMS Manifest file describes the structure of a site. It is also 
         possible to define a set of rules for extracting tab information from 
         such a file. Consequently, it is possible to use an IMSManifest file to 
-        create Forrests site.xml and tabs.xml files. The advantage would be that
+        create Forrest's site.xml and tabs.xml files. The advantage would be that
         we can then use SCORM compliant content objects within Forrest.</p>
   
         <p>Unfortunately, IMS Manifests are much more complex than site.xml and 
@@ -180,7 +180,7 @@
     <title>How does Installation work?</title>
     <p>When Forrest installs a plugin it downloads a zip of the plugin code and 
     extracts it into the <code>plugins</code> directory of Forrest and an entry is made 
-    in <code>src/plugins/stitemap.xmap</code>. For example, installing the 
+    in <code>src/plugins/sitemap.xmap</code>. For example, installing the 
     IMSManifest plugin described above will result in the following entry 
     being added to the plugin sitemap:</p>
 
@@ -195,9 +195,9 @@
 </map:select>
   ]]></source>
   
-      <p>Installed plugins are managed by the file 
-      FORREST_INSTALL_DIR/plugings/sitemap.xmap. This file is mounted by main 
-      Forrest sitemap with the following code:</p>
+      <p>Installed plugins are managed by the
+      FORREST_INSTALL_DIR/plugins/sitemap.xmap file. This file is mounted
+      by the main Forrest sitemap with the following code:</p>
   
   <source><![CDATA[
         <map:pipeline internal-only="false">