Merge pull request #628 from krook/fix-markdown-typoes

Correcting typos in the {ADVANCED, CONTRIBUTING, README}.md files.

Author: dmp42

ADVANCED.md

@@ -4,13 +4,13 @@
 
 ## "extras"
 
-The registry support additional features (that require additional dependencies) that you may require at install time.
+The registry supports additional features (that require additional dependencies) that you may require at install time.
 
 ### Installation
 
 If you are using the official registry container, you don't need to do anything, as all extras are installed by default.
 
-If you are using pip, you have to explicitely request the extra you want, using pip extra syntax:
+If you are using pip, you have to explicitly request the extra you want, using pip extra syntax:
 
 `pip install docker-registry[someextra]`
 
@@ -30,7 +30,7 @@ Note the bugsnag "stage" will be set to the specified configuration "flavor".
 
 #### "newrelic"
 
-This encapsulate your registry inside the new-relic agent.
+This encapsulates your registry inside the new-relic agent.
 
 You need to write a new-relic ini file, then use the following environment variables:
 
@@ -131,7 +131,7 @@ sudo yum install python-devel libevent-devel python-pip gcc xz-devel
 ```
 
 NOTE: On RHEL and CentOS you will need the
-[EPEL](http://fedoraproject.org/wiki/EPEL) repostitories enabled. Fedora
+[EPEL](http://fedoraproject.org/wiki/EPEL) repositories enabled. Fedora
 should not require the additional repositories.
 
 Then install the Registry app:
@@ -188,9 +188,9 @@ docker run \
 
 ## Advanced configuration options
 
-### Priviledged access
+### Privileged access
 
-It's possible to allow priviledge access to your registry using an rsa key (useful for administration scripts for example).
+It's possible to allow privileged access to your registry using an RSA key (useful for administration scripts for example).
 
 To do so, specify in your config:
 
@@ -213,7 +213,7 @@ Associated public key :
 
 ### Email exceptions
 
-Settings these options makes the Registry send an email on each code Exception:
+Setting these options makes the Registry send an email on each code Exception:
 
 1. `email_exceptions`:
   1. `smtp_host`: hostname to connect to using SMTP

CONTRIBUTING.md

@@ -21,7 +21,7 @@ It provides:
 
  * exceptions
  * a driver interface describing how the registry interacts with the data storage
- * a compatibility layer (eg: abstracting behavior differences between python versions)
+ * a compatibility layer (e.g.: abstracting behavior differences between python versions)
  * common useful utility code
  * filesystem storage driver
 
@@ -71,7 +71,7 @@ Drivers must stay inside `docker_registry.drivers`.
 
 We use `nose`, `coverage`, `hacking` (for `flake`), `tox` and `travis`.
 
-Wherever you are coding (registy, core, or driver), your friends are thus:
+Wherever you are coding (registry, core, or driver), your friends are thus:
 
  * run the tests: `python setup.py nosetests`
  * check your style: `flake8`
@@ -92,7 +92,7 @@ Existing code shouldn't regress.
 
 ## Storage driver developer howto
 
-Have a look at the [elliptics driver](https://github.com/noxiouz/docker-registry-driver-elliptics) and copy its stucture.
+Have a look at the [elliptics driver](https://github.com/noxiouz/docker-registry-driver-elliptics) and copy its structure.
 
 Explore the files.
 
@@ -108,7 +108,7 @@ Pretty much:
 Drivers are expected to receive bytes and to return bytes.
 Don't try to decode or encode content.
 
-## Development environement notes
+## Development environment notes
 
 We don't currently run any tests for python3, as we are stuck on gevent not being py3 ready.
 

README.md

@@ -6,7 +6,7 @@ Docker-Registry
 About this document
 ===================
 
-As the documentation evolves with different registry versions, be sure that before reading any further you do:
+As the documentation evolves with different registry versions, be sure that before reading any further you:
 
  * check which version of the registry you are running
  * switch to the corresponding tag to access the README that matches your product version
@@ -134,7 +134,7 @@ When using the `config_sample.yml`, you can pass all options through as environm
 1. `loglevel`: string, level of debugging. Any of python's
    [logging](http://docs.python.org/2/library/logging.html) module levels:
    `debug`, `info`, `warn`, `error` or `critical`
-1. `debug`: boolean, make the `/_ping` endpoint output more useful informations, such as library versions and host information.
+1. `debug`: boolean, make the `/_ping` endpoint output more useful information, such as library versions and host information.
 1. `storage_redirect`: Redirect resource requested if storage engine supports
    this, e.g. S3 will redirect signed URLs, this can be used to offload the
    server.
@@ -198,7 +198,7 @@ common:
   sqlalchemy_index_database: sqlite:////tmp/docker-registry.db
 ```
 
-In this case, the module is imported, and an instance of it's `Index`
+In this case, the module is imported, and an instance of its `Index`
 class is used as the search backend.
 
 ### Mirroring Options
@@ -228,7 +228,7 @@ to spawn a [redis-server](http://redis.io/) configured in
 shows an example to enable the LRU cache using the config directive `cache_lru`.
 
 Once this feature is enabled, all small files (tags, meta-data) will be cached
-in Redis. When using a remote storage backend (like Amazon S3), it will speeds
+in Redis. When using a remote storage backend (like Amazon S3), it will speed
 things up dramatically since it will reduce roundtrips to S3.
 
 All config settings are placed in a `cache` or `cache_lru` section.
@@ -250,10 +250,10 @@ To use and install one of these alternate storages:
 
  * `pip install docker-registry-driver-NAME`
  * in the configuration set `storage` to `NAME`
- * add any other storage dependent configuraiton option to the conf file
+ * add any other storage dependent configuration option to the conf file
  * review the storage specific documentation for additional dependency or configuration instructions.
 
- Currently, we are aware of the following storage driver:
+ Currently, we are aware of the following storage drivers:
 
   * [elliptics](https://github.com/noxiouz/docker-registry-driver-elliptics)
   * [swift](https://github.com/bacongobbler/docker-registry-driver-swift)
@@ -333,7 +333,7 @@ For more features and advanced options, have a look at the [advanced features do
 For developers
 ==============
 
-Read [contribute](CONTRIBUTE.md)
+Read [contributing](CONTRIBUTING.md)
 
 [search-endpoint]: http://docs.docker.com/reference/api/docker-io_api/#search
 [SQLAlchemy]: http://docs.sqlalchemy.org/