Removed extra troubleshooting content

Because there is a separate troubleshooting page

doc/topics/git/lfs/index.md

@@ -61,13 +61,6 @@ When you create a merge request from your fork back to the upstream project, and
 your merge request contains a new Git LFS object, GitLab associates the new LFS object
 with the _upstream_ project after merge.
 
-## Known limitations
-
-- The Git LFS original v1 API is unsupported.
-- Git LFS requests use HTTPS credentials, which means you should use a good Git
-  [credentials store](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage).
-- [Group wikis](../../../user/project/wiki/group.md) do not support Git LFS.
-
 ## Configure Git LFS for a project
 
 DETAILS:
@@ -306,6 +299,12 @@ see [Delete sensitive information from commits](../undo.md#delete-sensitive-info
 WARNING:
 Expunging file history requires rewriting Git history. This action is destructive and irreversible.
 
+## Reduce repository size after removing large files
+
+If you need to remove large files from your repository's history, to reduce
+the total size of your repository, see
+[Reduce repository size](../../../user/project/repository/reducing_the_repo_size_using_git.md).
+
 ## Related topics
 
 - Use Git LFS to set up [exclusive file locks](../../../user/project/file_lock.md#exclusive-file-locks).
@@ -314,11 +313,3 @@ Expunging file history requires rewriting Git history. This action is destructiv
 - [GitLab Git Large File Storage (LFS) Administration](../../../administration/lfs/index.md) for self-managed instances
 - [Troubleshooting Git LFS](troubleshooting.md)
 - [The `.gitattributes` file](../../../user/project/git_attributes.md)
-
-## Troubleshooting
-
-### Reduce repository size after removing large files
-
-If you need to remove large files from your repository's history, to reduce
-the total size of your repository, see
-[Reduce repository size](../../../user/project/repository/reducing_the_repo_size_using_git.md).

doc/topics/git/lfs/troubleshooting.md

@@ -8,6 +8,11 @@ info: "To determine the technical writer assigned to the Stage/Group associated
 
 When working with Git LFS, you might encounter the following issues.
 
+- The Git LFS original v1 API is unsupported.
+- Git LFS requests use HTTPS credentials, which means you should use a Git
+  [credentials store](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage).
+- [Group wikis](../../../user/project/wiki/group.md) do not support Git LFS.
+
 ## Error: repository or object not found
 
 This error can occur for a few reasons, including: