# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1245352609 -7200
#      Thu Jun 18 21:16:49 2009 +0200
# Node ID 03ef61d6882bad0c6b16281af064ef61827487ca
# Parent  c3aeeff8fb29050772691d8b14c684bc99167766
Updated the readme some more...

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -18,14 +18,14 @@
 Commands
 =========
 
-You can clone a Git repository from Hg by running `hg gclone [url]`.  It will create a directory appended with a '-hg', for example, if you were to run `hg gclone git://github.com/schacon/munger.git` it would clone the repository down into the directory 'munger-hg', then convert it to an Hg repository for you.
+You can clone a Git repository from Hg by running `hg clone [url]`.  For example, if you were to run `hg clone git://github.com/schacon/munger.git` it would clone the repository down into the directory 'munger.git', then convert it to an Hg repository for you.
 
 	hg clone git://github.com/schacon/munger.git
 	
-If you are starting from an existing Hg repository, you have to setup a Git repository somewhere that you have push access to, add it as a Git remote and then run `hg gpush` from within your project.  For example:
+If you are starting from an existing Hg repository, you have to setup a Git repository somewhere that you have push access to, add it as default path or default-push path in your .hg/hgrc and then run `hg push` from within your project.  For example:
 
 	$ cd hg-git # (an Hg repository)
-	$ (edit .hg/hgrc and add the target git repo in the path section)
+	$ (edit .hg/hgrc and add the target git url in the path section)
 	$ hg push
 
 This will convert all our Hg data into Git objects and push them up to the Git server.