summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Kozono <mkozono@gmail.com>2019-07-30 00:57:25 +0000
committerMichael Kozono <mkozono@gmail.com>2019-07-30 00:57:25 +0000
commitab75e3184e0290c8d15ac9ca989cf7354a040ba1 (patch)
treea890463b5b0418131f5b652abbd950a818c43828
parent405475d1a3ad820bb3ec305ffacd5c72f91b6d26 (diff)
downloadgitlab-ce-ab75e3184e0290c8d15ac9ca989cf7354a040ba1.tar.gz
Apply suggestion to doc/security/rate_limits.md
-rw-r--r--doc/security/rate_limits.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/security/rate_limits.md b/doc/security/rate_limits.md
index 3c18bdf3ed2..0ab831939e8 100644
--- a/doc/security/rate_limits.md
+++ b/doc/security/rate_limits.md
@@ -15,7 +15,7 @@ For example, a simple script can make thousands of web requests per second.
Whether malicious, apathetic, or just a bug, your application and infrastructure
may not be able to cope with the load (see
[Denial-of-service attack](https://en.wikipedia.org/wiki/Denial-of-service_attack)).
-Most cases can be mitigated by limiting the rate of requests from a single IP.
+Most cases can be mitigated by limiting the rate of requests from a single IP address.
Most [brute-force attacks](https://en.wikipedia.org/wiki/Brute-force_attack) are
similarly mitigated by a rate limit.