[doc] Editing for better style (#1736)

* Also removed references to Persona authentication.
* Changed code comment about Persona because it's for HTTP auth
  in general. See https://github.com/FreshRSS/FreshRSS/commit/3d876091e1268e3ccd5036449a4deb5134936206
  and https://github.com/FreshRSS/FreshRSS/issues/358#issuecomment-31931484

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/en/users/07_Frequently_Asked_Questions.md b/docs/en/users/07_Frequently_Asked_Questions.md
index 6391c55f5..427da7bd9 100644
--- a/docs/en/users/07_Frequently_Asked_Questions.md
+++ b/docs/en/users/07_Frequently_Asked_Questions.md
@@ -4,10 +4,10 @@ We may not have answered all of your questions in the previous sections. The FAQ
 
 Of course, ```/i``` has a purpose! We used it for performance and usability:
 
-* it allows to serve icons, images, styles and scripts without cookies. Whitout that trick, those files will be downloaded more often, specially when the form or the Personna authentications are used. Also, HTTP requests will be heavier.
+* It allows for serving icons, images, styles and scripts without cookies. Without that trick, those files would be downloaded more often, especially when form authentication is used. Also, HTTP requests would be heavier.
 * ```./p/``` public root can be served without any HTTP access restrictions. Whereas it could be implemented in ```./p/i/```.
-* It spares from having problems while serving public resources like ```favicon.ico```, ```robots.txt```, etc.
-* It allows to display the logo instead of a white page while hitting a restriction or a delay during the loading process.
+* It avoids problems while serving public resources like ```favicon.ico```, ```robots.txt```, etc.
+* It allows the logo to be displayed instead of a white page while hitting a restriction or a delay during the loading process.
 
 ## Why robots.txt is located in a sub-folder?
 
@@ -28,8 +28,8 @@ Here are the steps to follow:
 1. __Verify SimplePie validation__ with the [SimplePie on-line tool](http://simplepie.org/demo/ "SimplePie official demo"). If it is not recognized, there is nothing we can do.
 1. __Verify FreshRSS integration__ with the [demo](http://demo.freshrss.org "FreshRSS official demo"). If it is not working, you need to [create an issue on Github](https://github.com/FreshRSS/FreshRSS/issues/new "Create an issue for FreshRSS") so we can have a look at it. If it is working, there is probably something fishy with the hosting server.
 
-Here is a list of feed which don't work:
+Here is a list of feeds which don't work:
 
 * http://foulab.org/fr/rss/Foulab_News: is not a W3C valid feed (November 2014)
 * http://eu.battle.net/hearthstone/fr/feed/news: is not a W3C valid feed (Novembre 2014)
-* http://webseriesmag.blogs.liberation.fr/we/atom.xml: is not working for the user but succeed on all the described validations (November 2014)
\ No newline at end of file
+* http://webseriesmag.blogs.liberation.fr/we/atom.xml: is not working for the user but succeed on all the described validations (November 2014)