Skip to content
This repository
Browse code

README: Writing clarity

  • Loading branch information...
commit 6db55552d009f329b986350f052d98301a3fcca4 1 parent eae7447
Robb Shecter authored

Showing 1 changed file with 2 additions and 2 deletions. Show diff stats Hide diff stats

  1. 4  README.md
4  README.md
Source Rendered
@@ -20,7 +20,7 @@ Values
20 20
 
21 21
 * **Principle of Least Surprise.** Each command will only do things
22 22
     related to one *conceptual function*. The underlying implementation
23  
-    never forces features into the commands. This is similar to the 
  23
+    must never force features into the commands. This is related to the 
24 24
     Unix philosophy, [do one thing and do it well](http://en.wikipedia.org/wiki/Unix_philosophy).
25 25
     Here in this project, that "thing" is the conceptual function from the end-user's 
26 26
     perspective. 
@@ -108,7 +108,7 @@ Notes
108 108
 * `g add` isn't necessary for staging since `g commit` will
109 109
 automatically add objects. In fact, by default, g does not expose the concept of
110 110
 staging through its interface. It'd be very interesting to support a modular abstration,
111  
-exposing the staging area by configuration option. Mercurial has done this route: not exposing
  111
+exposing the staging area by configuration option. Mercurial has gone this route: not exposing
112 112
 a staging area by default.
113 113
 
114 114
 

0 notes on commit 6db5555

Please sign in to comment.
Something went wrong with that request. Please try again.