README.md in schema_plus-1.3.1 vs README.md in schema_plus-1.3.2

@@ -41,11 +41,11 @@
 
     gem "schema_plus"
 
 ## Features
 
-Here some examples that show off the high points.  For full details see the
+This README lists the major features, with examples of use.  For full details see the
 [RDoc documentation](http://rubydoc.info/gems/schema_plus).
 
 ### Indexes
 
 With standard Rails 3 migrations, you specify indexes separately from the
@@ -101,18 +101,18 @@
     t.string :last_name,  index: { conditions: 'deleted_at IS NULL' }
     t.string :last_name,  index: { expression: 'upper(last_name)' }
     t.string :last_name,  index: { kind: 'hash' }
     t.string :last_name,  index: { case_sensitive: false }        # shorthand for expression: 'lower(last_name)'
 
-These features are available also in ActiveRecord::Migration.add_index.  See
-doc at SchemaPlus::ActiveRecord::ConnectionAdapters::PostgresqlAdapter and
-SchemaPlus::ActiveRecord::ConnectionAdapters::IndexDefinition
+These features are available also in `ActiveRecord::Migration.add_index`.  See
+doc for [SchemaPlus::ActiveRecord::ConnectionAdapters::PostgresqlAdapter](http://rubydoc.info/gems/schema_plus/SchemaPlus/ActiveRecord/ConnectionAdapters/PostgresqlAdapter) and
+[SchemaPlus::ActiveRecord::ConnectionAdapters::IndexDefinition](http://rubydoc.info/gems/schema_plus/SchemaPlus/ActiveRecord/ConnectionAdapters/IndexDefinition)
 
 When you query column information using ActiveRecord::Base#columns, SchemaPlus
 analogously provides index information relevant to each column: which indexes
-reference the column, whether the column must be unique, etc.  See doc at
-SchemaPlus::ActiveRecord::ConnectionAdapters::Column
+reference the column, whether the column must be unique, etc.  See doc for
+[SchemaPlus::ActiveRecord::ConnectionAdapters::Column](http://rubydoc.info/gems/schema_plus/SchemaPlus/ActiveRecord/ConnectionAdapters/Column).
 
 SchemaPlus also tidies some index-related behavior:
 
 *   Rails' various db adapters have inconsistent behavior regarding an attempt
     to create a duplicate index: some quietly ignore the attempt, some raise
@@ -173,12 +173,12 @@
 (see create_table).
 
 To examine your foreign key constraints, `connection.foreign_keys` returns a
 list of foreign key constraints defined for a given table, and
 `connection.reverse_foreign_keys` returns a list of foreign key constraints
-that reference a given table.  See
-SchemaPlus::ActiveRecord::ConnectionAdapters::ForeignKeyDefinition.
+that reference a given table.  See doc at
+[SchemaPlus::ActiveRecord::ConnectionAdapters::ForeignKeyDefinition](http://rubydoc.info/gems/schema_plus/SchemaPlus/ActiveRecord/ConnectionAdapters/ForeignKeyDefinition).
 
 #### Foreign Key Issues
 
 Foreign keys can cause issues for Rails utilities that delete or load data
 because referential integrity imposes a sequencing requirement that those
@@ -296,10 +296,15 @@
 
 ## Release notes:
 
 ### Master branch (to be released)
 
-* (nothing new yet)
+* *nothing currently waiting to be released*
+
+### 1.3.2
+
+* Bug fix, remove_index with if_exists but no name
+* Sort indexes alphabetically when dumping, like rails does
 
 ### 1.3.1
 
 * Regression bug fix, non-option arguemnts to remove_index