From f13c4c5a35a18d8478b276cc44570bbc3398aa73 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Wed, 25 May 2011 16:21:17 -0400
Subject: [PATCH] Selected Apache License.  Dropped : from name.  Its simpler.

---
 docs/01_eclipse.mkd |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/01_eclipse.mkd b/docs/01_eclipse.mkd
index c04834c..e768b73 100644
--- a/docs/01_eclipse.mkd
+++ b/docs/01_eclipse.mkd
@@ -1,17 +1,17 @@
 ## Eclipse Tips
 
 ### Do Not Verify Self-Signed Certificates
-If you are using a self-signed certificate, like the one that is automatically generated by Git:Blit, you have to tell Eclipse/EGit to ignore certificate verification errors.
+If you are using a self-signed certificate, like the one that is automatically generated by Gitblit, you have to tell Eclipse/EGit to ignore certificate verification errors.
 
 ![sslverify](sslverify.png "http.sslVerify setting")
 
 ![sslverify2](sslverify2.png "Adding http.sslVerify setting")    
 
-### Pushing a New Project to a New Git:Blit Repository
+### Pushing a New Project to a New Gitblit Repository
 1. Project Root->Team->Share->Git
 Create a Git repository inside the project
 
-### Pushing a Git-Controlled Project to another Git:Blit Repository
+### Pushing a Git-Controlled Project to another Gitblit Repository
 1. Project Root->Team->Remote->Push
 2. Enter the URL information of the repository
 3. In the Refspec dialog click the buttons named  "All all branches spec" and "All all tags spec"

--
Gitblit v1.9.1