Author: twilliams
Date: Wed Aug 24 17:36:01 2005
New Revision: 239969
URL: http://svn.apache.org/viewcvs?rev=239969&view=rev
Log:
more spelling repair work.
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
URL:
http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml?rev=239969&r1=239968&r2=239969&view=diff
==============================================================================
---
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
(original)
+++
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
Wed Aug 24 17:36:01 2005
@@ -61,7 +61,7 @@
<a href="site:plugins/infrastructure">Plugin Infrastructure</a>
</li>
<li>verified with the Apache Forrest developer community that the
- requried functionality does not already exist</li>
+ required functionality does not already exist</li>
</ul>
</prerequisites>
@@ -104,7 +104,7 @@
<section id="seed">
<title>Seed a New Plugin</title>
<p>Regardless of the type of plugin you are building, the directory
- structure is almost identical, as are most of the requried
+ structure is almost identical, as are most of the required
configuration files. In this How-To we will assume that you are creating
a
plugin in the Forrest source tree. All plugins are developed in the
<code>forrest/plugins</code> directory.</p>
@@ -117,7 +117,7 @@
</source>
<p>The above ant target will ask you the name of the plugin and some
- additional information such as a breif description and will
+ additional information such as a brief description and will
build a minimal plugin directory structure and configuration. You will
need to customise these files to build your plugin.</p>
@@ -180,19 +180,19 @@
</section>
<section id="componentConfig">
- <title>Component Configuraiton</title>
+ <title>Component Configuration</title>
<p>If your plugin needs to provide additional Cocoon configuration
in the form of an <code>xconf</code>, or if some of the components
- you are using need a configuraiton file (such as a JTidy config)
+ you are using need a configuration file (such as a JTidy config)
you should place them in a <code>conf</code> directory in the root
of your plugin.</p>
</section>
<section id="hosted">
- <title>Style notes for plugins hosted at forrest.apapche.org</title>
+ <title>Style notes for plugins hosted at forrest.apache.org</title>
<p>
After seeding a new plugin, copy the configuration from an
- exisiting plugin (e.g.
org.apache.forrest.plugin.input.projectInfo).
+ existing plugin (e.g. org.apache.forrest.plugin.input.projectInfo).
Copy src/documentation/skinconf.xml and
src/documentation/content/xdocs/images/project-logo.gif
</p>
@@ -368,7 +368,7 @@
<title>Further Reading</title>
<ul>
- <li><a href="site:plugins/infrastructure">Plugin Infrastrucuture
Documentation</a> for Developers</li>
+ <li><a href="site:plugins/infrastructure">Plugin Infrastructure
Documentation</a> for Developers</li>
<li><a href="site:plugins">Plugins Documentation</a> for users</li>
</ul>
</section>
