aboutsummaryrefslogtreecommitdiff
path: root/doc/use_case
diff options
context:
space:
mode:
authorGravatar http://sunny256.sunbase.org/ <sunny256@web>2011-02-15 05:58:23 +0000
committerGravatar admin <admin@branchable.com>2011-02-15 05:58:23 +0000
commit982d0962b3ff4e82e83b715d8cc3fc93ea71783c (patch)
tree589aca9c59ad38d888da018892411a96e7b8c667 /doc/use_case
parent000d9fcf334436dc085d52655dc07f69cd465980 (diff)
Typo fixes in use_cases/Bob.mdwn
Diffstat (limited to 'doc/use_case')
-rw-r--r--doc/use_case/Bob.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/use_case/Bob.mdwn b/doc/use_case/Bob.mdwn
index a5dc01b37..573d9cde9 100644
--- a/doc/use_case/Bob.mdwn
+++ b/doc/use_case/Bob.mdwn
@@ -6,13 +6,13 @@ safe place.
With git-annex, Bob has a single directory tree that includes all
his files, even if their content is being stored offline. He can
reorganize his files using that tree, committing new versions to git,
-without worry about accidentially deleting anything.
+without worry about accidentally deleting anything.
When Bob needs access to some files, git-annex can tell him which drive(s)
they're on, and easily make them available. Indeed, every drive knows what
is on every other drive.
-Run in a cron job, git-annex adds new files to achival drives at night. It
+Run in a cron job, git-annex adds new files to archival drives at night. It
also helps Bob keep track of intentional, and unintentional copies of
files, and logs information he can use to decide when it's time to duplicate
the content of old drives.