Author: niallp
Date: Sun Mar 14 02:06:30 2010
New Revision: 922721
URL: http://svn.apache.org/viewvc?rev=922721&view=rev
Log:
Minor language tweaks
Modified:
commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
Modified: commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
URL:
http://svn.apache.org/viewvc/commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml?rev=922721&r1=922720&r2=922721&view=diff
==============================================================================
--- commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml (original)
+++ commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml Sun Mar 14
02:06:30 2010
@@ -232,7 +232,7 @@
Using the <i>target</i> option ensures that the <code>.class</code>
file format is compatible with
the required Java version - but it does not prevent/catch the use of
methods/classes which were
introduced in later Java versions (because the build will use the
current Java libraries by default).
- The only way to ensure that the coded does not accidentally use
classes/methods from a different (later)
+ The only way to ensure that components dont accidentally use
classes/methods from a later
version of Java is to compile and test using actual Java versions.
</p>
<p>
@@ -280,7 +280,7 @@
<profile>
<id>java-1.5</id>
<properties>
- <JAVA_1_5_HOME>C:\j\jdk1.5.0_01</JAVA_1_5_HOME>
+ <JAVA_1_5_HOME>C:\j\jdk1.5.0_22</JAVA_1_5_HOME>
</properties>
</profile>
<profile>
@@ -293,8 +293,8 @@
</settings>
]]></source>
<p>
- (Since the values only depend on the location of the Java
installations on your local machine,
- and will probably not change frequently, using the
<code>settings.xml</code> file is generally
+ (Since the values are the locations of the Java installations on
your local machine,
+ they are unlikely to change frequently and using the
<code>settings.xml</code> file will be
the most convenient).
</p>
<p>
