Fix spelling in some documentation

docs/content/b2.md

@@ -136,7 +136,7 @@ regardless of the source.
 ### Transfers ###
 
 Backblaze recommends that you do lots of transfers simultaneously for
-maximum speed.  In tests from my SSD equiped laptop the optimum
+maximum speed.  In tests from my SSD equipped laptop the optimum
 setting is about `--transfers 32` though higher numbers may be used
 for a slight speed improvement. The optimum number for you may vary
 depending on your hardware, how big the files are, how much you want
@@ -172,7 +172,7 @@ deleted then the bucket will be deleted.
 However `delete` will cause the current versions of the files to
 become hidden old versions.
 
-Here is a session showing the listing and and retreival of an old
+Here is a session showing the listing and retrieval of an old
 version followed by a `cleanup` of the old versions.
 
 Show current version and all the versions with `--b2-versions` flag.
@@ -188,7 +188,7 @@ $ rclone -q --b2-versions ls b2:cleanup-test
        15 one-v2016-07-02-155621-000.txt
 ```
 
-Retreive an old verson
+Retrieve an old version
 
 ```
 $ rclone -q --b2-versions copy b2:cleanup-test/one-v2016-07-04-141003-000.txt /tmp

docs/content/contact.md

@@ -29,7 +29,7 @@ Rclone has a Google+ page which announcements are posted to
 
 ## Twitter ##
 
-You can also follow me on twitter for rclone announcments
+You can also follow me on twitter for rclone announcements
 
   * [@njcw](https://twitter.com/njcw)
 

docs/content/crypt.md

@@ -223,7 +223,7 @@ Standard
   * file names encrypted
   * file names can't be as long (~156 characters)
   * can use sub paths and copy single files
-  * directory structure visibile
+  * directory structure visible
   * identical files names will have identical uploaded names
   * can use shortcuts to shorten the directory recursion
 
@@ -245,7 +245,7 @@ equivalents.  You can not rely on this for strong protection.
   * file names very lightly obfuscated
   * file names can be longer than standard encryption
   * can use sub paths and copy single files
-  * directory structure visibile
+  * directory structure visible
   * identical files names will have identical uploaded names
 
 Cloud storage systems have various limits on file name length and
@@ -293,7 +293,7 @@ This will have the following advantages
 
   * `rclone sync` will check the checksums while copying
   * you can use `rclone check` between the encrypted remotes
-  * you don't decrypt and encrypt unecessarily
+  * you don't decrypt and encrypt unnecessarily
 
 For example, let's say you have your original remote at `remote:` with
 the encrypted version at `eremote:` with path `remote:crypt`.  You
@@ -322,9 +322,9 @@ has a header and is divided into chunks.
   * 24 bytes Nonce (IV)
 
 The initial nonce is generated from the operating systems crypto
-strong random number genrator.  The nonce is incremented for each
+strong random number generator.  The nonce is incremented for each
 chunk read making sure each nonce is unique for each block written.
-The chance of a nonce being re-used is miniscule.  If you wrote an
+The chance of a nonce being re-used is minuscule.  If you wrote an
 exabyte of data (10¹⁸ bytes) you would have a probability of
 approximately 2×10⁻³² of re-using a nonce.
 
@@ -376,7 +376,7 @@ They are then encrypted with EME using AES with 256 bit key. EME
 (ECB-Mix-ECB) is a wide-block encryption mode presented in the 2003
 paper "A Parallelizable Enciphering Mode" by Halevi and Rogaway.
 
-This makes for determinstic encryption which is what we want - the
+This makes for deterministic encryption which is what we want - the
 same filename must encrypt to the same thing otherwise we can't find
 it on the cloud storage system.
 
@@ -400,11 +400,11 @@ used on case insensitive remotes (eg Windows, Amazon Drive).
 
 ### Key derivation ###
 
-Rclone uses `scrypt` with parameters `N=16384, r=8, p=1` with a an
+Rclone uses `scrypt` with parameters `N=16384, r=8, p=1` with an
 optional user supplied salt (password2) to derive the 32+32+16 = 80
 bytes of key material required.  If the user doesn't supply a salt
 then rclone uses an internal one.
 
 `scrypt` makes it impractical to mount a dictionary attack on rclone
-encrypted data.  For full protection agains this you should always use
+encrypted data.  For full protection against this you should always use
 a salt.

docs/content/filtering.md

@@ -69,7 +69,7 @@ docs](https://golang.org/pkg/regexp/syntax/) for more info on these.
              - doesn't match "hullo"
 
 A `{` and `}` define a choice between elements.  It should contain a
-comma seperated list of patterns, any of which might match.  These
+comma separated list of patterns, any of which might match.  These
 patterns can contain wildcards.
 
     {one,two}_potato - matches "one_potato"

docs/content/local.md

@@ -33,7 +33,7 @@ old Linux filesystem with non UTF-8 file names (eg latin1) then you
 can use the `convmv` tool to convert the filesystem to UTF-8. This
 tool is available in most distributions' package managers.
 
-If an invalid (non-UTF8) filename is read, the invalid caracters will
+If an invalid (non-UTF8) filename is read, the invalid characters will
 be replaced with the unicode replacement character, '<27>'.  `rclone`
 will emit a debug message in this case (use `-v` to see), eg
 
@@ -131,7 +131,7 @@ routine instead.
 This tells rclone to stay in the filesystem specified by the root and
 not to recurse into different file systems.
 
-For example if you have a directory heirachy like this
+For example if you have a directory hierarchy like this
 
 ```
 root

docs/content/overview.md

@@ -7,7 +7,7 @@ date: "2015-09-06"
 
 # Overview of cloud storage systems #
 
-Each cloud storage system is slighly different.  Rclone attempts to
+Each cloud storage system is slightly different.  Rclone attempts to
 provide a unified interface to them, but some underlying differences
 show through.
 

docs/content/s3.md

@@ -423,7 +423,7 @@ use the secret key as `xxxxxx/xxxx`  it will work fine.
 
 To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the "[Applications & API](https://cloud.digitalocean.com/settings/api/tokens)" page of the DigitalOcean control panel. They will be needed when promted by `rclone config` for your `access_key_id` and `secret_access_key`.
 
-When promted for a `region` or `location_constraint`, press enter to use the default value. The region must be included in the `endpoint` setting (e.g. `nyc3.digitaloceanspaces.com`). The defualt values can be used for other settings.
+When prompted for a `region` or `location_constraint`, press enter to use the default value. The region must be included in the `endpoint` setting (e.g. `nyc3.digitaloceanspaces.com`). The defualt values can be used for other settings.
 
 Going through the whole process of creating a new remote by running `rclone config`, each prompt should be answered as shown below:
 

docs/content/sftp.md

@@ -152,7 +152,7 @@ Modified times are used in syncing and are fully supported.
 SFTP supports checksums if the same login has shell access and `md5sum`
 or `sha1sum` as well as `echo` are in the remote's PATH.
 
-The only ssh agent supported under Windows is Putty's pagent.
+The only ssh agent supported under Windows is Putty's pageant.
 
 SFTP isn't supported under plan9 until [this
 issue](https://github.com/pkg/sftp/issues/156) is fixed.

docs/content/swift.md

@@ -197,7 +197,7 @@ set of OpenStack environment variables.
 When you run through the config, make sure you choose `true` for
 `env_auth` and leave everything else blank.
 
-rclone will then set any empty config parameters from the enviroment
+rclone will then set any empty config parameters from the environment
 using standard OpenStack environment variables.  There is [a list of
 the
 variables](https://godoc.org/github.com/ncw/swift#Connection.ApplyEnvironment)