Misc updates

Author: ilyaspiridonov

file_formats.md

@@ -6,7 +6,7 @@
 
 We support `Markdown` files in general. GitLocalize can work with any static site generators including `Jekyll`, `gitbook`, `Hugo` and so on.
 
-#### PO
+#### Gettext .po
 
 Fully supported (both .po and .pot)
 
@@ -30,6 +30,6 @@ Fully supported.
 
 `Markdown` and `code` cells can be translated in GitLocalize.
 
-## Request
+## Didn't find your format on the list?
 
 If you have a request for a file format, please let us know [here](https://gitlocalize.com/inquiries/new).

introduction.md

@@ -1 +1 @@
-On this page, we are collecting mini guides and answers to the most frequently asked questions. If you couldn't find an answer to your question, feel free to reach out to us through our [contact form](https://gitlocalize.com/inquiries/new) or open an issue in our [issue tracking repo](http://github.com/gitlocalize/feedback/issues).
+On this page, we are collecting mini guides and answers to the most frequently asked questions. If you couldn't find an answer to your question, or experience any issues using GitLocalize, feel free to reach out to us through our [contact form](https://gitlocalize.com/inquiries/new) or create an issue in our [issue tracking repo](http://github.com/gitlocalize/feedback/issues).

private_project_visibility.md

@@ -1,9 +1,11 @@
 # I want to Use GitLocalize for a Private Repository. Will My Project Be Private?
 
 If you are using GitLocalize for a private repository, your GitLocalize project will also be private.
-Users that are not added to the team will see a 404 error when trying to access the private project:
+Users that are not added to the team will see a 404 error when trying to access your private project:
 ![404](/assets/img/private_project_visibility/404.png)
 
 For this reason, you will need to make sure that each translator has access to your project by adding them to the team (see [Understanding Roles](/understanding_roles.html) for more information about roles and team members).
 
-In contrast, if you are using GitLocalize for a public repository, your translation project will also be public. Any user can contribute to a public project, even if they are not part of the team. It makes it easier for community members to contribute to public translation projects.
+In contrast, if you are using GitLocalize for a public repository, your translation project will also be public. Any user can contribute to a public project, even if they are not part of the team.
+
+However, users without an Admin or Moderator role will only be able to create review requests (send their translations for review to Language Moderators) without creating pull requests. Pull requests are created by Language Moderators or Admins once translations are reviewed.