Overview and use cases for repo limit

doc/user/admin_area/settings/account_and_limit_settings.md

@@ -2,7 +2,7 @@
 
 ## Repository size limit
 
-> [Introduced][ee-740] in GitLab Enterprise Edition 8.12.
+> [Introduced][ee-740] in [GitLab Enterprise Edition 8.12][ee-8.12].
 
 Repositories within your GitLab instance can grow quickly, especially if you are
 using LFS. Their size can grow exponentially and eat up your storage device quite
@@ -12,6 +12,18 @@ In order to avoid this from happening, you can set a hard limit for your
 repositories' size. This limit can be set globally, per group, or per project,
 with per project limits taking the highest priority.
 
+There are numerous cases where you'll need to set up a limit for repository size.
+For instance, consider the following workflow:
+
+1. Your team develops apps which demand large files to be stored in
+the application repository
+1. Although you have enabled [Git LFS](../../../workflow/lfs/manage_large_binaries_with_git_lfs.html#git-lfs)
+to your project, your storage has grown significantly
+1. Before you blow your storage limit up, you set up a limit of 10 GB
+per repository
+
+### How it works
+
 Only a GitLab administrator can set those limits. Setting the limit to `0` means
 there are no restrictions.
 
@@ -28,5 +40,9 @@ allowed repository size.
 For more manually purging the files, read the docs on
 [reducing the repository size using Git][repo-size].
 
+> **Note:**
+> For GitLab.com, the repository size limit is 10 GB.
+
 [ee-740]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/740
 [repo-size]: ../../project/repository/reducing_the_repo_size_using_git.md
+[ee-8.12]: https://about.gitlab.com/2016/09/22/gitlab-8-12-released/#limit-project-size-ee