diff --git a/content/200-orm/800-more/400-comparisons/01-prisma-and-typeorm.mdx b/content/200-orm/800-more/400-comparisons/01-prisma-and-typeorm.mdx
index 69f85eeee1..d8405c0194 100644
--- a/content/200-orm/800-more/400-comparisons/01-prisma-and-typeorm.mdx
+++ b/content/200-orm/800-more/400-comparisons/01-prisma-and-typeorm.mdx
@@ -22,7 +22,7 @@ It uses the [Prisma schema](/orm/prisma-schema) to define application models in
 
 ## API design & Level of abstraction
 
-TypeORM and Prisma operate on different levels of abstraction. TypeORM is closer to mirroring SQL in its API while Prisma Client provides a higher-level abstraction that was carefully designed with the common tasks of application developers in mind. Prisma's API design heavily leans on the idea of [making the right thing easy](https://www.jason.af/right-thing-easy-thing/).
+TypeORM and Prisma operate on different levels of abstraction. TypeORM is closer to mirroring SQL in its API while Prisma Client provides a higher-level abstraction that was carefully designed with the common tasks of application developers in mind. Prisma's API design heavily leans on the idea of [making the right thing easy](https://jason.energy/right-thing-easy-thing/).
 
 While Prisma Client operates on a higher-level of abstraction, it strives to expose the full power of the underlying database and lets you drop down to [raw SQL](/orm/prisma-client/queries/raw-database-access/raw-queries) at any time if your use case requires it.