From b5ce0542faa97b93ca7548ed91d3729fe8d9b1b7 Mon Sep 17 00:00:00 2001
From: Brian Spendolini <69256666+JetterMcTedder@users.noreply.github.com>
Date: Thu, 19 Jan 2023 10:06:35 -1000
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c73f760..51aae2e 100644
--- a/README.md
+++ b/README.md
@@ -142,7 +142,7 @@ you can get your public IP from here, for example: https://ifconfig.me/
 
 ## Deploy the database
 
-There are two may strategies that can be used: imperative and declarative. The imperative approach is the one that has been used until now, where the script to create the database objects are applied in the defined order. The declarative approach is instead where you have the database state (a snapshot of the schema) you want to have and a tool will take care of making all the correct changes to bring the target database to that state.
+There are two main strategies that can be used: imperative and declarative. The imperative approach is the one that has been used until now, where the script to create the database objects are applied in the defined order. The declarative approach is instead where you have the database state (a snapshot of the schema) you want to have and a tool will take care of making all the correct changes to bring the target database to that state.
 
 In both cases the first step is to have at hand the connection string needed to connect to create Azure SQL database. Depending on your deployment strategy preference, switch to the `./database/declarative-deploy` or `./database/imperative-deploy` folder and create new `.env` file, that will contain the aforementioned connection string. Use the provided `.env.template` as a guide. The connection string look like: