nicolaken 2002/11/18 05:36:25
Modified: src/xdocs guide-example-configuration.xml
Log:
Fixed XML so that there is no text out of <p> tags.
Revision Changes Path
1.6 +3 -3 jakarta-avalon-phoenix/src/xdocs/guide-example-configuration.xml
Index: guide-example-configuration.xml
===================================================================
RCS file:
/home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-example-configuration.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- guide-example-configuration.xml 15 Sep 2002 02:07:32 -0000 1.5
+++ guide-example-configuration.xml 18 Nov 2002 13:36:25 -0000 1.6
@@ -11,7 +11,7 @@
<p>This page contains a real production example of a block
assembly and block .xinfo description based an extract from
a B2B Enterprise Integration and Collaboration Platform developed by
- <a href="http://www.osm.net";>OSM</a></p>.
+ <a href="http://www.osm.net";>OSM</a>.</p>
<p>This example was originally a Mailing List response to a
some user questions!</p>
<p>The orginal post was written by Stephen McConnell from OSM.</p>
@@ -128,8 +128,8 @@
E.g. the provide element references a block by its name - and declares that
the
named block will serve as the provider of the service. The role attribute
matches
the role element in the <code>.xinfo</code> dependency declaration.</p>
- The name attribute also serves a the key to lookup a configuration element in
- the application configuration.xml file.
+ <p>The name attribute also serves a the key to lookup a configuration element
in
+ the application configuration.xml file.</p>
<source><![CDATA[
<?xml version="1.0"?>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
