From a0c3cc3dc2734358a6009123050b0d2e165e9195 Mon Sep 17 00:00:00 2001
From: Yudai Takada <t.yudai92@gmail.com>
Date: Tue, 26 Mar 2024 11:08:36 +0900
Subject: [PATCH] Fix a typo (#259)

s/Contraint/Constraint/
---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index e961efb..687793c 100644
--- a/README.md
+++ b/README.md
@@ -506,7 +506,7 @@ end
 In Postgres, adding a unique constraint creates a unique index, which blocks reads and writes.
 
 ```ruby
-class AddUniqueContraint < ActiveRecord::Migration[7.1]
+class AddUniqueConstraint < ActiveRecord::Migration[7.1]
   def change
     add_unique_constraint :users, :some_column
   end
@@ -518,7 +518,7 @@ end
 Create a unique index concurrently, then use it for the constraint.
 
 ```ruby
-class AddUniqueContraint < ActiveRecord::Migration[7.1]
+class AddUniqueConstraint < ActiveRecord::Migration[7.1]
   disable_ddl_transaction!
 
   def up
@@ -539,7 +539,7 @@ end
 In Postgres, adding an exclusion constraint blocks reads and writes while every row is checked.
 
 ```ruby
-class AddExclusionContraint < ActiveRecord::Migration[7.1]
+class AddExclusionConstraint < ActiveRecord::Migration[7.1]
   def change
     add_exclusion_constraint :users, "number WITH =", using: :gist
   end