From b2a8627d293b3c7531c60b1228a2917706bbbf9a Mon Sep 17 00:00:00 2001 From: Ben Lynn Date: Tue, 4 Sep 2007 00:15:57 -0700 Subject: [PATCH] Rephrased a few sentences --- intro.txt | 5 ++--- secrets.txt | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/intro.txt b/intro.txt index e15e55e..9aa8d4a 100644 --- a/intro.txt +++ b/intro.txt @@ -1,7 +1,6 @@ = Introduction = -I'll use an analogy to introduce version control. -See [[http://en.wikipedia.org/wiki/Revision_control][the Wikipedia entry on revision control]] for a saner explanation. +I'll use an analogy to introduce version control. See [[http://en.wikipedia.org/wiki/Revision_control][the Wikipedia entry on revision control]] for a saner explanation. == Work is Play == @@ -9,7 +8,7 @@ I've played computer games almost all my life. In contrast, I only started using Think of editing your code or document, or whatever, as playing a game. Once you've made a lot of progress, you'd like to save. To do so, you click on the "Save" button in your trusty editor. -But this will overwrite the old version. It's like those old school games which only had one save slot: sure you could save, but you could never go back to an older state. Which was a shame, because your previous save might have been right at a really fun part of the game that you'd like to revisit one day. Or worse still, your current save is in an unwinnable state, which means you have to start again. +But this will overwrite the old version. It's like those old school games which only had one save slot: sure you could save, but you could never go back to an older state. Which was a shame, because your previous save might have been right at a really fun part of the game that you'd like to revisit one day. Or worse still, your current save is in an unwinnable state, and you have to start again. == Version Control == diff --git a/secrets.txt b/secrets.txt index a595742..645a896 100644 --- a/secrets.txt +++ b/secrets.txt @@ -1,4 +1,4 @@ -= Git's Secrets Revealed = += Secrets Revealed = We take a peek under the hood and explain how Git performs its miracles. I will skimp over details. For in-depth descriptions refer to one of the [[.][references]]. -- 2.11.4.GIT