Apply 2 suggestion(s) to 1 file(s)

doc/security/rate_limits.md

@@ -70,22 +70,20 @@ For configuration information, see
 ## Non-configurable limits
-### Git operations via Shell (SSH)
+### Git operations using SSH
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78373) in GitLab 14.7.
-GitLab Shell performs rate-limiting by user account and project for Git operations. 
-GitLab Shell accepts `git` operation requests and then makes a call to the 
-Rails rate-limiter (backed by Redis).
-If the `user + project` exceeds the rate limit, GitLab Shell drops further
-connection requests for that `user + project`.
-The rate-limiter is applied at the Git command ([plumbing](https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain)) level. 
-Each command has a rate limit of 600/minute. For example, 
-`git push` has 600/minute and `git pull` has another 600/minute.
-As the same commands are shared by `git-upload-pack`, `git pull` and `git clone`,
-they're in effect the same command for the purposes of rate-limiting.
+GitLab rate limits Git operations by user account and project. If a request from a user for a Git operation
+on a project exceeds the rate limit, GitLab drops further connection requests from that user for the project.
+The rate limit applies at the Git command ([plumbing](https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain)) level. 
+Each command has a rate limit of 600 per minute. For example:
+- `git push` has a rate limit of 600 per minute.
+- `git pull` has its own rate limit of 600 per minute.
+
+Because the same commands are shared by `git-upload-pack`, `git pull`, and `git clone`, they are they share a rate limit.
 ### Repository archives