svn commit: r345203 - /forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml

[cr...@apache.org]

Author: crossley
Date: Wed Nov 16 23:34:09 2005
New Revision: 345203

URL: http://svn.apache.org/viewcvs?rev=345203&view=rev
Log:
Remove a confusing shortcut.

Modified:
    forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml?rev=345203&r1=345202&r2=345203&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-install.xml Wed Nov 16 23:34:09 2005
@@ -48,19 +48,20 @@
       <li>Need the SVN trunk version of Forrest for using the "dispatcher" because it is in an early stage.</li>
       <li>Read <a href="site:v0.80//howto/buildPlugin">How to Build a Plugin</a>
         especially the section about using Forrest's own Ant.</li>
-      <li>Installing a mozilla browser and the forrestbar helps a lot in developing.</li>
+      <li>Installing a mozilla browser and the
+        <a href="site:tools/forrestbar">Forrestbar</a> helps a lot in developing.</li>
     </ul>
   </prerequisites>
 
   <steps title="Steps">
     <p>
-      The process of setting up the plugin should be easy. Still it has to many stages and it
+      The process of setting up the plugin should be easy. Still it has too many stages and it
        will become easier in the future.
     </p>
     <section id="localBuild">
-      <title>Build the internal.structurer and the output.themes plugins</title>
+      <title>Build the internal.structurer and the output.themer plugins</title>
       <p>
-        The first step is to build and deploy the internal.structurer and the output.themes plugins. Change to a terminal window of your choice
+        The first step is to build and deploy the internal.structurer and the output.themer plugins. Change to a terminal window of your choice
         and go (cd) to the trunk version of forrest {forrest-trunk}. Then do an SVN update.
       </p>
       <source>
@@ -76,7 +77,7 @@
 ant local-deploy
       </source>
       <p>
-        Alternatively, run the script <code>etc/structurer.sh</code> *after* you did an update.
+        Alternatively, run the script <code>etc/structurer.sh</code> *after* you did an svn update.
       </p>
     </section>
     <section id="newSeed">
@@ -91,17 +92,14 @@
         be realesed to the stable plugins. So make regular updates of your forrest-trunk to keep track.
      </note>
      <warning>
-      The way we develope contracts will/may change with introduction of java based processing rather then xsl. Please keep this in mind
+      The way we develop contracts will/may change with introduction of java-based processing 
+      (for certain parts) rather then xsl. Please keep this in mind
         and help updating the documentation by sending patches. TIA. ;-)
      </warning>
       <source>cd ~/src/ 
 mkdir v2 
 cd v2/ 
 forrest seed-v2 </source>
-<note>Another way would be using the template directly in forrest. That enables you to send patches directly agains the seed-v2. ;-)
-  As well worth if you just want to see current developing state and do not want to play with the dispatcher yet.</note>
-      <source>cd {forrest-trunk}/main/template-sites/v2/
-forrest run</source>
     </section>
     <section id="forrestProperties">
       <title>Modifying forrest.properties (HEADSUP: if you are *not* using the seed-v2 target nor v2/)</title>