fix(docs): correct typos and grammar in ORM and Studio docs

apps/docs/content/docs/orm/more/comparisons/prisma-and-sequelize.mdx

@@ -16,7 +16,7 @@ While Prisma ORM and Sequelize solve similar problems, they work in very differe
 
 **Prisma ORM** is a new kind of ORM that mitigates many problems of traditional ORMs, such as bloated model instances, mixing business with storage logic, lack of type-safety or unpredictable queries caused e.g. by lazy loading.
 
-It uses the [Prisma schema](/orm/prisma-schema/overview) to define application models in a declarative way. Prisma Migrate then allows to generate SQL migrations from the Prisma schema and executes them against the database. CRUD queries are provided by Prisma Client, a lightweight and entirely type-safe database client for Node.js and TypeScript.
+It uses the [Prisma schema](/orm/prisma-schema/overview) to define application models in a declarative way. Prisma Migrate then allows you to generate SQL migrations from the Prisma schema and execute them against the database. CRUD queries are provided by Prisma Client, a lightweight and entirely type-safe database client for Node.js and TypeScript.
 
 ## API comparison
 

apps/docs/content/docs/orm/more/comparisons/prisma-and-typeorm.mdx

@@ -16,7 +16,7 @@ While Prisma ORM and TypeORM solve similar problems, they work in very different
 
 **Prisma ORM** is a new kind of ORM that mitigates many problems of traditional ORMs, such as bloated model instances, mixing business with storage logic, lack of type-safety or unpredictable queries caused e.g. by lazy loading.
 
-It uses the [Prisma schema](/orm/prisma-schema/overview) to define application models in a declarative way. Prisma Migrate then allows to generate SQL migrations from the Prisma schema and executes them against the database. CRUD queries are provided by Prisma Client, a lightweight and entirely type-safe database client for Node.js and TypeScript.
+It uses the [Prisma schema](/orm/prisma-schema/overview) to define application models in a declarative way. Prisma Migrate then allows you to generate SQL migrations from the Prisma schema and execute them against the database. CRUD queries are provided by Prisma Client, a lightweight and entirely type-safe database client for Node.js and TypeScript.
 
 ## API design & Level of abstraction
 
@@ -297,7 +297,7 @@ This section explains the differences in type safety when loading relations of a
 
 #### TypeORM
 
-TypeORM allows to eagerly load relations from the database via the `relations` option that can be passed to its [`find`](https://typeorm.io/find-options) methods.
+TypeORM allows you to eagerly load relations from the database via the `relations` option that can be passed to its [`find`](https://typeorm.io/find-options) methods.
 
 Consider this example:
 
@@ -427,9 +427,9 @@ This section explains the differences in type safety when filtering a list of re
 
 #### TypeORM
 
-TypeORM allows to pass a `where` option to its [`find`](https://typeorm.io/find-options) methods to filter the list of returned records according to specific criteria. These criteria can be defined with respect to a model's properties.
+TypeORM allows you to pass a `where` option to its [`find`](https://typeorm.io/find-options) methods to filter the list of returned records according to specific criteria. These criteria can be defined with respect to a model's properties.
 
-##### Loosing type-safety using operators
+##### Losing type-safety using operators
 
 Consider this example:
 

apps/docs/content/docs/orm/prisma-migrate/workflows/baselining.mdx

@@ -42,7 +42,7 @@ However, when you `prisma migrate deploy` your migrations to databases that alre
 
 The target database already contains the tables and columns created by the initial migration, and attempting to create these elements again will most likely result in an error.
 
-![A migration history represented by three migration files (file icon and name), surrounded by a a box labelled 'migration history'. The first migration is marked 'do not apply', and the second two migrations are marked 'apply'. An arrow labelled with the command 'prisma migrate deploy' points from the migration history to a database labelled 'production'.](/img/orm/prisma-migrate/workflows/deploy-db.png)
+![A migration history represented by three migration files (file icon and name), surrounded by a box labelled 'migration history'. The first migration is marked 'do not apply', and the second two migrations are marked 'apply'. An arrow labelled with the command 'prisma migrate deploy' points from the migration history to a database labelled 'production'.](/img/orm/prisma-migrate/workflows/deploy-db.png)
 
 Baselining solves this problem by telling Prisma Migrate to pretend that the initial migration(s) **have already been applied**.
 

apps/docs/content/docs/studio/integrations/embedding.mdx

@@ -20,7 +20,7 @@ If you want to see what embedded Studio looks like, **[check out the demo](https
 
 You can embed Prisma Studio in your own app in various scenarios:
 
-- Create an quick admin dashboard for editing data
+- Create a quick admin dashboard for editing data
 - Multi-tenant application where every user has their own DB
 - Provide an easy way to view and edit data to your users