forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r233983 - /forrest/trunk/site-author/content/xdocs/developer-guide.xml
Date Sat, 20 Aug 2005 01:32:21 GMT
Author: crossley
Date: Fri Aug 19 18:32:17 2005
New Revision: 233983

URL: http://svn.apache.org/viewcvs?rev=233983&view=rev
Log:
Fix XML validation error: v2.0 is <a> rather than <link>.

Modified:
    forrest/trunk/site-author/content/xdocs/developer-guide.xml

Modified: forrest/trunk/site-author/content/xdocs/developer-guide.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/developer-guide.xml?rev=233983&r1=233982&r2=233983&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/developer-guide.xml (original)
+++ forrest/trunk/site-author/content/xdocs/developer-guide.xml Fri Aug 19 18:32:17 2005
@@ -46,7 +46,7 @@
         read this guide and reduce the technical learning curve to developing in Forrest,
above all 
         we hope that you'll come away remembering that.  While the following document is
about Forrest
         committership, it is also useful in understanding what we mean by community.
-        <link href="http://forrest.apache.org/committed.html">http://forrest.apache.org/committed.html</link>
+        <a href="http://forrest.apache.org/committed.html">http://forrest.apache.org/committed.html</a>
       </p>
     </section>
     
@@ -77,7 +77,7 @@
         <title>Subversion</title>
         <p>Whether you use the svn command-line client or a fancy client,
           then you still need to make sure you know how to operate SVN properly.
-          <link href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com</link>
is a must.
+          <a href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com</a>
is a must.
         </p>
         
         <p>e.g. Make sure to do three things before creating the patch:</p>
@@ -109,8 +109,8 @@
         to debugging sitemaps.  While true errors will generally always print in the log
files, 
         while you're debugging something you may find it useful to also customize log output
in
         the "logkit.xconf" in webapp/WEB-INF.  For more information, 
-        see: <link href="http://forrest.apache.org/docs_0_70/faq.html#logs">
-        http://forrest.apache.org/docs_0_70/faq.html#logs</link>
+        see: <a href="http://forrest.apache.org/docs_0_70/faq.html#logs">
+        http://forrest.apache.org/docs_0_70/faq.html#logs</a>
       </p>
       <p><strong>Java Code.</strong> Since there's really no way to "trace"
the java code through
         the pipeline process, you may find <code>getLogger().debug()</code> useful
for understanding 
@@ -160,7 +160,7 @@
       <section id="pipelines">
         <title>Pipelines</title>
         <p>There is an absolutely wonderful introduction to Cocoon Pipelines for Forrest
hidden in this 
-          <link href="http://forrest.apache.org/docs_0_80/howto/howto-custom-html-source.html">How-To</link>.
 
+          <a href="http://forrest.apache.org/docs_0_80/howto/howto-custom-html-source.html">How-To</a>.
 
           For a non-Cocooner trying to work with Forrest, it is a *must-read*.
         </p>
       </section>



Mime
View raw message