Update README.md

diff --git a/README.md b/README.md
index 974cd177c81196cf70770815c70308ca5831c39c..ec2983b9dc7ab7407799afbcbacef626fb558a4f 100644 (file)
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ In a future release *Pelican-toot* must have its own configuration parameter for
 
 Hashtag(s) are taken - if any - from `article.tags` and concatenated separating each of them with commas.
 
-Pelican can handle tags with whitespaces (for example `#My nice article`) without problems but hashtags in Mastodon are all written without. For this reason all whitespaces in Pelican hashtags will be trimmed (`#Mynicearticle`).
+Pelican can handle tags with whitespaces (for example `#My nice article`) without problems but hashtags in Mastodon are all written without. For this reason all whitespaces from Pelican hashtags will be removed before publishing (`#Mynicearticle`).
 
 Now if your post exceeds this limit you simply will receive the errore message `your toot exceeds Mastodon max limit...`
 
@@ -51,4 +51,4 @@ There is no need to register an app in your Mastodon profile because *Pelican-to
 
 On every run *Pelican-toot* looks for a file called `pelicantoot_clientcred.secret` and - if it is not found - it gets in touch with Mastodon, creates an app called *PelicanToot* and writes API keys and other necessary information in this file.
 
-If you **cancel** this file *Pelican-toot* will create another app on its next run (this could be done in case of problem despite the fact Mastodon advise this is NOT a good behaviour since app should be created only once).
\ No newline at end of file
+If you **cancel** this file *Pelican-toot* will create another app on its next run (this could be done in case of problem despite the fact Mastodon advise this is NOT a good behaviour since app should be created only once).