diff --git a/content/deploy/cli-command-reference.md b/content/deploy/cli-command-reference.md
index a59b7561..60fec5f2 100644
--- a/content/deploy/cli-command-reference.md
+++ b/content/deploy/cli-command-reference.md
@@ -124,7 +124,7 @@ The `--badger` superflag allows you to set many advanced [Badger options](https:
| Old flag | Old type | New superflag and options | New type | Applies to | Notes |
|---------:|:---------|---------:|:---------|:----:|:----:|
-| | | **`--graphql`** | | | [GraphQL]({{< relref "graphql/overview.md" >}}) superflag |
+| | | **`--graphql`** | | | GraphQL superflag |
| `--graphql_introspection` | bool | `introspection` | bool |`alpha`| Enables GraphQL schema introspection |
| `--graphql_debug` | bool | `debug` | bool |`alpha`| Enables debug mode in GraphQL |
| `--graphql_extensions` | bool | `extensions` | bool |`alpha`| Enables extensions in GraphQL response body |
diff --git a/content/dgraph-overview.md b/content/dgraph-overview.md
index 1eddd588..05ec5d4b 100644
--- a/content/dgraph-overview.md
+++ b/content/dgraph-overview.md
@@ -55,7 +55,7 @@ For complex queries that the GraphQL specification does not support, Dgraph prov
As a native GraphQL database, Dgraph doesn’t have a relational database running in the background, or complex resolvers to map between database and GraphQL schemas. We often call this "single-schema development." The big time savings is that there are no GraphQL resolvers or custom queries needed to get started. All GraphQL fields are "resolved" simply by following our graph database edges to required fields. With single-schema development, you can change your GraphQL schema, insert data, and call your new APIs in seconds, not hours.
- To learn more about Dgraph's GraphQL implementation, see this [GraphQL Overview]({{< relref "/graphql/overview" >}}). If you are a SQL user, check out:
+ If you are a SQL user, check out:
[Dgraph for SQL Users](https://dgraph.io/learn/courses/datamodel/sql-to-dgraph/overview/introduction/).
diff --git a/content/graphql/overview/index.md b/content/graphql/overview/index.md
deleted file mode 100644
index c303b99d..00000000
--- a/content/graphql/overview/index.md
+++ /dev/null
@@ -1,74 +0,0 @@
-+++
-title = "GraphQL Overview"
-description = "Dgraph gives you GraphQL. You’re always working with GraphQL, not a translation layer. Here's all the GraphQL documentation that you might need."
-weight = 1
-[menu.main]
- name = "Overview"
- identifier = "graphql-overview"
- parent = "graphql"
-+++
-
-**Welcome to the official GraphQL documentation for Dgraph.**
-
-Designed from the ground up to be run in production, Dgraph is the native GraphQL database with a graph backend. It is open-source, scalable, distributed, highly available and lightning fast.
-
-* These docs tell you all the details. If you are looking for a walk through tutorial, then head over to our [tutorials section](/graphql/todo-app-tutorial/todo-overview).
-
-Dgraph gives you GraphQL. You're always working with GraphQL, not a translation layer. When you build an app with Dgraph, Dgraph is your GraphQL database.
-
-## Exploring the docs
-
-* How it Works - Once you've got yourself started with [tutorials](/graphql/todo-app-tutorial/todo-overview), you might need to review [how it works](/graphql/how-dgraph-graphql-works).
-* [Schema](/graphql/schema/schema-overview) - You'll need the schema reference to find out about all the options of what can be in your schema.
-* [The API](/graphql/api/api-overview) - The API section tells you about how the GraphQL API is served and how you can access it.
-* [Queries](/graphql/queries/queries-overview) - Everything you need to know about writing GraphQL queries.
-* [Mutations](/graphql/mutations/mutations-overview) - Everything you need to know about writing GraphQL mutations with Dgraph.
-* [Subscriptions](/graphql/subscriptions) - GraphQL subscriptions help you make your APP more responsive or, for example, add live feeds. Dgraph can generate subscriptions for you.
-* [Custom Logic](/graphql/custom/custom-overview) - Dgraph's auto generated GraphQL API is fantastic, but as your app gets more complicated, you'll need to add custom business logic to your API.
-* [Authorization](/graphql/authorization/authorization-overview) - Find out how Dgraph can add automated authorization to your GraphQL API.
-* [Local Administration](/graphql/admin) - Once you're up and running you might also need to know a few details about administering your Dgraph instance if you are running locally.
-* [Dgraph Cloud](https://dgraph.io/docs/cloud/admin/overview) - If you are using hosted Dgraph on Dgraph Cloud, then head over here to learn about administering your backend.
-
-## Contribute
-
-
-
-
\ No newline at end of file
diff --git a/scripts/branchdeploy.sh b/scripts/branchdeploy.sh
old mode 100644
new mode 100755
index bfc89f0d..71b76a15
--- a/scripts/branchdeploy.sh
+++ b/scripts/branchdeploy.sh
@@ -15,9 +15,9 @@ RESET='\033[0m'
# argument $1 is the netlify base url
# argument $2 is the $HEAD netlify variable which is the branch name
+echo "branchdeploy URL $1 branch $2"
releaseVersion=$(echo $2 | sed 's/.*\///')
-
-echo "branchdeploy => '$releaseVersion'"
+echo "version '$releaseVersion'"
VERSION_STRING="$releaseVersion"
# In Unix environments, env variables should also be exported to be seen by Hugo
export VERSIONS=${VERSION_STRING}