forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r536462 - /forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml
Date Wed, 09 May 2007 08:55:59 GMT
Author: crossley
Date: Wed May  9 01:55:58 2007
New Revision: 536462

URL: http://svn.apache.org/viewvc?view=rev&rev=536462
Log:
Fix a linking error.

Modified:
    forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml?view=diff&rev=536462&r1=536461&r2=536462
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/glossary.xml Wed May  9 01:55:58 2007
@@ -226,7 +226,7 @@
           <link href="#sitemap">sitemaps</link> in main/webapp/*.xmap files.
           The main sitemap mounts a plugin sitemap from each declared plugin.
           For example an input plugin might handle projectInfo source documents
-          to convert them into the <link href="internal-xml">internal document format</link>
+          to convert them into the <link href="#internal-xml">internal document format</link>
           for further processing, while an output plugin would concern itself
           with generating output PDF documents. Nice <link href="#SoC">Separation of
Concerns</link>.
           If no plugin is found to handle a certain document type, then processing falls
back to the core.



Mime
View raw message