git-read-tree.txt: update sparse checkout examples

[git.git] / Documentation / gitcvs-migration.txt

diff --git a/Documentation/gitcvs-migration.txt b/Documentation/gitcvs-migration.txt
index 0e49c1c03776af30f0509679f720273061aaa7b3..d861ec452f8f115017830422b4b459861f8bd703 100644 (file)
--- a/Documentation/gitcvs-migration.txt
+++ b/Documentation/gitcvs-migration.txt
@@ -47,25 +47,25 @@ them first before running git pull.
 [NOTE]
 ================================
 The 'pull' command knows where to get updates from because of certain
 [NOTE]
 ================================
 The 'pull' command knows where to get updates from because of certain

-configuration variables that were set by the first 'git-clone'
+configuration variables that were set by the first 'git clone'

 command; see `git config -l` and the linkgit:git-config[1] man
 page for details.
 ================================
 
 You can update the shared repository with your changes by first committing
 command; see `git config -l` and the linkgit:git-config[1] man
 page for details.
 ================================
 
 You can update the shared repository with your changes by first committing

-your changes, and then using the 'git-push' command:
+your changes, and then using the 'git push' command:

 
 ------------------------------------------------
 $ git push origin master
 ------------------------------------------------
 
 to "push" those commits to the shared repository.  If someone else has
 
 ------------------------------------------------
 $ git push origin master
 ------------------------------------------------
 
 to "push" those commits to the shared repository.  If someone else has

-updated the repository more recently, 'git-push', like 'cvs commit', will
+updated the repository more recently, 'git push', like 'cvs commit', will

 complain, in which case you must pull any changes before attempting the
 push again.
 
 complain, in which case you must pull any changes before attempting the
 push again.
 

-In the 'git-push' command above we specify the name of the remote branch
-to update (`master`).  If we leave that out, 'git-push' tries to update
+In the 'git push' command above we specify the name of the remote branch
+to update (`master`).  If we leave that out, 'git push' tries to update

 any branches in the remote repository that have the same name as a branch
 in the local repository.  So the last 'push' can be done with either of:
 
 any branches in the remote repository that have the same name as a branch
 in the local repository.  So the last 'push' can be done with either of: