diff --git a/doc/settings/configuration.md b/doc/settings/configuration.md
index cef0a3d5cb6d3aa3637b5bbd8d728fe80092b5e5_ZG9jL3NldHRpbmdzL2NvbmZpZ3VyYXRpb24ubWQ=..8cc4b4cf672843781a5dc239753193be532fb135_ZG9jL3NldHRpbmdzL2NvbmZpZ3VyYXRpb24ubWQ= 100644
--- a/doc/settings/configuration.md
+++ b/doc/settings/configuration.md
@@ -427,7 +427,7 @@
 
 ## Configuring Rack Attack
 
-To prevent abusive clients doing damage GitLab uses rack-attack gem.
-Check [this page](https://gitlab.com/help/security/rack_attack.md)
+To prevent abusive clients doing damage, GitLab uses the Rack Attack gem.
+Check [this page](https://docs.gitlab.com/ee/security/rack_attack.html)
 for more information.
 
@@ -432,8 +432,5 @@
 for more information.
 
-File `config/initializers/rack_attack.rb` is managed by omnibus-gitlab
-and must be configured in `/etc/gitlab/gitlab.rb`.
-
 ## Disabling automatic cache cleaning during installation
 
 If you have large gitlab installation, you might not want to run `rake cache:clean` task.