From 50777ace57956ae1b635c5fb411d7162ccf7f44a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Sat, 18 Jul 2020 21:55:59 +0200 Subject: [PATCH] what-about-design: more rephrasing stuff and typo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/what-about-design.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/posts/what-about-design.md b/content/posts/what-about-design.md index 6c15b65..dfbbf85 100644 --- a/content/posts/what-about-design.md +++ b/content/posts/what-about-design.md @@ -131,10 +131,10 @@ Maybe you're not part of Snikket's target, in which case there might someday be a similar solution that's more adapted to your use-case. For the more technical of us who understand the protocol and/or can deal with -common less united designs, it may be ok to continue using our current -applications and workaround these issues ourselves. For the masses I believe -this is not an option. Your may take this with a grain of salt as it is as a -developer that I am saying this to you. +less unified designs, it may be ok to continue using our current applications +and workaround these issues ourselves. For the masses I believe this is not an +option. You may take this with a grain of salt as it is as a developer that I +am saying this to you. In the end why does it matter to the end-user if it's actually XMPP that's being used, as long as these new solutions incorporate properties we care