3 files changed, 5 insertions, 6 deletions

diff --git a/docs/cryptography.md b/docs/cryptography.md
index 3a485df9..d59cf216 100644
--- a/docs/cryptography.md
+++ b/docs/cryptography.md
@@ -4,7 +4,7 @@
 
 To get Open PGP support we use GpgME >= 1.8.0. GpgME has now include Gpgme++ and QGpgME, that were living before in kdepim repositories.
 
-GpgME gives use directly PGP and SMime support and needs gpg-agent, gpg2, gpgsm and a pinentry to be installed to work correctly. The package names differ between the distributions on Fedora the are named gnupg2, gnupg2-smime and pinentry-qt (there are several different flavours for diffrent environments. I think the Qt flavour mathes best).
+GpgME gives us directly PGP and SMime support and needs gpg-agent, gpg2, gpgsm and a pinentry to be installed to work correctly. The package names differ between the distributions on Fedora the are named gnupg2, gnupg2-smime and pinentry-qt (there are several different flavours for diffrent environments. I think the Qt flavour matches best).
 
 gnupg using ~/.gnupg as default homedir to store every file it uses. In our test docker environment, we setup all relevat files and added keys without passphrase to test PGP/SMime support. We also incuded one key `With Passphrase "test" <passphrase@example.org>`, that has a phassphrase named `test`.
 
diff --git a/docs/design.md b/docs/design.md
index 3b37a5b2..4152bb93 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -13,7 +13,7 @@ The overall architecture is split into three layers; Ui, Domain Logic and Infras
 +----------------------------+
 |                            |
 |        Domain Logic        |
-|        Actions/Models      |
+|        Fabric/Models       |
 |                            |
 +--------------+------+------+
 |              |      |      |
diff --git a/docs/project.md b/docs/project.md
index 9e0db20b..2cdbe2af 100644
--- a/docs/project.md
+++ b/docs/project.md
@@ -17,6 +17,7 @@ This section is supposed to outline that.
         * Desktop integration (notifications, startmenu)
     * Offline capability
     * Cryptography
+    * Multi-account support
 
 * To Kontact/Thunderbird/...
     * Simple but powerful UI (assuming we can achieve that)
@@ -63,10 +64,8 @@ Decisions are generally made in discussion with the team, and result in document
 
 Should the team not be able to reach consensus, the team lead makes the final decision.
 
-NOTE: We should probably have a phabricator board for open decisions.
-
 ## Planning
-All planning happens on the [KDE Phabricator instance](https://phabricator.kde.org/project/view/43/).
+All planning happens on the [KDE Phabricator instance](https://phabricator.kde.org/tag/kube/).
 
 ## Releases / Milestones
 Releases will follow achieved milestones. Milestones are assembled from tasks on the roadmap.
@@ -75,7 +74,7 @@ Releases will follow achieved milestones. Milestones are assembled from tasks on
 The product will follow the semantic versioning scheme (semver.org), with each feature release corresponding to a milestone on phabricator.
 
 ## Git repository
-The git repository can be found here: [git://anongit.kde.org/kontact-quick](git://anongit.kde.org/kontact-quick)
+The git repository can be found here: [git://anongit.kde.org/kube](git://anongit.kde.org/kube)
 
 The "development" branch is used for the latest development version, master is always stable and always releasable. Branches for specific versions that receive patch releases may be created as required.