Update docs to markdown style guide.

3 files changed, 17 insertions, 10 deletions

diff --git a/doc/security/README.md b/doc/security/README.md
index f8dd1291b9b..b89e8cbe020 100644
--- a/doc/security/README.md
+++ b/doc/security/README.md
@@ -1,2 +1,4 @@
-+ [Password length limits](password_length_limits.md)
-+ [Rack attack](rack_attack.md)
+# Security
+
+- [Password length limits](password_length_limits.md)
+- [Rack attack](rack_attack.md)
diff --git a/doc/security/password_length_limits.md b/doc/security/password_length_limits.md
index c8d66e9636c..d21b26a43e8 100644
--- a/doc/security/password_length_limits.md
+++ b/doc/security/password_length_limits.md
@@ -1,6 +1,7 @@
 # Custom password length limits
 
 If you want to enforce longer user passwords you can create an extra Devise initializer with the steps below.
+
 If you do not use the `devise_password_length.rb` initializer the password length is set to a minimum of 8 characters in `config/initializers/devise.rb`.
 
 ```bash
diff --git a/doc/security/rack_attack.md b/doc/security/rack_attack.md
index 9e863bbd190..92066997be8 100644
--- a/doc/security/rack_attack.md
+++ b/doc/security/rack_attack.md
@@ -1,18 +1,22 @@
 # Rack attack
 
 To prevent abusive clients doing damage GitLab uses rack-attack gem.
+
 If you installed or upgraded GitLab by following the official guides this should be enabled by default.
+
 If you are missing `config/initializers/rack_attack.rb` the following steps need to be taken in order to enable protection for your GitLab instance:
 
-1. In config/application.rb find and uncomment the following line:
-  config.middleware.use Rack::Attack
-2. Rename config/initializers/rack_attack.rb.example to config/initializers/rack_attack.rb
-3. Review the paths_to_be_protected and add any other path you need protecting
-4. Restart GitLab instance
+1.  In config/application.rb find and uncomment the following line:
+
+        config.middleware.use Rack::Attack
+
+1.  Rename `config/initializers/rack_attack.rb.example` to `config/initializers/rack_attack.rb`.
+
+1.  Review the `paths_to_be_protected` and add any other path you need protecting.
+
+1.  Restart GitLab instance.
 
-By default, user sign-in, user sign-up(if enabled) and user password reset is limited to 6 requests per minute.
-After trying for 6 times, client will have to wait for the next minute to be able to try again.
-These settings can be found in `config/initializers/rack_attack.rb`
+By default, user sign-in, user sign-up(if enabled) and user password reset is limited to 6 requests per minute. After trying for 6 times, client will have to wait for the next minute to be able to try again. These settings can be found in `config/initializers/rack_attack.rb`
 
 If you want more restrictive/relaxed throttle rule change the `limit` or `period` values. For example, more relaxed throttle rule will be if you set limit: 3 and period: 1.second(this will allow 3 requests per second). You can also add other paths to the protected list by adding to `paths_to_be_protected` variable. If you change any of these settings do not forget to restart your GitLab instance.