Fixed all the errors found by Ryan

Author: javiereguiluz

contributing/documentation/format.rst

@@ -156,7 +156,7 @@ If you want to modify that title, use this alternative syntax:
         :doc:`environments`
 
 **Links to the API** follow a different syntax, where you must specify the type
-of linked resource (``namespace``, ``class`` or ``method``):
+of the linked resource (``namespace``, ``class`` or ``method``):
 
 .. code-block:: rst
 

contributing/documentation/overview.rst

@@ -3,11 +3,12 @@ Contributing to the Documentation
 
 One of the essential principles of the Symfony project is that **documentation is
 as important as code**. That's why a great amount of resources are dedicated to
-document new features and to maintain updated the rest of the documentation.
+documenting new features and to keeping the rest of the documentation up to date.
 
-More than 800 developers all around the world have contributed to Symfony
+More than 800 developers all around the world have contributed to Symfony's
 documentation, and we are glad that you are considering joining this big family.
-This guide will explain everything you need to contribute to Symfony documentation.
+This guide will explain everything you need to contribute to the Symfony
+documentation.
 
 Before Your First Contribution
 ------------------------------
@@ -18,20 +19,20 @@ Before Your First Contribution
   If you are not familiar with this format, read :doc:`this article </contributing/documentation/format>`
   for a quick overview of its basic features.
 * Symfony documentation is hosted on GitHub_. You'll need a GitHub user account
-  to contribute documentation.
+  to contribute to the documentation.
 * Symfony documentation is published under a
   :doc:`Creative Commons BY-SA 3.0 License </contributing/documentation/license>`
   and all your contributions will implicitly adhere to that license.
 
 Your First Documentation Contribution
 -------------------------------------
 
-In this section you'll learn how to contribute to Symfony documentation for the
-first time. Next section will explain the abbreviated process to follow for the
-next contributions.
+In this section you'll learn how to contribute to the Symfony documentation for
+the first time. The next section will explain the shorter process you'll follow
+in the future for every contribution after your first.
 
 Let's imagine that you want to improve the installation chapter of the Symfony
-book. In order to do those changes, follow these steps:
+book. In order to make your changes, follow these steps:
 
 **Step 1.** Go to the official Symfony documentation repository located at
 `github.com/symfony/symfony-docs`_ and `fork the repository`_ to your personal
@@ -54,7 +55,7 @@ Nowadays this is the ``2.3`` branch:
     $ cd symfony-docs/
     $ git checkout 2.3
 
-If you were instead documenting a new feature, switch to the first Symfony
+If you are instead documenting a new feature, switch to the first Symfony
 version which included it: ``2.5``, ``2.6``, etc.
 
 **Step 4.** Create a dedicated **new branch** for your changes. This greatly
@@ -74,15 +75,15 @@ doc:`/contributing/documentation/standards`.
 .. code-block:: bash
 
     $ git commit book/installation.rst
-    $ git push
+    $ git push origin improve_install_chapter
 
 **Step 7.** Everything is now ready to initiate a **pull request**. Go to your
 forked repository at ``https//github.com/<YOUR GITHUB USERNAME>/symfony-docs``
-and click on the ``Pull Requests`` link located at the sidebar.
+and click on the ``Pull Requests`` link located in the sidebar.
 
 Then, click on the big ``New pull request`` button. As GitHub cannot guess the
 exact changes that you want to propose, select the appropriate branches where
-changes should be applied:
+changes should be applied:º
 
 .. image:: /images/docs-pull-request-change-base.png
    :align: center
@@ -91,10 +92,10 @@ In this example, the **base repository** should be ``symfony/symfony-docs`` and
 the **base branch** should be the ``2.3``, which is the branch that you selected
 to base your changes on. The **compare repository** should be your forked copy
 of ``symfony-docs`` and the **compare branch** should be ``improve_install_chapter``,
-which is the name that you selected to work on your changes.
+which is the name of the branch you created and where you made your changes.
 
 **Step 8.** The last step is to prepare the **description** of the pull request.
-To ensure that your work is reviewed quickly, you have to add the following table
+To ensure that your work is reviewed quickly, please add the following table
 at the beginning of your pull request description:
 
 .. code-block:: text
