README.md in strong_migrations-0.7.0 vs README.md in strong_migrations-0.7.1

@@ -43,11 +43,11 @@
 
 Deploy the code, then wrap this step in a safety_assured { ... } block.
 
 class RemoveColumn < ActiveRecord::Migration[6.0]
   def change
-    safety_assured { remove_column :users, :name, :string }
+    safety_assured { remove_column :users, :name }
   end
 end
 ```
 
 An operation is classified as dangerous if it either:
@@ -609,11 +609,11 @@
 StrongMigrations.disable_check(:add_index)
 ```
 
 Check the [source code](https://github.com/ankane/strong_migrations/blob/master/lib/strong_migrations.rb) for the list of keys.
 
-## Down Migrations / Rollbacks [unreleased]
+## Down Migrations / Rollbacks
 
 By default, checks are disabled when migrating down. Enable them with:
 
 ```ruby
 StrongMigrations.check_down = true
@@ -705,13 +705,13 @@
 ## Target Version
 
 If your development database version is different from production, you can specify the production version so the right checks run in development.
 
 ```ruby
-StrongMigrations.target_postgresql_version = "10"
-StrongMigrations.target_mysql_version = "8.0.12"
-StrongMigrations.target_mariadb_version = "10.3.2"
+StrongMigrations.target_version = 10 # or "8.0.12", "10.3.2", etc
 ```
+
+The major version works well for Postgres, while the full version is recommended for MySQL and MariaDB.
 
 For safety, this option only affects development and test environments. In other environments, the actual server version is always used.
 
 ## Analyze Tables