svn commit: r180202 - in /forrest/trunk: main/fresh-site/src/documentation/content/xdocs/samples/linking.xml site-author/content/xdocs/docs/upgrading_07.xml

[cr...@apache.org]

Author: crossley
Date: Sun Jun  5 20:09:00 2005
New Revision: 180202

URL: http://svn.apache.org/viewcvs?rev=180202&view=rev
Log:
Minor punctuation changes.

Modified:
    forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples/linking.xml
    forrest/trunk/site-author/content/xdocs/docs/upgrading_07.xml

Modified: forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples/linking.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples/linking.xml?rev=180202&r1=180201&r2=180202&view=diff
==============================================================================
--- forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples/linking.xml (original)
+++ forrest/trunk/main/fresh-site/src/documentation/content/xdocs/samples/linking.xml Sun Jun  5 20:09:00 2005
@@ -64,7 +64,7 @@
         In versions prior to 0.7 raw un-processed content was stored in
         the "<code>content/</code>" directory. In 0.7 onwards, raw
         un-processed data is stored alongside the xdocs. In addition,
-        in 0.6 and earlier HTML documents could be stored in the xdocs
+        in 0.6 and earlier, HTML documents could be stored in the xdocs
         directory and served without processing. If you 
         you wish to emulate the behaviour of 0.6 and earlier see the 
         next section.
@@ -97,7 +97,7 @@
       the file <code>content/xdocs/hello.sxw</code> can be used to produce a 
       skinned version of the document at with the name <code>hello.html</code>.
       Similarly, you can use <a href="/docs/plugins/index.html">Forrest Output 
-      Plugins</a> to #create different output formats such as PDF, in this 
+      Plugins</a> to create different output formats such as PDF, in this 
       case <code>content/xdocs/hello.sxw</code> can produce 
       <code>hello.pdf</code>.</p>
       
@@ -105,7 +105,7 @@
       can still retrieve the raw un-processed version with, for example, 
       <code>hello.sxw</code>. If you want to prevent the user retrieving the 
       un-processed version you will have to create matchers that intercept
-      these requests within your projects sitemap.</p>
+      these requests within your project sitemap.</p>
       </section>
   
     </section>
@@ -149,19 +149,19 @@
       <source><![CDATA[<a href="../hello.pdf">]]><a href="../hello.pdf">../hello.pdf</a><![CDATA[</a>]]></source>
       
       <section>
-        <title>Emulating the Behaviour of pre 0.7 Versions of Forrest</title>
+        <title>Emulating the behaviour of pre 0.7 versions of Forrest</title>
         
-        <p>In versions prior to 0.7 raw un-processed content was stored in
+        <p>Prior to 0.7 version, the raw un-processed content was stored in
         the "<code>content/</code>" directory. In 0.7 onwards, raw
         un-processed data is stored alongside the xdocs. In addition
-        in 0.6 and earlier HTML files could be stored in the xdocs 
+        with 0.6 and earlier, HTML files could be stored in the xdocs 
         directory and they would be served without further processing.
         As described above, this is not the case in 0.7 where HTML files
         are, by default, skinned by Forrest.</p>
         
         <p>If you 
         you wish to emulate the behaviour of 0.6 and earlier then you
-        must add the following to your projects sitemap.</p>
+        must add the following to your project sitemap.</p>
         
         <source>
 &lt;map:match pattern="**.html"&gt;
@@ -200,7 +200,7 @@
         content as raw un-processed content, whilst still serving other content
         as skinned documents. For example, the following snippet would allow
         you to serve the content of an old, deprecated site without processing
-        from Forrest whilst still allowing all other content to be processed 
+        from Forrest, whilst still allowing all other content to be processed 
         by Forrest in the normal way:</p>
         
         <source>

Modified: forrest/trunk/site-author/content/xdocs/docs/upgrading_07.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs/upgrading_07.xml?rev=180202&r1=180201&r2=180202&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs/upgrading_07.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs/upgrading_07.xml Sun Jun  5 20:09:00 2005
@@ -139,19 +139,19 @@
         Any linked file with .html extension was not processed and not
         adorned with Forrest skin and navigation menus.
       </p>
-      <p>It was also possible to place HTML content in the XDocs directory
-      where it would be copied across if it were linked from the main
+      <p>It was also possible to place HTML content in the xdocs directory
+      where it would be copied across if it was linked from the main
       content.</p>
       <p>
         In 0.7 version, any file that is linked to, needs to be placed in
         the content/xdocs/ directory structure.
         Any linked file with .html extension is now processed and is
         adorned with Forrest skin and navigation menus.
-      </p>        
+      </p>
       <p>If you 
         you wish to emulate the behaviour of 0.6 and earlier then you
-        must add the following to your projects sitemap.</p>
-        
+        must add the following to your project sitemap.</p>
+
         <source>
 &lt;map:match pattern="**.html"&gt;
  &lt;map:select type="exists"&gt;
@@ -174,7 +174,7 @@
  &lt;/map:select&gt;
 &lt;/map:match&gt;
         </source>
-        
+
       <p>
         If you need to include files that are not linked to,
         then place them in the src/documentation/content/ directories