Merge pull request #39 from Chris2Brooks/patch-1

Fixed deadlink inside Using GraphQL Api

Author: Swizec

src/pages/serverless-graphql/index.mdx

@@ -321,7 +321,7 @@ Should you rip out your REST API and rewrite for GraphQL? Please don't.
 
 GraphQL doesn't care where data comes from. Relational database, NoSQL database, files, a REST API, another GraphQL API ... All you need is a function that reads data in response to a query.
 
-You can [start using GraphQL without changing your existing server](https://swizec.com/blog/how-you-can-start-using-graphql-today-without-changing-the-backend/swizec/9350) with a GraphQL middle layer. Create a GraphQL server on top of your REST API.
+You can [start using GraphQL without changing your existing server](https://swizec.com/blog/how-you-can-start-using-graphql-today-without-changing-the-backend/) with a GraphQL middle layer. Create a GraphQL server on top of your REST API.
 
 ![](giphy:wow)
 
@@ -661,4 +661,4 @@ Various no-code and low-code solutions exist that do the work for you. Look at y
 
 They tend to exhibit the *expose entire DB as API* problem. But they can be a good starting point.
 
-Next chapter we look at building lambda pipelines for distributed data processing.
+Next chapter we look at building lambda pipelines for distributed data processing.