svn commit: r160996 - forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml

[cr...@apache.org]

Author: crossley
Date: Mon Apr 11 18:10:46 2005
New Revision: 160996

URL: http://svn.apache.org/viewcvs?view=rev&rev=160996
Log:
Add a note to ensure robust sitemap matches.
Fix some typos.

Modified:
    forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml

Modified: forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml?view=diff&r1=160995&r2=160996
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs/howto/howto-buildPlugin.xml Mon Apr 11 18:10:46 2005
@@ -122,7 +122,7 @@
       
       <note>Although you can name your project anything you like we do have 
       some <a href="site:documentation/developers/pluginInfrastructure">naming 
-      coventions</a> that we recommend you follow. Plugins intended to be
+      conventions</a> that we recommend you follow. Plugins intended to be
       held at forrest.apache.org must follow the naming convention.</note> 
       
       <note>If you plan on building your plugin elsewhere you can copy the
@@ -248,7 +248,7 @@
       functionality, you can use that site for testing the plugin. However, you
       must first deploy in your local install of Forrest. Each plugin contains
       a buildfile that includes a <code>test</code> target. This target, by
-      default, builds the documtantion for your plugin.</p>
+      default, builds the documentation for your plugin.</p>
       
       <p class="instruction">Run the command <code>ant test</code> in
       the plugins directory.</p>
@@ -267,6 +267,9 @@
       In addition, we recommend that you use the samples in your documentation 
       for your tests, this way you are documenting your plugin at the same time 
       as writing your tests.</p>
+
+      <p>Ensure that your sitemaps are robust and handle matches for files
+      in sub-directories, as well as those at the root level.</p>
     </section>
     
     <section id="release">