summaryrefslogtreecommitdiff
path: root/doc/preferred_content.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-03-29 14:39:10 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-03-29 14:39:10 -0400
commitbce30628d5e6df5b64c482bc5fe161576efaaa79 (patch)
treea62a6f6f3e55170ca48cc1a9e90808b5f0311ed7 /doc/preferred_content.mdwn
parent1d352f4c12136e6f6dd89fbfd68bc4f9ca9a5467 (diff)
update for required content
Diffstat (limited to 'doc/preferred_content.mdwn')
-rw-r--r--doc/preferred_content.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/preferred_content.mdwn b/doc/preferred_content.mdwn
index af76a0e7b..9829fc687 100644
--- a/doc/preferred_content.mdwn
+++ b/doc/preferred_content.mdwn
@@ -1,7 +1,7 @@
git-annex tries to ensure that the configured number of [[copies]] of your
data always exist, and leaves it up to you to use commands like `git annex
get` and `git annex drop` to move the content to the repositories you want
-to contain it. But sometimes, it can be good to have more fine-grained
+to contain it. But often, it can be good to have more fine-grained
control over which content is wanted by which repositories. Configuring
this allows the git-annex assistant as well as
`git annex get --auto`, `git annex drop --auto`, `git annex sync --content`,