From d9c11a5f243d9410f0e0afe7bfc7ac7dd5319ed8 Mon Sep 17 00:00:00 2001
From: ryanb-ifit <77697275+ryanb-ifit@users.noreply.github.com>
Date: Thu, 25 Mar 2021 01:35:49 -0500
Subject: [PATCH] Update 100-data-modeling.mdx (#1485)

---
 .../050-overview/100-what-is-prisma/100-data-modeling.mdx       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/200-concepts/050-overview/100-what-is-prisma/100-data-modeling.mdx b/content/200-concepts/050-overview/100-what-is-prisma/100-data-modeling.mdx
index b26ee8724c..e6028ad2bc 100644
--- a/content/200-concepts/050-overview/100-what-is-prisma/100-data-modeling.mdx
+++ b/content/200-concepts/050-overview/100-what-is-prisma/100-data-modeling.mdx
@@ -159,7 +159,7 @@ Depending on which parts of Prisma you want to use in your application, the data
 No matter which approach though, with Prisma you never create application models in your programming language by manually defining classes, interfaces, or structs. Instead, the application models are defined in your [Prisma schema](../../components/prisma-schema):
 
 - **Only Prisma Client**: Application models in the Prisma schema are _generated based on the introspection of your database schema_. Data modeling happens primarily on the database-level.
-- **Prisma Client and Prisma Migrate)**: Data modeling happens in the Prisma schema by _manually adding application models_ to it. Prisma Migrate maps these application models to tables in the underlying database.
+- **Prisma Client and Prisma Migrate**: Data modeling happens in the Prisma schema by _manually adding application models_ to it. Prisma Migrate maps these application models to tables in the underlying database.
 
 As an example, the `User` model from the previous example would be represented as follows in the Prisma schema: