svn commit: r1517182 - /maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties

[mi...@apache.org]

Author: michaelo
Date: Sat Aug 24 18:49:34 2013
New Revision: 1517182

URL: http://svn.apache.org/r1517182
Log:
Use proper title case for SCM titles as in all other titles.

Modified:
    maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties

Modified: maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties?rev=1517182&r1=1517181&r2=1517182&view=diff
==============================================================================
--- maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties (original)
+++ maven/plugins/trunk/maven-project-info-reports-plugin/src/main/resources/project-info-report.properties Sat Aug 24 18:49:34 2013
@@ -148,17 +148,17 @@ report.mailing-lists.title              
 report.scm.accessbehindfirewall.cvs.intro                          = For those developers who are stuck behind a corporate firewall, {CVSGrab, http://cvsgrab.sourceforge.net/} can use the viewcvs web interface to checkout the source code.
 report.scm.accessbehindfirewall.general.intro                      = Refer to the documentation of the SCM used for more information about access behind a firewall.
 report.scm.accessbehindfirewall.svn.intro                          = For those users who are stuck behind a corporate firewall which is blocking HTTP access to the Subversion repository, you can try to access it via the developer connection:
-report.scm.accessbehindfirewall.title                              = Access from behind a firewall
+report.scm.accessbehindfirewall.title                              = Access from Behind a Firewall
 report.scm.accessthroughtproxy.svn.intro1                          = The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The file's location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)
 report.scm.accessthroughtproxy.svn.intro2                          = There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
 report.scm.accessthroughtproxy.svn.intro3                          = Example: Edit the 'servers' file and add something like:
-report.scm.accessthroughtproxy.title                               = Access through a proxy
+report.scm.accessthroughtproxy.title                               = Access Through a Proxy
 report.scm.anonymousaccess.cvs.intro                               = This project's CVS repository can be checked out through anonymous CVS with the following instruction set. When prompted for a password for anonymous, simply press the Enter key.
 report.scm.anonymousaccess.general.intro                           = Refer to the documentation of the SCM used for more information about anonymously check out. The connection url is:
 report.scm.anonymousaccess.git.intro                               = The source can be checked out anonymously from GIT with this command (See {http://git-scm.com/docs/git-clone,http://git-scm.com/docs/git-clone}):
 report.scm.anonymousaccess.hg.intro                                = The source can be checked out anonymously from Mercurial with this command (See {http://www.selenic.com/mercurial/hg.1.html#clone,http://www.selenic.com/mercurial/hg.1.html#clone}):
 report.scm.anonymousaccess.svn.intro                               = The source can be checked out anonymously from SVN with this command:
-report.scm.anonymousaccess.title                                   = Anonymous access
+report.scm.anonymousaccess.title                                   = Anonymous Access
 report.scm.clearcase.intro                                         = This project uses {ClearCase, http://www-306.ibm.com/software/awdtools/clearcase/} to manage its source code. Informations on ClearCase use can be found at {http://www.redbooks.ibm.com/redbooks/pdfs/sg246399.pdf, http://www.redbooks.ibm.com/redbooks/pdfs/sg246399.pdf}.
 report.scm.cvs.intro                                               = This project uses {Concurrent Versions System, http://www.cvshome.org/} to manage its source code. Instructions on CVS use can be found at {http://cvsbook.red-bean.com/, http://cvsbook.red-bean.com/}.
 report.scm.description                                             = This is a link to the online source repository that can be viewed via a web browser.
@@ -174,7 +174,7 @@ report.scm.devaccess.svn.intro1.other   
 report.scm.devaccess.svn.intro1.svn                                = Committers must checkout the Subversion repository via SVN.
 report.scm.devaccess.svn.intro1.svnssh                             = Committers must checkout the Subversion repository via SVN+SSH.
 report.scm.devaccess.svn.intro2                                    = To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)
-report.scm.devaccess.title                                         = Developer access
+report.scm.devaccess.title                                         = Developer Access
 report.scm.general.intro                                           = This project uses a Source Content Management System to manage its source code.
 report.scm.name                                                    = Source Repository
 report.scm.noscm                                                   = No source configuration management system is defined. Please check back at a later date.