rubocop -a

README.md

@@ -13,10 +13,10 @@ Tested with:
 
 ## Usage
 Add a gem to your Gemfile:
-`gem 'activesupport-cache-database'`
+```gem 'activesupport-cache-database'```
 
 Generate a migration file to create required table:
-`rails generate cache:database:install`
+```rails generate cache:database:install```
 
 Make sure to read through migration file, before running a migration. You might want to tweak it to fit your usecase.
 

lib/generators/cache/database/install_generator.rb

@@ -1,21 +1,21 @@
-require "rails/generators/active_record"
+require 'rails/generators/active_record'
 
 module Cache
   module Database
     module Generators
       class InstallGenerator < Rails::Generators::Base
         include ActiveRecord::Generators::Migration
 
-        source_root File.join(__dir__, "templates")
-        desc "Add migration for ActiveSupport::Cache::Database"
+        source_root File.join(__dir__, 'templates')
+        desc 'Add migration for ActiveSupport::Cache::Database'
 
         def self.next_migration_number(path)
           next_migration_number = current_migration_number(path) + 1
           ActiveRecord::Migration.next_migration_number(next_migration_number)
         end
 
         def copy_migrations
-          migration_template "create_table_for_cache.rb", "db/migrate/create_cache_database.rb"
+          migration_template 'create_table_for_cache.rb', 'db/migrate/create_cache_database.rb'
         end
       end
     end

lib/generators/cache/database/templates/create_table_for_cache.rb

@@ -1,4 +1,4 @@
-class Migration < ::ActiveRecord::Migration[5.2]
+class Migration < ActiveRecord::Migration[5.2]
   def change
     create_table :activesupport_cache_entries, primary_key: 'key', id: :binary, limit: 255 do |t|
       t.binary :value, null: false
@@ -17,7 +17,9 @@ def change
       add_index :activesupport_cache_entries, :version, where: 'version IS NOT NULL'
     end
 
-    # In case, your using Postgres you might wanto to turn table to unlogged tables. This comes with 50% write performance improvement, but comes with multiple downsides you need to be aware off:
+    # if your using Postgres you might want to turn cache table into unlogged tables.
+    # This comes with 50% write performance improvement, but comes with multiple
+    # downsides you need to be aware off:
     # - No validation, data will be lost in case of forced restart.
     # - No replication to read replicas
     #