diff --git a/docs/Database.md b/docs/Database.md
index 60e55ef0..b4eca8d0 100644
--- a/docs/Database.md
+++ b/docs/Database.md
@@ -1,4 +1,5 @@
 # Maintenance Operations
 <div>
 Manage aptly’s internal metadata database and package pool.
+
 </div>
diff --git a/docs/Mirrors.md b/docs/Mirrors.md
index 18717d29..4bacaec1 100644
--- a/docs/Mirrors.md
+++ b/docs/Mirrors.md
@@ -1,8 +1,8 @@
 # Manage Remote Repository Mirrors
 <div>
-Manage mirrors of remote Debian repositories.
+Manage mirrors of remote Debian repositories (http, https or ftp).
 
-HTTP, HTTPS and FTP repositories are supported.
+Flat debian repositories, mirroring source packages and debian installers is supported.
 
 </div>
 
diff --git a/docs/Publish.md b/docs/Publish.md
index b5e172b9..3e497a67 100644
--- a/docs/Publish.md
+++ b/docs/Publish.md
@@ -1,22 +1,17 @@
 # Publish Repositories and Mirrors
 <div>
 
-Publish snapshot or local repo as Debian repository which could be served by HTTP/FTP/rsync server. Repository is signed by user's key with GnuPG. Key should be created beforehand (see section GPG Keys below).  Published repository could be consumed directly by apt.
+Publish snapshot or local repo as Debian repository to be used as APT source on Debian based systems.
 
-Repositories could be published to Amazon S3 service: create bucket,
-[configure publishing endpoint](/doc/feature/s3/) and use S3 endpoint when
-publishing.
+The published repository is signed with the user's GnuPG key.
 
+Repositories can be published to local directories, Amazon S3 buckets, Azure or Swift Storage.
 
 #### GPG Keys
 
-GPG key is required to sign any published repository. Key should be generated before publishing first repository.
+GPG key is required to sign any published repository. The key pari should be generated before publishing.
 
-Key generation, storage, backup and revocation is out of scope of this document, there are many tutorials available, e.g. [this one](http://fedoraproject.org/wiki/Creating_GPG_Keys).
-
-Publiс part of the key should be exported from your keyring using `gpg --export --armor` and imported into apt keyring using `apt-key` tool on all machines that would be using published repositories.
-
-Signing releases is highly recommended, but if you want to skip it, you can either use `gpgDisableSign` configuration option or `--skip-signing` flag.
+Publiс part of the key should be exported from your keyring using `gpg --export --armor` and imported on the system which uses a published repository.
 
 #### Parameters
 
diff --git a/docs/Tasks.md b/docs/Tasks.md
index b71ca31a..03668d8e 100644
--- a/docs/Tasks.md
+++ b/docs/Tasks.md
@@ -1,8 +1,8 @@
 # Background Tasks
 <div>
-An aptly task is a sequence of multiple aptly commands run within a single aptly thread.
 
-For example, a task could be to [create a new repository](/doc/aptly/repo/create), [add packages to it](/doc/aptly/repo/add), [create a snapshot](/doc/aptly/snapshot/create) and [serve it](/doc/aptly/serve).
+Several API operations allow to be run in background asynchronously in a task. In that case, a Task object with an ID and a State is returned, which can be queried for progress.
+
+Tasks should be deleted once they are no longer in progress, in order to not cause memory overflows.
 
-Four commands can be now run in a single command.
 </div>