Update repo mirroring docs

doc/workflow/repository_mirroring.md

@@ -2,37 +2,25 @@
 
 >[Introduced][ee-51] in GitLab Enterprise Edition 8.2.
 
-## Overview
-
 Repository Mirroring is a way to mirror repositories from external sources.
-It's going to mirror all branches, tags, and commits that you have
-in your project within another Git platform.
-
-It's very useful when, for some reason, you cannot simply remove a project
-from another source.
+It can be used to mirror all branches, tags, and commits that you have
+in your repository.
 
-Your mirror at GitLab will be updated automatically once an hour. You can manually
-update it whenever you need.
-
-## Use-cases
+Your mirror at GitLab will be updated automatically once an hour, but you can
+also manually update it whenever you need.
 
-- You migrated to GitLab but still needs to keep you project in another source.
-You simple set it up to mirror to GitLab and all the essential history of
-commits, tags and branches will be reproduced in your GitLab EE instance.
-- You have old projects in another source that you don't use actively anymore.
-You create a mirror to your active GitLab EE instance to be able to be aware of
-any eventual changes in your project.
+## Overview
 
-## Description
+Repository mirroring is very useful when, for some reason, you must use a
+project from another source.
 
 There are two kinds of repository mirroring features supported by GitLab:
 **push** and **pull**. The **push** method mirrors the repository in GitLab
 to another location, whereas the **pull** method mirrors an external repository
 in one in GitLab.
 
-By default mirror repositories are updated every hour, and all new branches, tags, and
-commits will be visible in the project's activity feed.
-
+By default, mirror repositories are updated every hour, and all new branches,
+tags, and commits will be visible in the project's activity feed.
 Users with at least [developer access][perms] to the project can also force an
 immediate update with a click of a button.
 
@@ -48,6 +36,17 @@ A few things/limitations to consider:
 - The Git LFS objects will not be synced. You'll need to push/pull them
   manually.
 
+## Use-cases
+
+- You migrated to GitLab but still need to keep you project in another source.
+  In that case, you can simply set it up to mirror to GitLab (pull) and all the
+  essential history of commits, tags and branches will be available in your
+  GitLab instance.
+- You have old projects in another source that you don't use actively anymore,
+  but don't want to remove for archiving purposes. In that case, you can create
+  a push mirror so that your active GitLab repository can push its changes to the
+  old location.
+
 ## Pulling from a remote repository
 
 You can set up a repository to automatically have its branches, tags, and commits