diff --git a/src/_posts/2021-02-16-co-op-cloud.md b/src/_posts/2021-02-16-co-op-cloud.md
index f5d14cb..b5a316c 100644
--- a/src/_posts/2021-02-16-co-op-cloud.md
+++ b/src/_posts/2021-02-16-co-op-cloud.md
@@ -25,7 +25,7 @@ As time has gone on, though, we've had a few moments when we questioned our reli
 
 - Not being able to delegate user management to specific groups has made it hard for us to use Cloudron's Single Sign On system with groups who manage their own users.
 
-- Cloudron's central paradigm is focussed on "non-technical" users with the nice web front end for managing apps. However, we found our clients actually need to know what "domain name" or "storage volumes" are. That's why they pay us for support. They want it to "just work". Using an interface designed for non-technical users is not suitable for technical users and adds a lot of bloat.
+- Cloudron's central paradigm is focussed on "non-technical" users with the nice web front end for managing apps. However, we found our clients don't actually need to know what "domain name" or "storage volumes" are. That's why they pay us for support. They want it to "just work". Using an interface designed for non-technical users is not suitable for technical users and adds a lot of bloat.
 
 - Cloudron is a bit of a [black box](https://en.wikipedia.org/wiki/Black_box). When something breaks, it breaks hard and requires technical users to respond and investigate and then fix the issues.