1 files changed, 1 insertions, 1 deletions
diff --git a/docs/design.md b/docs/design.md
index 03c37899..210cbba8 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -266,7 +266,7 @@ KubeComponents.MailView {
 ## Configuration and Accounts
 Kube is a groupware application, so one of its most important features is being able to work with various remote backends. We live in a world of multiple devies and applications, so it is interesting to share as much state and configuration accross all different devices and applications, which is why we try to store as much of that in the backend.
-From the perspective of Kube we are working with different "Accounts". Each account represents a different backend, such as your personal IMAP or Kolab server, or a hosted offering such as GMail or KOLAB NOW. Each of those accounts may interact with various protocols such as imap, smtp, ldap, caldav etc.
+From the perspective of Kube we are working with different "Accounts". Each account represents a different backend, such as your personal IMAP or Kolab server, or a hosted offering such as GMail or Kolab Now. Each of those accounts may interact with various protocols such as imap, smtp, ldap, caldav etc.
 To add support for a new backend thus means that a new account type has to be added to Kube.

diff --git a/docs/design.md b/docs/design.md index 03c37899..210cbba8 100644 --- a/docs/design.md +++ b/docs/design.md
@@ -266,7 +266,7 @@ KubeComponents.MailView {
266	## Configuration and Accounts	266	## Configuration and Accounts
267	Kube is a groupware application, so one of its most important features is being able to work with various remote backends. We live in a world of multiple devies and applications, so it is interesting to share as much state and configuration accross all different devices and applications, which is why we try to store as much of that in the backend.	267	Kube is a groupware application, so one of its most important features is being able to work with various remote backends. We live in a world of multiple devies and applications, so it is interesting to share as much state and configuration accross all different devices and applications, which is why we try to store as much of that in the backend.
268		268
269	From the perspective of Kube we are working with different "Accounts". Each account represents a different backend, such as your personal IMAP or Kolab server, or a hosted offering such as GMail or KOLAB NOW. Each of those accounts may interact with various protocols such as imap, smtp, ldap, caldav etc.	269	From the perspective of Kube we are working with different "Accounts". Each account represents a different backend, such as your personal IMAP or Kolab server, or a hosted offering such as GMail or Kolab Now. Each of those accounts may interact with various protocols such as imap, smtp, ldap, caldav etc.
270		270
271	To add support for a new backend thus means that a new account type has to be added to Kube.	271	To add support for a new backend thus means that a new account type has to be added to Kube.
272		272