aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFriendika <info@friendika.com>2011-03-23 05:33:41 -0700
committerFriendika <info@friendika.com>2011-03-23 05:33:41 -0700
commit620d7bd7701160560a038c7eff0e3f481047014d (patch)
tree1bbd6ad1f750b7d2ee57a5de11851dffacbe8662
parentf0b791fe9a4a37f87811ae1a6c45b9cb6778bf3e (diff)
downloadvolse-hubzilla-620d7bd7701160560a038c7eff0e3f481047014d.tar.gz
volse-hubzilla-620d7bd7701160560a038c7eff0e3f481047014d.tar.bz2
volse-hubzilla-620d7bd7701160560a038c7eff0e3f481047014d.zip
upd8 readme
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index 4ec6441c7..484550393 100644
--- a/README
+++ b/README
@@ -89,12 +89,12 @@ But we're creating something completely different.
Something better.
- Start with richer communications. Adorn your text, colour it. We've got a
+ Start with richer communications. Adorn your text, colour it. We've got a
text counter in case you're sending across to one of the primitive social
networks, but we don't think you should have to squeeze your communications
into some arbitrary limit. Free yourself from thinking how to squeeze your
message into 140 or 420 characters, or sending messages in some strange
-short-hand code. Edit your text after you send it. It's OK.
+short-hand code. Even edit your text after you send it. It's OK.
A single instance of Friendika can easily support hundreds of (and up to
several thousand) people using commodity hosting hardware. You could even run