Revamp/import data

content/deploy/_index.md

@@ -38,14 +38,14 @@ running multiple instances of Dgraph, over multiple servers in a cluster.
     <a href="{{< relref "tls-configuration.md">}}">
       <h2>TLS Configuration</h2>
       <p>
-        Setting up secure TLS connections between clients and servers 
+        Setting up secure TLS connections between clients and servers
       </p>
     </a>
   </div>
   <div class="item">
     <div class="icon"><i class="lni lni-upload" aria-hidden="true"></i></div>
-    <a href="{{< relref "fast-data-loading/overview.md">}}">
-      <h2>Fast Data Loading</h2>
+    <a href="{{< relref "about_import.md">}}">
+      <h2>Data Import</h2>
       <p>
         Dgraph tools for fast data loading
       </p>

content/deploy/dgraph-administration.md

@@ -189,7 +189,7 @@ Doing periodic exports is always a good idea. This is particularly useful if you
 2. Ensure it is successful
 3. [Shutdown Dgraph]({{< relref "#shut-down-database" >}}) and wait for all writes to complete
 4. Start a new Dgraph cluster using new data directories (this can be done by passing empty directories to the options `-p` and `-w` for Alphas and `-w` for Zeros)
-5. Reload the data via [bulk loader]({{< relref "deploy/fast-data-loading/bulk-loader.md" >}})
+5. Reload the data via [bulk loader]({{< relref "bulk-loader.md" >}})
 6. Verify the correctness of the new Dgraph cluster. If all looks good, you can delete the old directories (export serves as an insurance)
 
 These steps are necessary because Dgraph's underlying data format could have changed, and reloading the export avoids encoding incompatibilities.
@@ -265,7 +265,7 @@ are affected. Then, you can drop the old types and predicates from DB.
     command will do.
 
 {{% notice "note" %}}
-The above steps are valid for migration from a cluster in `v20.11` to a single-tenant cluster in `v21.03`, 
+The above steps are valid for migration from a cluster in `v20.11` to a single-tenant cluster in `v21.03`,
 as backup and restore are cluster-wide operations and a single namespace cannot be restored in a multi-tenant cluster.
 {{% /notice %}}