fix build

Author: dphuang2

blog/2023-08-10-graphql-vs-rest/graphql-vs-rest.mdx

@@ -282,7 +282,7 @@ generation stands out as a prominent feature among most GraphQL technology
 stacks. This significantly benefits developers by reducing the amount of
 boilerplate code they need to write. The ability to generate code from "front to
 back" is a game-changer for rapid development. While the REST ecosystem is
-progressing, it took a back seat for many years until [OpenAPI](/blog/openapi)
+progressing, it took a back seat for many years until OpenAPI
 emerged.
 
 Whether in small or large-scale software systems, GraphQL addresses a crucial
@@ -465,8 +465,8 @@ examples and always leaned towards DX. After reading 1,000s of perspectives, I
 am convinced that you should start with REST to avoid the complications of
 GraphQL. If you are lucky enough to be making technical decisions at "unicorn
 scale", I would consider looking at GraphQL to optimize the query interface.
-Meanwhile, take advantage of the [growing OpenAPI
-ecosystem](/blog/openapi#openapi-tools-and-ecosystem).
+Meanwhile, take advantage of the growing OpenAPI
+ecosystem.
 
 In most cases, for GraphQL to effectively address the problems it was originally
 designed to solve, a team should ideally possess a considerable number of