@@ -123,7 +124,7 @@ carefully review your work in short time and they will let you know about any
 required change.
 
 In case you need to add or modify anything, there is no need to create a new
-pull request. Just make sure that you are in the correct branch, make your
+pull request. Just make sure that you are on the correct branch, make your
 changes and push them:
 
 .. code-block:: bash
@@ -147,18 +148,17 @@ The first contribution took some time because you had to fork the repository,
 learn how to write documentation, comply with the pull requests standards, etc.
 The second contribution will be much easier, except for one detail: given the
 furious update activity of the Symfony documentation repository, odds are that
-your fork is now outdated comparing it with the official repository.
+your fork is now out of date with the official repository.
 
-Solving this problem requires to `sync your fork`_ with the original repository.
-To do so, execute first this command to tell git which is the original repository
-from which you created the fork:
+Solving this problem requires you to `sync your fork`_ with the original repository.
+To do this, execute this command first to tell git about the original repository:
 
 .. code-block:: bash
 
     $ cd projects/symfony-docs/
     $ git remote add upstream https://github.com/symfony/symfony-docs.git
 
-Now you can **sync your fork** executing the following command:
+Now you can **sync your fork** by executing the following command:
 
 .. code-block:: bash
 
@@ -167,7 +167,8 @@ Now you can **sync your fork** executing the following command:
     $ git checkout master
     $ git merge upstream/master
 
-Now you can proceed following the same steps explained in the previous section:
+Great! Now you can proceed by following the same steps explained in the previous
+section:
 
 .. code-block:: bash
 
@@ -193,18 +194,18 @@ Now you can proceed following the same steps explained in the previous section:
     # | Applies to    | [Symfony version numbers this applies to]
     # | Fixed tickets | [comma separated list of tickets fixed by the PR]
 
-Your second contribution is now completed, so **go and celebrate again!**
-You will also see how your ranking improves in the list of
+Your second contribution is now complete, so **go and celebrate again!**
+You can also see how your ranking improves in the list of
 `Symfony Documentation Contributors`_.
 
 Your Next Documentation Contributions
 -------------------------------------
 
 Now that you've made two contributions to the Symfony documentation, you are
 probably comfortable with all the Git-magic involved in the process. That's
-why your next contributions would be much faster and easier. Here you can find
-the complete steps to contribute to Symfony documentation, which you can use as
-a **checklist**:
+why your next contributions would be much faster. Here you can find the complete
+steps to contribute to the Symfony documentation, which you can use as a
+**checklist**:
 
 .. code-block:: bash
 
@@ -244,8 +245,8 @@ You guessed right: after all this hard work, it's **time to celebrate again!**
 Frequently Asked Questions
 --------------------------
 
-Why Do my Changes so Long to Be Reviewed and/or Merged?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Why Do my Changes Take so Long to Be Reviewed and/or Merged?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Please be patient. It can take up to several days before your pull request can
 be fully reviewed. After merging the changes, it could take again several hours
@@ -272,7 +273,7 @@ What If I Want to Submit my Work without Fully Finishing It?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can do it. But please use one of these two prefixes to let reviewers know
-which is the state of your work:
+about the state of your work:
 
 * ``[WIP]`` (Work in Progress) is used when you are not yet finished with your
   pull request, but you would like it to be reviewed. The pull request won't
@@ -283,14 +284,15 @@ which is the state of your work:
   will not be merged until it is merged in the core code (or closed if the
   change is rejected).
 
-Would You Admit a Huge Pull Request with Lots of Changes?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Would You Accept a Huge Pull Request with Lots of Changes?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 First, make sure that the changes are somewhat related. Otherwise, please create
 separate pull requests. Anyway, before submitting a huge change, it's probably a
 good idea to open an issue in the Symfony Documentation repository to ask the
 managers if they agree with your proposed changes. Otherwise, they could refuse
-your proposal after having made all the work and you would have wasted a lot of time.
+your proposal after you put all that hard work into making the changes. We
+definitely don't want you to waste your time!
 
 .. _`github.com/symfony/symfony-docs`: https://github.com/symfony/symfony-docs
 .. _reStructuredText: http://docutils.sourceforge.net/rst.html