You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by wg...@apache.org on 2006/03/10 19:57:28 UTC
svn commit: r384892 - in /jakarta/velocity/engine/trunk/xdocs: build.xml
changes14.xml docs/developer-guide.xml docs/user-guide.xml overview.xml
Author: wglass
Date: Fri Mar 10 10:57:26 2006
New Revision: 384892
URL: http://svn.apache.org/viewcvs?rev=384892&view=rev
Log:
changed it's to its when appropriate. VELOCITY-431. Thanks to Carl Manaster for pointing this out.
Modified:
jakarta/velocity/engine/trunk/xdocs/build.xml
jakarta/velocity/engine/trunk/xdocs/changes14.xml
jakarta/velocity/engine/trunk/xdocs/docs/developer-guide.xml
jakarta/velocity/engine/trunk/xdocs/docs/user-guide.xml
jakarta/velocity/engine/trunk/xdocs/overview.xml
Modified: jakarta/velocity/engine/trunk/xdocs/build.xml
URL: http://svn.apache.org/viewcvs/jakarta/velocity/engine/trunk/xdocs/build.xml?rev=384892&r1=384891&r2=384892&view=diff
==============================================================================
--- jakarta/velocity/engine/trunk/xdocs/build.xml (original)
+++ jakarta/velocity/engine/trunk/xdocs/build.xml Fri Mar 10 10:57:26 2006
@@ -178,7 +178,7 @@
<code>docs/api</code> directory
</li>
<li>
- <b><code>test</code></b> (after jar) will test Velocity against it's testbed
+ <b><code>test</code></b> (after jar) will test Velocity against its testbed
suite of test routines
</li>
<li>
Modified: jakarta/velocity/engine/trunk/xdocs/changes14.xml
URL: http://svn.apache.org/viewcvs/jakarta/velocity/engine/trunk/xdocs/changes14.xml?rev=384892&r1=384891&r2=384892&view=diff
==============================================================================
--- jakarta/velocity/engine/trunk/xdocs/changes14.xml (original)
+++ jakarta/velocity/engine/trunk/xdocs/changes14.xml Fri Mar 10 10:57:26 2006
@@ -119,7 +119,7 @@
<subsection name="1.3.1-rc2" href="1.3.1-rc2">
<p>
This section desscribes changes to the VEL_1_3_BRANCH after
-the 1.3.1-rc2 release. It was released as 1.3.1 on it's own branch,
+the 1.3.1-rc2 release. It was released as 1.3.1 on its own branch,
VEL_1_3_1_BRANCH on March 31, 2003.
</p>
</subsection>
Modified: jakarta/velocity/engine/trunk/xdocs/docs/developer-guide.xml
URL: http://svn.apache.org/viewcvs/jakarta/velocity/engine/trunk/xdocs/docs/developer-guide.xml?rev=384892&r1=384891&r2=384892&view=diff
==============================================================================
--- jakarta/velocity/engine/trunk/xdocs/docs/developer-guide.xml (original)
+++ jakarta/velocity/engine/trunk/xdocs/docs/developer-guide.xml Fri Mar 10 10:57:26 2006
@@ -380,7 +380,7 @@
This is very convenient as it
allows localized configuration and sharing of resources. For example, this
is a very appropriate model for use in a Servlet 2.2+ compliant web application
- as each web application can have it's own instance of Velocity, allowing
+ as each web application can have its own instance of Velocity, allowing
that web application's servlet to share resources like templates, a logger, etc.
The singleton is accessable via the <code>org.apache.velocity.app.Velocity</code>
class, and and example of use :
@@ -1400,9 +1400,9 @@
<p>
There is a set of default values contained in Velocity's jar, found in
/src/java/org/apache/velocity/runtime/defaults/velocity.defaults, that
-Velocity uses as it's configuration baseline.
+Velocity uses as its configuration baseline.
This ensures that Velocity will always have a 'correct' value
-for it's configuration keys at startup, although it may not be what you want.
+for its configuration keys at startup, although it may not be what you want.
</p>
<p>
@@ -1422,7 +1422,7 @@
<p>
Below are listed the configuration keys that control Velocity's behavior.
-Organized by category, each key is listed with it's current default value
+Organized by category, each key is listed with its current default value
to the right of the '=' sign.
</p>
@@ -1791,7 +1791,7 @@
<li>
<b>Existing Log4j Logger/Category</b><br/>
-Starting with version 1.3, Velocity will log it's output to an existing
+Starting with version 1.3, Velocity will log its output to an existing
Log4j Category setup elsewhere in the application. With version 1.5, we have
switched to using the Logger class, as the Category class is now deprecated
in Log4j. To use this feature you must
@@ -2032,7 +2032,7 @@
<ul>
<li>
- <b>FileResourceLoader :</b> This loader gets resources from the filesystem. It's
+ <b>FileResourceLoader :</b> This loader gets resources from the filesystem. Its
configuration properties include :
<ul>
<li>
Modified: jakarta/velocity/engine/trunk/xdocs/docs/user-guide.xml
URL: http://svn.apache.org/viewcvs/jakarta/velocity/engine/trunk/xdocs/docs/user-guide.xml?rev=384892&r1=384891&r2=384892&view=diff
==============================================================================
--- jakarta/velocity/engine/trunk/xdocs/docs/user-guide.xml (original)
+++ jakarta/velocity/engine/trunk/xdocs/docs/user-guide.xml Fri Mar 10 10:57:26 2006
@@ -1829,7 +1829,7 @@
<p>
In fact, because all script elements
- are escaped, <em>$jazz</em> is never evaluated for it's boolean value.
+ are escaped, <em>$jazz</em> is never evaluated for its boolean value.
Suppose
backslashes precede script elements that are legitimately escaped:
</p>
@@ -2125,7 +2125,7 @@
<p>
<i>However...</i>, there are things you can do. One easy solution is to take
-advantage of the fact that 'doublequote' (") renders it's contents. So you
+advantage of the fact that 'doublequote' (") renders its contents. So you
could do something like
</p>
Modified: jakarta/velocity/engine/trunk/xdocs/overview.xml
URL: http://svn.apache.org/viewcvs/jakarta/velocity/engine/trunk/xdocs/overview.xml?rev=384892&r1=384891&r2=384892&view=diff
==============================================================================
--- jakarta/velocity/engine/trunk/xdocs/overview.xml (original)
+++ jakarta/velocity/engine/trunk/xdocs/overview.xml Fri Mar 10 10:57:26 2006
@@ -81,7 +81,7 @@
<section name="Extending Velocity's Capability" href="ExtendingVelocity'sCapability">
<p>While Velocity is generally useful within an application as is, there are a number of ways
- it's capabilities can be extended.
+ its capabilities can be extended.
</p>
<ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org