Mercurial > hg-stable
changeset 718:7dae73778114
Fix typos in FAQ
| author | jdc@uwo.ca |
|---|---|
| date | Sun, 17 Jul 2005 08:39:44 +0100 |
| parents | a51e3ded642d |
| children | dda258572847 c6b912f8b5b2 |
| files | doc/FAQ.txt |
| diffstat | 1 files changed, 4 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/FAQ.txt Sat Jul 16 17:25:05 2005 +0100 +++ b/doc/FAQ.txt Sun Jul 17 08:39:44 2005 +0100 @@ -65,7 +65,7 @@ The 'tip' is the most recently changed head, and also the highest numbered revision. If you have just made a commit, that commit will be -the head. Alternately, if you have just pulled from another +the tip. Alternately, if you have just pulled from another repository, the tip of that repository becomes the current tip. The 'tip' is the default revision for many commands such as update, @@ -152,7 +152,7 @@ pull multiple copies over the network. No need to check files out here as you won't be changing them. -The outgoing tree contains all the changes you intend for merger into +The outgoing tree contains all the changes you intend for merge into upsteam. Publish this tree with 'hg serve" or hgweb.cgi or use 'hg push" to push it to another publicly availabe repository. @@ -196,7 +196,7 @@ If you'd like to request a feature, send your request to mercurial@selenic.com. As Mercurial is still very new, there are -certainly features it is missing and you can give up feedback on how +certainly features it is missing and you can give us feedback on how best to implement them. @@ -256,7 +256,7 @@ A manifest is simply a list of all files in a given revision of a project along with the nodeids of the corresponding file revisions. So grabbing a given version of the project means simply looking up its -manifest and reconstruction all the file revisions pointed to by it. +manifest and reconstructing all the file revisions pointed to by it. A changeset is a list of all files changed in a check-in along with a change description and some metadata like user and date. It also