Merge pull request #494 from Naresh-Khatri/main

fix: typo "suites" to "suits"

Author: AlexBlokh

src/content/docs/kit-overview.mdx

@@ -23,7 +23,7 @@ import Prerequisites from "@mdx/Prerequisites.astro"
   drizzle-kit
 </Npm>
 <Callout type="warning">
-Make sure to first go through Drizzle [get started](/docs/get-started) and [migration foundamentals](/docs/migrations) and pick SQL migration flow that suites your business needs best. 
+Make sure to first go through Drizzle [get started](/docs/get-started) and [migration foundamentals](/docs/migrations) and pick SQL migration flow that suits your business needs best. 
 </Callout>
 
 Based on your schema, Drizzle Kit let's you generate and run SQL migration files, 

src/content/docs/migrations.mdx

@@ -20,7 +20,7 @@ SQL databases require you to specify a **strict schema** of entities you're goin
 and if (when) you need to change the shape of those entities - you will need to do it via **schema migrations**.
 
 There're multiple production grade ways of managing database migrations. 
-Drizzle is designed to perfectly suite all of them, regardless of you going **database first** or **codebase first**.
+Drizzle is designed to perfectly suits all of them, regardless of you going **database first** or **codebase first**.
 
 **Database first** is when your database schema is a source of truth. You manage your database schema either directly on the database or 
 via database migration tools and then you pull your database schema to your codebase application level entities.