[DOCUMENTATION] Fix misc typos in docu

Author: Josef Glatz

Documentation/COMMANDS.md

@@ -77,7 +77,7 @@ All log commands are using a grep-filter (specified as optional argument)
 |                            | __ct mysql:restore typo3 dump.sql.xz__ -> xz'ed (lzma'ed) sql dump        |
 |                            | __ct mysql:restore typo3 dump.sql --filter=typo3__ -> No TYPO3 cache tables in dump |
 | ct mysql:restore           | Create (and drops if already exists) a database and restore from a dump   |
-|                            | Dump file can be plaintext, gziped, bzip2 or lzma compressed              |
+|                            | Dump file can be plaintext, gzip, bzip2 or lzma compressed              |
 |                            | and will automatically detected                                           |
 |                            | __ct mysql:restore typo3 dump.sql.bz2__                                   |
 | ct mysql:convert           | Convert character set and collation of a database                         |

Documentation/USAGE-DOCKER.md

@@ -4,7 +4,7 @@
 
 ## Docker creation
 
-You can easly create new docker instances (from my or a custom docker boilerplate) also with code intalization
+You can easily create new docker instances (from my or a custom docker boilerplate) also with code initialization
 and Makefile running.
 
 ```bash
@@ -32,8 +32,8 @@ ct docker:create foobar --code=git... --make=build --up
 
 ## Docker startup
 
-The `docker:up` command will search the `docker-compose.yml` in the current parent directroy tree and
-execute `docker-compose` from this directroy - you don't have to change the current directroy.
+The `docker:up` command will search the `docker-compose.yml` in the current parent directory tree and
+execute `docker-compose` from this directory - you don't have to change the current directory.
 
 Also the previous docker instance will be shut down to avoid port conflicts.
 
@@ -45,7 +45,7 @@ ct docker:up
 ## Custom docker commands
 
 As `docker:up` the `docker:compose` will search the `docker-compose.yml` and will execute your command
-from this directroy.
+from this directory.
 
 ```bash
 # Stop docker instance
@@ -86,7 +86,7 @@ ct docker:exec ps
 
 You can define a common CLI script entrypoint with the environment variable CLI_SCRIPT in your docker containers.
 The environment variable will be read by `ct docker:cli` and will be executed - you don't have to jump
-into your containers, you can start your CLI_SCRIPTs from the outide.
+into your containers, you can start your CLI_SCRIPTs from the outside.
 
 ```bash
 # Execute predefined cli command with argument "help" in "main" container
@@ -110,7 +110,7 @@ ct docker:sniff mysql
 ```
 
 ## Docker cleanup
-Docker currently doesn't cleanup orphaned images or volumes so you have to cleanup your system regulary to get free disk space
+Docker currently doesn't cleanup orphaned images or volumes so you have to cleanup your system regularly to get free disk space
 
 ```bash
 ct docker:cleanup

Documentation/USAGE-MYSQL.md

@@ -17,7 +17,7 @@ ct mysql:list
 
 # Debugging
 
-The `ct mysql:querylog` and `ct mysql:slowlog` provides a convinent way to access the general query log 
+The `ct mysql:querylog` and `ct mysql:slowlog` provides a convenient way to access the general query log 
 and the slow log.
 
 In the query log you can see all queries send and executed by the MySQL database.
@@ -67,7 +67,7 @@ Also the compression is automatically detected by file mime type.
 ct mysql:restore typo3 dump.sql
 ```
 
-# Datbase charset conversion
+# Database charset conversion
 
 ```bash
 # Convert database to UTF8

Documentation/USAGE-PHP.md

@@ -4,7 +4,7 @@
 
 ## Composer (auto searching in path tree)
 
-Because you always need to jump into `composer.json` directroy `ct php:composer` will do this for you
+Because you always need to jump into `composer.json` directory `ct php:composer` will do this for you
 
 ```bash
 # Run composer install task

Documentation/USAGE-SYNC.md

@@ -69,7 +69,7 @@ ct share:restore --rsync
 
 With `sync:deploy` you can push your files to your production servers.
 Please keep in mind that this feature is just an wrapped rsync and should only be
-the simplest solution for deployment. For more advanced or centralized deployemnt try
+the simplest solution for deployment. For more advanced or centralized deployment try
 solutions build on Jenkis, Ansible and others.
 
 ```bash