Merge pull request github#15256 from imwiss/patch-2

Updated wording around GraphQL vs REST

content/graphql/overview/about-the-graphql-api.md

@@ -12,7 +12,7 @@ topics:
 
 ## Overview
 
-Here are some quick links to get you up and running with the GraphQL API v4:
+Here are some quick links to get you up and running with the GraphQL API:
 
 * [Authentication](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)
 * [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint)
@@ -36,9 +36,9 @@ The [GraphQL](https://graphql.github.io/) data query language is:
 
 ## Why GitHub is using GraphQL
 
-GitHub chose GraphQL for our API v4 because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over the REST API v3 endpoints. GraphQL lets you replace multiple REST requests with _a single call_ to fetch the data you specify.
+GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and _only_ the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL lets you replace multiple REST requests with _a single call_ to fetch the data you specify.
 
-For more details about why GitHub has moved to GraphQL, see the original [announcement blog post](https://githubengineering.com/the-github-graphql-api/).
+For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/).
 
 ## About the GraphQL schema reference