Fix component name references

src/main/java/org/apache/commons/logging/LogFactory.java

@@ -575,7 +575,7 @@ public abstract class LogFactory {
      * </p>
      * <p>
      * Even when using an AccessController, however, this method can still
-     * throw SecurityException. Commons-logging basically relies on the
+     * throw SecurityException. Commons Logging basically relies on the
      * ability to access classloaders. A policy that forbids all
      * classloader access will also prevent commons-logging from working:
      * currently this method will throw an exception preventing the entire app

src/main/java/org/apache/commons/logging/package-info.java

@@ -147,7 +147,7 @@
  * <h3>Configuring the Underlying Logging System</h3>
  * <p>The basic principle is that the user is totally responsible for the
  * configuration of the underlying logging system.
- * Commons-logging should not change the existing configuration.</p>
+ * Commons Logging should not change the existing configuration.</p>
  * <p>Each individual <a href="Log.html">Log</a> implementation may
  * support its own configuration properties.  These will be documented in the
  * class descriptions for the corresponding implementation class.</p>

src/site/xdoc/index.xml

@@ -36,7 +36,7 @@ of a particular one on the overall application that the library is a part of.</p
 
 <p>The Logging package is an ultra-thin bridge between different logging
 implementations.  A library that uses the commons-logging API can be used with
-any logging implementation at runtime. Commons-logging comes with support for a
+any logging implementation at runtime. Commons Logging comes with support for a
 number of popular logging implementations, and writing adapters for others is a
 reasonably simple task.</p>