Update Java-Language.xml - title case

en-US/Java-Language.xml

@@ -2,7 +2,7 @@
 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
 ]>
 <section id="sect-Defensive_Coding-Java-Language">
-  <title>The core language</title>
+  <title>The Core Language</title>
   <para>
     Implementations of the Java programming language provide strong
     memory safety, even in the presence of data races in concurrent
@@ -12,7 +12,7 @@
   </para>
 
   <section id="sect-Defensive_Coding-Java-Language-ReadArray">
-    <title>Increasing robustness when reading arrays</title>
+    <title>Increasing Robustness when Reading Arrays</title>
     <para>
       External data formats often include arrays, and the data is
       stored as an integer indicating the number of array elements,
@@ -40,7 +40,7 @@
   </section>
 
   <section id="sect-Defensive_Coding-Java-Language-Resources">
-    <title>Resource management</title>
+    <title>Resource Management</title>
     <para>
       Unlike C++, Java does not offer destructors which can deallocate
       resources in a predictable fashion.  All resource management has
@@ -160,7 +160,7 @@
   </section>
   
   <section id="sect-Defensive_Coding-Java-Language-Exceptions">
-    <title>Recovering from exceptions and errors</title>
+    <title>Recovering from Exceptions and Errors</title>
     <para>
       Java exceptions come in three kinds, all ultimately deriving
       from <literal>java.lang.Throwable</literal>:
@@ -220,7 +220,7 @@
     </para>
 
     <section id="sect-Defensive_Coding-Java-Language-Exceptions-Errors">
-      <title>The difficulty of catching errors</title>
+      <title>The Difficulty of Catching Errors</title>
       <para>
 	Errors (that is, exceptions which do not (indirectly) derive
 	from <literal>java.lang.Exception</literal>), have the