You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by br...@apache.org on 2004/07/19 02:25:37 UTC

svn commit: rev 23041 - forrest/trunk/src/documentation/content/xdocs/howto

Author: brondsem
Date: Sun Jul 18 17:25:36 2004
New Revision: 23041

Modified:
   forrest/trunk/src/documentation/content/xdocs/howto/howto-howto.xml
Log:
the How-To DTD is not under development

Modified: forrest/trunk/src/documentation/content/xdocs/howto/howto-howto.xml
==============================================================================
--- forrest/trunk/src/documentation/content/xdocs/howto/howto-howto.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/howto/howto-howto.xml	Sun Jul 18 17:25:36 2004
@@ -20,8 +20,6 @@
  <header>
   <title>How to write a How-To</title>
   <version>0.3</version>
-  <notice>This document is a sample to test the DTD structure and to
-  provide a template for devloping other How-To documents.</notice>
   <abstract>This How-To describes the steps necessary to write a How-To
    document. Writing documentation is a valuable way to give back to the community.
   </abstract>
@@ -48,7 +46,7 @@
 <ul>
 <li>A unique How-To topic, related to using Forrest, which fulfills a specific need. Check out existing How-Tos to find a niche for your work. Consider posting your idea for the How-To to user mailing list, to make sure another author's draft is not already in process.</li>
 <li>A sufficient ability in English to write the FAQ. However, we would rather that you just make a start, as the community can help to fine-tune the document.</li>
-<li>Currently, the Forrest project is still working out the exact details for a How-To dtd and template. For now, just edit the most recent version of any existing How-To, filling in your own content as necessary. Make sure you run
+<li>An understanding of the How-To DTD.  You can copy this How-To and modify with your own content as necessary. Make sure you run
 '<code>forrest validate-xdocs</code>' before contributing your document.</li>
 </ul>
 <note>See the