clarify export data

Author: raphael-istari

content/deploy/admin/dgraph-administration.md

@@ -145,7 +145,7 @@ As an `Administrator` you might want to export data from Dgraph to:
 * move the data from Dgraph Cloud instance to another Dgraph instance, or Dgraph Cloud instance
 * share your data
 
-For more information about exporting your database, see [Export data]({{< relref "howto/exportdata/about-export.md" >}})
+For more information about exporting your database, see [Export data]({{< relref "export-data.md" >}})
 
 ## Shut down database
 

content/deploy/installation/production-checklist.md

@@ -39,8 +39,9 @@ Do not run multiple Dgraph Zeros or Dgraph Alpha processes on a single machine.
 
 ### Operating System
 
-Dgraph is designed to run on Linux. To run Dgraph on Windows
-and macOS, use the [standalone Docker image]({{<relref "dgraph-overview#to-run-dgraph-using-the-standalone-docker-image">}}).
+Dgraph is designed to run on Linux. 
+
+To run Dgraph on Windows and macOS, use the [standalone Docker image]({{<relref identifier="learning-environment">}}).
 
 ### CPU and Memory
 
@@ -104,7 +105,7 @@ A Dgraph instance is run as a single process from a single static binary. It doe
 
 A backup policy is a predefined, set schedule used to schedule backups of information from business applications. A backup policy helps to ensure data recoverability in the event of accidental data deletion, data corruption, or a system outage.
 
-For Dgraph, backups are created using the [backups enterprise feature]({{< relref "/enterprise-features/binary-backups" >}}). You can also create full exports of your data and schema using [data exports]({{< relref "dgraph-administration.md#exporting-database" >}}) available as an open source feature.
+For Dgraph, backups are created using the [backups feature]({{< relref "/enterprise-features/binary-backups" >}}). You can also create full exports of your data and schema using [data exports]({{< relref "dgraph-administration.md#exporting-database" >}}).
 
 We **strongly** recommend that you have a backup policy in place before moving your application to the production phase, and we also suggest that you have a backup policy even for pre-production apps supported by Dgraph database instances running in development, staging, QA or pre-production clusters.
 

content/dql/query/dql-query.md

@@ -190,7 +190,7 @@ Dgraph offers functions for
   - if geo area intersects a given are : [intersects]({{< relref "functions.md#intersects" >}})
 
 
-### Variable (`var`) block
+### Var block
 
   Variable blocks (`var` blocks) start with the keyword `var` instead of a block name.
 

content/dql/query/functions.md

@@ -11,7 +11,7 @@ Functions allow filtering based on properties of nodes or [variables]({{<relref
 
 
 Comparison functions (`eq`, `ge`, `gt`, `le`, `lt`) in the query root (aka `func:`) can only
-be applied on [indexed predicates]({{< relref "dql-schema.md#indexing" >}}). 
+be applied on [indexed predicates]({{< relref "predicate-indexing.md" >}}). 
 Comparison functions can be used on [@filter]({{<relref "filter.md" >}}) directives even on predicates that have not been indexed.
 Filtering on non-indexed predicates can be slow for large datasets, as they require
 iterating over all of the possible values at the level where the filter is being used.
@@ -377,7 +377,7 @@ Query Example: Movies with directors with `Steven` in `name` and have directed m
 
 
 
-Query Example: A movie in each genre that has over 30000 movies.  Because there is no order specified on genres, the order will be by UID.  The [count index]({{< relref "dql-schema.md#count-index">}}) records the number of edges out of nodes and makes such queries more .
+Query Example: A movie in each genre that has over 30000 movies.  Because there is no order specified on genres, the order will be by UID.  The [count index]({{< relref "predicate-indexing.md#count-index">}}) records the number of edges out of nodes and makes such queries more .
 
 {{< runnable >}}
 {

content/dql/query/sorting.md

@@ -19,7 +19,7 @@ Sortable Types: `int`, `float`, `String`, `dateTime`, `default`
 
 Results can be sorted in ascending order (`orderasc`) or descending order (`orderdesc`) by a predicate or variable.
 
-For sorting on predicates with [sortable indices]({{< relref "dql-schema.md#sortable-indices">}}), Dgraph sorts on the values and with the index in parallel and returns whichever result is computed first.
+For sorting on predicates with [sortable indices]({{< relref "predicate-indexing.md#sortable-indices">}}), Dgraph sorts on the values and with the index in parallel and returns whichever result is computed first.
 
 {{% notice "note" %}}
 Dgraph returns `null` values at the end of the results, irrespective of their sort. This behavior is consistent across indexed and non-indexed sorts.

content/howto/exportdata/export-data.md renamed to content/howto/export-data.md

@@ -1,13 +1,20 @@
 +++
-title = "Export data from Dgraph"
+title = "Export data"
 type = "docs"
 keywords = "export, data, self hosted"
+weight = 3
 [menu.main]
-    parent = "exportdata"
-    weight = 3
+    identifier = "exportdata"
+    parent = "howto"
 +++
 
-As an `Administrator` you can export data on all nodes, configure the Alpha server, specify the export format, export to an object store, disable HTTPS for exports, and encrypt exports
+As an `Administrator` you can export data from Dgraph to an an object store, NFS, or a file path.
+
+When you export data, three files are generated:
+
+* `g01.gql_schema.gz`: The GraphQL schema file. This file can be imported using the Schema APIs
+* `g01.json.gz` or `g01.rdf.gz`: the data from your instance in JSON format or RDF format. By default, Dgraph exports data in RDF format.
+* `g01.schema.gz`: This file is the internal Dgraph schema. If you have set up the Dgraph Cloud instance with a GraphQL schema, then you can ignore this file.
 
 ## Export data using  the GraphQL admin endpoint
 
@@ -171,7 +178,7 @@ You can access Azure Blob Storage locally using one of these methods:
      --set accessKey="<AccountName>",secretKey="<AccountKey>" \
      --set azuregateway.enabled=true
    ```
-You can use the [MinIO GraphQL mutation]({{< relref "/howto/exportdata/export-data.md#example-mutation-to-export-to-minio" >}}) with MinIO configured as a gateway.
+You can use the [MinIO GraphQL mutation]({{< relref "export-data.md#example-mutation-to-export-to-minio" >}}) with MinIO configured as a gateway.
 
 ### Google Cloud Storage
 
@@ -219,7 +226,7 @@ When you have a `credentials.json`, you can access GCS locally using one of thes
    helm install my-gateway minio/minio \
      --values myvalues.yaml
    ```
-You can use the [MinIO GraphQL mutation]({{< relref "/howto/exportdata/export-data.md#example-mutation-to-export-to-minio" >}}) with MinIO configured as a gateway.
+You can use the [MinIO GraphQL mutation]({{< relref "export-data.md#example-mutation-to-export-to-minio" >}}) with MinIO configured as a gateway.
 
 ## Disable HTTPS for exports to S3 and Minio
 

content/howto/exportdata/_index.md

@@ -18,7 +18,7 @@ Verify that you have a local folder `<local-path-to-data>` containing
 - at least one **data file** in RDF or JSON in plain or gzip format with the data to import
 - an optional **schema file**.
 
-Those files have been generated by an [export]({{< relref "about-export.md" >}}) or by a [data migration]({{< relref "about-data-migration.md" >}}) tool.
+Those files have been generated by an [export]({{< relref "export-data.md" >}}) or by a [data migration]({{< relref "about-data-migration.md" >}}) tool.
 
 
 ## Importing data on Dgraph Cloud