Revamp/correct gqlschema

content/cloud/cloud-api/_index.md

@@ -2,6 +2,6 @@
 title = "Dgraph Cloud API"
 weight = 15
 [menu.main]
-  identifier = "cloud"
+  identifier = "cloud-api"
   parent = "cloud"
 +++

content/dql-syntax/dql-rdf.md

@@ -79,6 +79,7 @@ The supported [RDF datatypes](https://www.w3.org/TR/rdf11-concepts/#section-Data
 
 
 
+
 ### Facets
 ####  Creating a list with facets
 

content/graphql/schema/_index.md

@@ -1,7 +1,7 @@
 +++
 title = "Schema"
 [menu.main]
-  identifier = "schema"
+  identifier = "gqlschema"
   parent = "graphql"
   weight = 2
 +++

content/graphql/schema/authorization/_index.md

@@ -3,7 +3,7 @@ title = "Authorization"
 weight = 5
 [menu.main]
   identifier = "authorization"
-  parent = "schema"
+  parent = "gqlschema"
 +++
 
 Dgraph's GraphQL implementation comes with built-in authorization. This lets you annotate your schema with rules that determine who can query and mutate your data.
@@ -54,7 +54,7 @@ You can authenticate your users using the following methods:
 Dgraph's GraphQL implementation is completely flexible about how your app does
 authentication; instead, Dgraph focuses on authorization.  
 
-Dgraph's GraphQL endpoint supports both symmetric (secret-based) and asymmetric (public key) 
+Dgraph's GraphQL endpoint supports both symmetric (secret-based) and asymmetric (public key)
 encryption. The connection between Dgraph and your authentication mechanism can
 be a JSON Web Key (JWK) URL or a signed JSON Web Token (JWT). So, you can provide
 Dgraph with the public key of the JWT signer (such as Firebase or Auth0) and
@@ -169,4 +169,4 @@ The authorization variables include the rest of the given claims along with the
 
 {{% notice "note" %}}
 In cases where the same variable is present in both custom claims and standard claims, the variable value in the custom claim takes precedence.
-{{% /notice %}}
+{{% /notice %}}

content/graphql/schema/dgraph-schema.md

@@ -3,7 +3,7 @@ title = "Dgraph Schema Fragment"
 description = "While editing your schema, this GraphQL schema fragment can be useful. It sets up the definitions of the directives that you’ll use in your schema."
 weight = 9
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
 +++
 
 While editing your schema, you might find it useful to include this GraphQL schema fragment.  It sets up the definitions of the directives, etc. (like `@search`) that you'll use in your schema.  If your editor is GraphQL aware, it may give you errors if you don't have this available and context sensitive help if you do.

content/graphql/schema/directives/_index.md

@@ -3,7 +3,7 @@ title = "Directives"
 weight = 4
 [menu.main]
   identifier = "directives"
-  parent = "schema"
+  parent = "gqlschema"
 +++
 
 The list of all directives supported by Dgraph.
@@ -111,4 +111,4 @@ Reference: [Subscriptions](/graphql/subscriptions)
 
 The `@lambdaOnMutate` directive allows you to listen to mutation events(`add`/`update`/`delete`). Depending on the defined events and the occurrence of a mutation event, `@lambdaOnMutate` triggers the appropriate lambda function implemented on a given lambda server.
 
-Reference: [LambdaOnMutate directive](/graphql/lambda/webhook)
+Reference: [LambdaOnMutate directive](/graphql/lambda/webhook)

content/graphql/schema/documentation.md

@@ -3,7 +3,7 @@ title = "Documentation and Comments"
 description = "Dgraph accepts GraphQL documentation comments, which get passed through to the generated API and shown as documentation in GraphQL tools."
 weight = 7
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
 +++
 
 ## Schema Documentation Processed  by Generated API

content/graphql/schema/graph-links.md

@@ -3,7 +3,7 @@ title = "Relationships"
 description = "All the data in your app form a GraphQL data graph. That graph has nodes of particular types and relationships between the nodes to form the data graph."
 weight = 2
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
 +++
 
 All the data in your app form a GraphQL data graph. That graph has nodes of particular types and relationships between the nodes to form the data graph.

content/graphql/schema/migration.md

@@ -3,7 +3,7 @@ title = "Schema Migration"
 description = "This document describes all the things that you need to take care while doing a schema update or migration."
 weight = 5
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
     identifier = "schema-migration"
 +++
 

content/graphql/schema/reserved.md

@@ -3,7 +3,7 @@ title = "Reserved Names"
 description = "This document provides the full list of names that are reserved and can’t be used to define any other identifiers."
 weight = 3
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
 +++
 
 The following names are reserved and can't be used to define any other identifiers:

content/graphql/schema/types.md

@@ -3,7 +3,7 @@ title = "Types"
 description = "How to use GraphQL types to set a GraphQL schema for the Dgraph database. Includes scalars, enums, types, interfaces, union, password, & geolocation types."
 weight = 1
 [menu.main]
-    parent = "schema"
+    parent = "gqlschema"
 +++
 
 This page describes how to use GraphQL types to set the a GraphQL schema for