1. Pierre-Yves David
  2. mutable-history

Commits

Pierre-Yves David  committed b116de5

tutorial: fix some various typo

  • Participants
  • Parent commits 01a2704
  • Branches stable

Comments (0)

Files changed (1)

File tests/test-tutorial.t

View file
  • Ignore whitespace
 Getting rid of branchy history
 ----------------------------------
 
-While I was working on my list. someone help made a change remotly.
+While I was working on my list. someone made a change remotly.
 
   $ cd ../remote
   $ hg up -q
 
 .. note: We can't amend changeset 7e82d3f3c2cb or 9ca060c80d74 as they are immutable.
 
-I now want to push to remote all my changes except the bathroom one, which I'm not
-totally happy with yet. To be able to push "SPAM SPAM" I need a version of "SPAM SPAM" which is not a child of
-"bathroom stuff"
+ I now want to push to remote all my changes except the bathroom one, which I'm
+ not totally happy with yet. To be able to push "SPAM SPAM" I need a version of
+ "SPAM SPAM" which is not a child of "bathroom stuff"
 
 You can use 'rebase -r' or 'grab' for that:
 
   adding file changes
   added 3 changesets with 3 changes to 1 files
 
-for simplicity shake we get the bathroom change in line again
+for simplicity sake we get the bathroom change in line again
 
   $ hg rebase -r 10b8aeaa8cc8 -d a224f2a4fb9f
   merging shopping
 -----------------------
 
 
-sharing mutable changeset
+sharing mutable changesets
 ----------------------------
 
-To share mutable changeset with others, just check that the repo you interact
+To share mutable changesets with others, just check that the repo you interact
 with is "not publishing". Otherwise you will get the previously observe
 behavior where exchanged changeset are automatically published.
 
 
 
 To resolve this unstable state, you need to rebase bf1b0d202029 onto
-a44c85f957d3. The "hg evolve" command will do this for you.
+a44c85f957d3. The `hg evolve` command will do this for you.
 
 It has a --dry-run option to only suggest the next move.