doc/*.mdwn: Various typo fixes
This commit is contained in:
parent
83b0d82f73
commit
3d643a5707
7 changed files with 8 additions and 8 deletions
|
@ -19,7 +19,7 @@ safe to do so.
|
||||||
* `--from=remote`
|
* `--from=remote`
|
||||||
|
|
||||||
Rather than dropping the content of files in the local repository,
|
Rather than dropping the content of files in the local repository,
|
||||||
this option can specifiy a remote from which the files'
|
this option can specify a remote from which the files'
|
||||||
contents should be removed.
|
contents should be removed.
|
||||||
|
|
||||||
* `--auto`
|
* `--auto`
|
||||||
|
|
|
@ -24,7 +24,7 @@ To make the import process add metadata to the imported files from the feed,
|
||||||
|
|
||||||
* `--force`
|
* `--force`
|
||||||
|
|
||||||
Force downoading items it's seen before.
|
Force downloading items it's seen before.
|
||||||
|
|
||||||
* `--template`
|
* `--template`
|
||||||
|
|
||||||
|
|
|
@ -20,7 +20,7 @@ nothing is output, and it exits nonzero.
|
||||||
Enable batch mode, in which a line containing the filename is read from
|
Enable batch mode, in which a line containing the filename is read from
|
||||||
stdin, the key is output to stdout (with a trailing newline), and repeat.
|
stdin, the key is output to stdout (with a trailing newline), and repeat.
|
||||||
|
|
||||||
Note that is there is no key corresponding to the file, an empty line is
|
Note that if there is no key corresponding to the file, an empty line is
|
||||||
output to stdout instead.
|
output to stdout instead.
|
||||||
|
|
||||||
# SEE ALSO
|
# SEE ALSO
|
||||||
|
|
|
@ -38,7 +38,7 @@ first "/~/" or "/~user/" is expanded to the specified home directory.
|
||||||
This checks if all specified keys are present in the annex,
|
This checks if all specified keys are present in the annex,
|
||||||
and exits zero if so.
|
and exits zero if so.
|
||||||
|
|
||||||
Exits 1 if the key is certianly not present in the annex.
|
Exits 1 if the key is certainly not present in the annex.
|
||||||
Exits 100 if it's unable to tell (perhaps the key is in the process of
|
Exits 100 if it's unable to tell (perhaps the key is in the process of
|
||||||
being removed from the annex).
|
being removed from the annex).
|
||||||
|
|
||||||
|
|
|
@ -49,7 +49,7 @@ by running "git annex sync" on the remote.
|
||||||
syncing with. This behavior can be overridden by configuring the preferred
|
syncing with. This behavior can be overridden by configuring the preferred
|
||||||
content of a repository. See [[git-annex-preferred-content]](1).
|
content of a repository. See [[git-annex-preferred-content]](1).
|
||||||
|
|
||||||
To make two repositories have the same set of fies, you should use
|
To make two repositories have the same set of files, you should use
|
||||||
[[git-annex-mirror]](1) instead of this flag.
|
[[git-annex-mirror]](1) instead of this flag.
|
||||||
|
|
||||||
* `--message=msg`
|
* `--message=msg`
|
||||||
|
|
|
@ -10,8 +10,8 @@ See [[tips/using_the_web_as_a_special_remote]] for usage examples.
|
||||||
git-annex uses [aria2](http://aria2.sourceforge.net/) to download torrents.
|
git-annex uses [aria2](http://aria2.sourceforge.net/) to download torrents.
|
||||||
|
|
||||||
If git-annex is not built using the haskell torrent library to parse
|
If git-annex is not built using the haskell torrent library to parse
|
||||||
torrents, it also needs the needs the `btshowmetainfo` program, from
|
torrents, it also needs the `btshowmetainfo` program, from either
|
||||||
either bittornado or the original BitTorrent client.
|
bittornado or the original BitTorrent client.
|
||||||
|
|
||||||
## notes
|
## notes
|
||||||
|
|
||||||
|
|
|
@ -41,6 +41,6 @@ The following tuning parameters are available:
|
||||||
Use just one level of hash directories in the git-annex branch,
|
Use just one level of hash directories in the git-annex branch,
|
||||||
instead of the default two levels.
|
instead of the default two levels.
|
||||||
|
|
||||||
Note that git-annex will automatically propigate these setting to
|
Note that git-annex will automatically propagate these settings to
|
||||||
`.git/config` for tuned repositories. You should never directly change
|
`.git/config` for tuned repositories. You should never directly change
|
||||||
these settings in `.git/config`
|
these settings in `.git/config`
|
||||||
|
|
Loading…
Reference in a new issue