Author: crossley
Date: Sat Oct 24 23:28:06 2009
New Revision: 829465
URL: http://svn.apache.org/viewvc?rev=829465&view=rev
Log:
Remove the word "existing" which made it sound like only useful for "legacy"
documents.
Some puntuation tweaks for readability.
Modified:
forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-b/customSchema.xml
Modified:
forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-b/customSchema.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-b/customSchema.xml?rev=829465&r1=829464&r2=829465&view=diff
==============================================================================
---
forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-b/customSchema.xml
(original)
+++
forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples-b/customSchema.xml
Sat Oct 24 23:28:06 2009
@@ -23,15 +23,15 @@
<body>
<p>
Forrest comes with a set of schemas for common documents, however, if you
- have existing documents that use a different schema you will want to tell
+ have documents that use a different schema you will need to tell
Forrest how to work with them. The best way of doing this is to
<a href="ext:forrest/buildPlugin">build a plugin</a> so that you can
- easily reuse the functionality on different projects. Plugins also allow
+ easily re-use the functionality on different projects. Plugins also allow
you to share this new functionality with other users, and to benefit from
their contributions to your work.
</p>
<p>
- If you don't want to build a plugin you can make Forrest process them
+ If you don't want to build a plugin, you can make Forrest process them
within your project sitemap (but this won't really save you any work
since
the process is almost the same). This sample site has a demonstration of
using a custom DTD. If you request <a href="site:custom-example"><a
