crossley 2003/10/06 04:48:33
Modified: src/documentation/xdocs/userdocs/components/transformers
xinclude-transformer.xml cinclude-transformer.xml
Log:
Fix some speling errors.
Minor text tweaks.
Revision Changes Path
1.2 +2 -2 cocoon-2.1/src/documentation/xdocs/userdocs/components/transformers/xinclude-transformer.xml
Index: xinclude-transformer.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/userdocs/components/transformers/xinclude-transformer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xinclude-transformer.xml 2 Sep 2003 12:03:16 -0000 1.1
+++ xinclude-transformer.xml 6 Oct 2003 11:48:32 -0000 1.2
@@ -49,7 +49,7 @@
<p>
A simple example using xinclude might help to use this transfomer
- effectivly:
+ effectively:
</p>
<p>
Add the XIncludetransfomer to the components in your sitemap.xmap
@@ -80,7 +80,7 @@
<p>
In this example pipeline it assumed that simple-xinc.xml contains
the include element. As well as defining the include element,
- it defines the namespache URI "http://www.w3.org/2001/XInclude".
+ it defines the namespace URI "http://www.w3.org/2001/XInclude".
This helps the XIncludeTransformer to find the include element to
get replaced by the included content.
The simple-xinc.xml may look like this:
1.2 +7 -7 cocoon-2.1/src/documentation/xdocs/userdocs/components/transformers/cinclude-transformer.xml
Index: cinclude-transformer.xml
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/userdocs/components/transformers/cinclude-transformer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cinclude-transformer.xml 2 Sep 2003 12:03:16 -0000 1.1
+++ cinclude-transformer.xml 6 Oct 2003 11:48:32 -0000 1.2
@@ -15,9 +15,9 @@
<body>
<s1 title="CInclude Transformer">
<p>This transformer includes XML in the current stream and acts therefore
- as a kind of (dynamic) content aggregation. Two forms, one verbose
- and flexible approach, and a simple approach are supported by the
- transformer. We will first discuss the simple approach and
+ as a kind of (dynamic) content aggregation. Two forms are supported by
+ the transformer: one verbose and flexible approach, and a simple approach.
+ We will first discuss the simple approach and
the more flexible is mentioned in the next chapter. In addition
the cinclude transformer provides a caching mechanism (for the
simple include form).</p>
@@ -36,7 +36,7 @@
<li>Cacheable: no.</li>
</ul>
<p>
- A simple example might help to use the CIncludeTransfomer effectivly:
+ A simple example might help to use the CIncludeTransfomer effectively:
</p>
<p>
Add the CIncludeTransformer to the components in your sitemap.xmap
@@ -66,7 +66,7 @@
<p>
In this example pipeline it assumed that simple-cinc.xml contains
the include element. Beside defining the include element
- it defines the namespache URI "http://apache.org/cocoon/include/1.0".
+ it defines the namespace URI "http://apache.org/cocoon/include/1.0".
This helps the CIncludeTransformer to find the tag to get replaced by
the xml content referenced via the src attribute.
The simple-cinc.xml may look like this:
@@ -201,7 +201,7 @@
element, so only parts are cached and others are not.
</p>
<p>
- A simple example might help to use the caching effectivly:
+ A simple example might help to use the caching effectively:
</p>
<p>
First define your pipeline to use the CIncludeTransformer with
@@ -223,7 +223,7 @@
<p>
In this example-pipeline it is assumed that simple-cinc.xml contains
the <code>cached-include</code> element. Beside defining the element
- it uses the namespache URI "http://apache.org/cocoon/include/1.0".
+ it uses the namespace URI "http://apache.org/cocoon/include/1.0".
This helps the transformer to find the tag to get replaced by
the xml content referenced via the src attribute.
The simple-cinc.xml may look like this:
|