[geany/geany] 54ed21: Use capitilized version of Git inside documentation

[Frank Lanitz]

Branch:      refs/heads/master
Author:      Frank Lanitz <frank at frank.uvena.de>
Committer:   Frank Lanitz <frank at frank.uvena.de>
Date:        Thu, 31 May 2012 20:30:44
Commit:      54ed2189fe5a8c3f6d9c7a340c8647f4e4195e1f
             https://github.com/geany/geany/commit/54ed2189fe5a8c3f6d9c7a340c8647f4e4195e1f

Log Message:
-----------
Use capitilized version of Git inside documentation


Modified Paths:
--------------
    doc/geany.txt
    doc/plugins.dox

Modified: doc/geany.txt
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -4985,7 +4985,7 @@ Contributing to this document
 This document (``geany.txt``) is written in `reStructuredText`__
 (or "reST"). The source file for it is located in Geany's ``doc``
 subdirectory.  If you intend on making changes, you should grab the
-source right from git to make sure you've got the newest version. After
+source right from Git to make sure you've got the newest version. After
 editing the file, to build the HTML document to see how your changes
 look, run "``make doc``" in the subdirectory ``doc`` of Geany's source
 directory. This regenerates the ``geany.html`` file. To generate a PDF


Modified: doc/plugins.dox
2 files changed, 1 insertions(+), 1 deletions(-)
===================================================================
@@ -96,7 +96,7 @@
  *  However, once you have done your fork of geany-plugins you can develop 
  *  your plugin until you think its the right time to publish it. At this point create a 
  *  pull request for adding your patch set into master branch of geany-plugins. 
- *  Of course, you don't need to use github - just any git is fine. But github 
+ *  Of course, you don't need to use github - just any Git is fine. But github 
  *  is making it way easier for review, merging and get in touch with you for 
  *  comments.
  *


@@ Diff output truncated at 100000 characters. @@


--------------
This E-Mail was brought to you by github_commit_mail.py (Source: TBD).