README.md in capture_migration_sql-1.0.3 vs README.md in capture_migration_sql-1.0.4

@@ -1,8 +1,10 @@
-# CaptureMigrationSql
+# Capture Migration SQL
 
 [![Continuous Integration](https://github.com/bdurand/capture_migration_sql/actions/workflows/continuous_integration.yml/badge.svg)](https://github.com/bdurand/capture_migration_sql/actions/workflows/continuous_integration.yml)
+[![Regression Test](https://github.com/bdurand/capture_migration_sql/actions/workflows/regression_test.yml/badge.svg)](https://github.com/bdurand/capture_migration_sql/actions/workflows/regression_test.yml)
 [![Ruby Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://github.com/testdouble/standard)
+[![Gem Version](https://badge.fury.io/rb/capture_migration_sql.svg)](https://badge.fury.io/rb/capture_migration_sql)
 
 This gem adds the ability to capture and persist the SQL statements executed by migrations. There are a couple of reasons why you may want to do this.
 
 1. Having a list of SQL changes in a migration can allow a more thorough review of database changes during a code review. The Ruby schema directives in Rails are nice for simple tables and for documentation purposes, but if you need to tune your database for performance or data integrity, seeing the raw SQL can give you a better idea of exactly what each change involves.