diff --git a/README.md b/README.md
index 65d7243..e291353 100644
--- a/README.md
+++ b/README.md
@@ -98,13 +98,7 @@ To configure with bitbucket you will need to create a new [app password](https:/
 ## Known issues
 
 - When cloning if you see something like `Username for 'https://gitlab.com': ` the command won't finish. I haven't been able to identify the reason for this occuring. The fix for this is to make sure your token is in the osxkeychain. See the troubleshooting section for how to set this up.
-
-## Troubleshooting
-
-- If the `security` command does not return your token, follow this [GitHub Documentation](https://help.github.com/en/articles/caching-your-github-password-in-git). For GitHub tokens you will need to set your token as your username and set nothing as the password when prompted. For GitLab you will need to set your token for both the username and password when prompted. This will correctly store your credentials in the keychain. If you are still having problems see this [StackOverflow Post](https://stackoverflow.com/questions/31305945/git-clone-from-github-over-https-with-two-factor-authentication)
-- If your GitHub account is behind 2fa follow this [Github Documentation](https://github.blog/2013-09-03-two-factor-authentication/#how-does-it-work-for-command-line-git)
-- Make sure your `$ git --version` is >= 2.19.0
-- You see (Error: open /dev/null: too many open files) you need to increase your ulimits, there are lots of docs online for this. For mac the quick and dirty is below
+- If you are cloning a large org you may see `Error: open /dev/null: too many open files` which means you need to increase your ulimits, there are lots of docs online for this. For mac the quick and dirty is below
 
   ```
   # reset the soft and hard file limit boundaries
@@ -114,5 +108,11 @@ To configure with bitbucket you will need to create a new [app password](https:/
   $ ulimit -n 20000
   ```
 
+## Troubleshooting
+
+- If the `security` command does not return your token, follow this [GitHub Documentation](https://help.github.com/en/articles/caching-your-github-password-in-git). For GitHub tokens you will need to set your token as your username and set nothing as the password when prompted. For GitLab you will need to set your token for both the username and password when prompted. This will correctly store your credentials in the keychain. If you are still having problems see this [StackOverflow Post](https://stackoverflow.com/questions/31305945/git-clone-from-github-over-https-with-two-factor-authentication)
+- If your GitHub account is behind 2fa follow this [Github Documentation](https://github.blog/2013-09-03-two-factor-authentication/#how-does-it-work-for-command-line-git)
+- Make sure your `$ git --version` is >= 2.19.0
+
 ### Updating brew tap
 - [See Readme](https://github.com/gabrie30/homebrew-utils/blob/master/README.md)