what-about-design: more rephrasing stuff and typo

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2020-07-18 21:55:59 +02:00
parent fec8b4fd84
commit 50777ace57
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2

View file

@ -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. 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 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 less unified designs, it may be ok to continue using our current applications
applications and workaround these issues ourselves. For the masses I believe and workaround these issues ourselves. For the masses I believe this is not an
this is not an option. Your may take this with a grain of salt as it is as a option. You may take this with a grain of salt as it is as a developer that I
developer that I am saying this to you. am saying this to you.
In the end why does it matter to the end-user if it's actually XMPP that's 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 being used, as long as these new solutions incorporate properties we care