(DOCS): Edit Database migration (RocketChat#1450)

* (DOCS): Edit Database migration

* Edit header

Author: paulofariadias

administrator-guides/database-migration/README.md

@@ -6,9 +6,9 @@ The action of updating an older schema to a newer one (or vice versa) is called
 
 When you incrementally update Rocket.Chat versions, database migration is automatic and you do not have to take any explicit action.
 
-However, from time to time, you may have need to skip multiple versions in your Rocket.Chat upgrades.
+However, from time to time, you may need to skip multiple versions in your Rocket.Chat upgrades.
 
-Database migration may fail in these scenarios.
+Database migration may fail in a scenario like this.
 
 A typical failure message is similar to:
 
@@ -21,9 +21,9 @@ A typical failure message is similar to:
 |                      Database target version: 58                     |
 ```
 
-As an example, the above migration is locked and stuck on 18.  We need a target of 19 before migration to 58.
+As an example, the migration above is locked and stuck on 18.  We need a target of 19 before migrating to 58.
 
-One way to force migration is to manually unlock the migration in mongo and also increase database version to the target version (19).
+One way to force this migration is to manually unlock the migration in Mongo and also increase the database version to the target version (19).
 
 ```js
 use rocketchat
@@ -32,6 +32,4 @@ db.migrations.update({_id: 'control'},{$set:{locked:false,version:19}})
 
 Restart Rocket.Chat and the migration should succeed now to the latest version.
 
-Note that certain new values that are vital to Rocket.Chat operations may remain unpopulated when you skip versions.
-
-For example, you may have to manually apply roles to users.
+**Note**: certain new values that are vital to Rocket.Chat operations may remain unpopulated when you skip versions. For example, you may have to manually apply roles to users.