fix links (#1044)

vesoft-inc · Jan 18, 2022 · 6c93dd1 · 6c93dd1
1 parent 6eb423d
commit 6c93dd1
Show file tree

Hide file tree

Showing 23 changed files with 20 additions and 363 deletions.
diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md
@@ -341,11 +341,11 @@ Nebula Graph {{ nebula.release }} does not provide any commands or tools to supp
 
 3. Scale out graphd: Prepare the binary and config files of the graphd process in the new host. Modify the config files and add all existing addresses of the metad processes. Then start the new graphd process.
 
-4. Scale in storaged: (The number of replicas must be greater than 1) See [Balance remove command](../8.service-tuning/load-balance.md#storage_1). After the command is finished, stop this storaged process.
+4. Scale in storaged: (The number of replicas must be greater than 1) See [Balance remove command](../8.service-tuning/load-balance.md). After the command is finished, stop this storaged process.
 
 5. Scale out storaged: (The number of replicas must be greater than 1) Prepare the binary and config files of the storaged process in the new host, Modify the config files and add all existing addresses of the metad processes. Then start the new storaged process.
 
-You also need to run [Balance Data and Balance leader](../8.service-tuning/load-balance) after scaling in/out storaged.
+You also need to run [Balance Data and Balance leader](../8.service-tuning/load-balance.md) after scaling in/out storaged.
 
 ### "After changing the name of the host, the old one keeps displaying `OFFLINE`. What should I do?"
 

diff --git a/docs-2.0/20.appendix/0.vid.md b/docs-2.0/20.appendix/0.vid.md
diff --git a/docs-2.0/20.appendix/3.system-design.md b/docs-2.0/20.appendix/3.system-design.md
diff --git a/docs-2.0/20.appendix/4.raft.md b/docs-2.0/20.appendix/4.raft.md
diff --git a/docs-2.0/20.appendix/5.partition.md b/docs-2.0/20.appendix/5.partition.md
diff --git a/docs-2.0/20.appendix/comments.md b/docs-2.0/20.appendix/comments.md
diff --git a/docs-2.0/20.appendix/identifier-case-sensitivity.md b/docs-2.0/20.appendix/identifier-case-sensitivity.md
diff --git a/docs-2.0/20.appendix/keywords-and-reserved-words.md b/docs-2.0/20.appendix/keywords-and-reserved-words.md
diff --git a/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md b/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md
@@ -55,7 +55,7 @@ nebula> SHOW JOB 31;
 +----------------+---------------------+------------+-------------------------+-------------------------+
 ```
 
-Nebula Graph creates a job to rebuild the index. The job ID is displayed in the preceding return message. To check if the rebuilding process is complete, use the `SHOW JOB <job_id>` statement. For more information, see [SHOW JOB](../18.operation-and-maintenance-statements/4.job-statements.md/#show-job-job_id).
+Nebula Graph creates a job to rebuild the index. The job ID is displayed in the preceding return message. To check if the rebuilding process is complete, use the `SHOW JOB <job_id>` statement. For more information, see [SHOW JOB](../18.operation-and-maintenance-statements/4.job-statements.md#show_job).
 
 ## Legacy version compatibility
 

diff --git a/...l-guide/8.clauses-and-options/7.unwind.md → ...gql-guide/8.clauses-and-options/unwind.md b/...l-guide/8.clauses-and-options/7.unwind.md → ...gql-guide/8.clauses-and-options/unwind.md
diff --git a/...and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md b/...and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md
@@ -169,6 +169,6 @@ If the compiling fails, we suggest you:
 
 1. Check whether the operating system release meets the requirements and whether the memory and hard disk space are sufficient.
 
-2. Check whether the [third-party](../1.resource-preparations/#_5) is installed correctly.
+2. Check whether the [third-party](../1.resource-preparations.md) is installed correctly.
 
 3. Use `make -j1` to reduce the compiling concurrency.
diff --git a/...-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md b/...-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md
@@ -282,7 +282,7 @@ sudo /usr/local/nebula/scripts/nebula.service start <metad|graphd|storaged|all>
 
 ### Step 4: Check the cluster status
 
-Install the native CLI client [Nebula Console](../../2.quick-start/3.connect-to-nebula-graph.md#_1), then connect to any machine that has started the graphd process, and run `SHOW HOSTS` to check the cluster status. For example:
+Install the native CLI client [Nebula Console](../../2.quick-start/3.connect-to-nebula-graph.md), then connect to any machine that has started the graphd process, and run `SHOW HOSTS` to check the cluster status. For example:
 
 ```bash
 $ ./nebula-console --addr 192.168.10.111 --port 9669 -u root -p nebula