1 files changed, 16 insertions, 17 deletions
diff --git a/doc/update/6.2-to-6.3.md b/doc/update/6.2-to-6.3.md
index 7f916047369..dfe2e551b36 100644
--- a/doc/update/6.2-to-6.3.md
+++ b/doc/update/6.2-to-6.3.md
@@ -1,22 +1,21 @@
 # From 6.2 to 6.3
 
-## Requires version: 6.1 or 6.2
+**Requires version: 6.1 or 6.2.**
 
-### 0. Backup
+## 0. Backup
 
-It's useful to make a backup just in case things go south:
-(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
+It's useful to make a backup just in case things go south: (With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
 
 ```bash
 cd /home/git/gitlab
 sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
 ```
 
-### 1. Stop server
+## 1. Stop server
 
     sudo service gitlab stop
 
-### 2. Get latest code
+## 2. Get latest code
 
 ```bash
 cd /home/git/gitlab
@@ -25,7 +24,7 @@ sudo -u git -H git checkout 6-3-stable
 # For GitLab Enterprise Edition: sudo -u git -H git checkout 6-3-stable-ee
 ```
 
-### 3. Update gitlab-shell (and its config)
+## 3. Update gitlab-shell (and its config)
 
 ```bash
 cd /home/git/gitlab-shell
@@ -33,9 +32,9 @@ sudo -u git -H git fetch
 sudo -u git -H git checkout v1.7.9 # Addresses multiple critical security vulnerabilities
 ```
 
-The Gitlab-shell config changed recently, so check for config file changes and make `/home/git/gitlab-shell/config.yml` the same as https://github.com/gitlabhq/gitlab-shell/blob/master/config.yml.example
+The Gitlab-shell config changed recently, so check for config file changes and make `/home/git/gitlab-shell/config.yml` the same as <https://github.com/gitlabhq/gitlab-shell/blob/master/config.yml.example>
 
-### 4. Install libs, migrations, etc.
+## 4. Install libs, migrations, etc.
 
 ```bash
 cd /home/git/gitlab
@@ -54,7 +53,7 @@ sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
 sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
 ```
 
-### 5. Update config files
+## 5. Update config files
 
 TIP: to see what changed in gitlab.yml.example in this release use next command: 
 
@@ -62,8 +61,8 @@ TIP: to see what changed in gitlab.yml.example in this release use next command:
 git diff 6-2-stable:config/gitlab.yml.example 6-3-stable:config/gitlab.yml.example
 ```
 
-* Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-3-stable/config/gitlab.yml.example but with your settings.
-* Make `/home/git/gitlab/config/unicorn.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-3-stable/config/unicorn.rb.example but with your settings.
+- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-3-stable/config/gitlab.yml.example but with your settings.
+- Make `/home/git/gitlab/config/unicorn.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-3-stable/config/unicorn.rb.example but with your settings.
 
 ```bash
 # Copy rack attack middleware config
@@ -71,19 +70,19 @@ cd /home/git/gitlab
 sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
 ```
 
-### 6. Update Init script
+## 6. Update Init script
 
 ```bash
 sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
 sudo chmod +x /etc/init.d/gitlab
 ```
 
-### 7. Start application
+## 7. Start application
 
     sudo service gitlab start
     sudo service nginx restart
 
-### 8. Check application status
+## 8. Check application status
 
 Check if GitLab and its environment are configured correctly:
 
@@ -98,8 +97,8 @@ If all items are green, then congratulations upgrade complete!
 ## Things went south? Revert to previous version (6.2)
 
 ### 1. Revert the code to the previous version
-Follow the [`upgrade guide from 6.1 to 6.2`](6.1-to-6.2.md), except for the database migration 
-(The backup is already migrated to the previous version)
+
+Follow the [`upgrade guide from 6.1 to 6.2`](6.1-to-6.2.md), except for the database migration (the backup is already migrated to the previous version).
 
 ### 2. Restore from the backup: