delete zone (#1066)

docs-2.0/2.quick-start/4.nebula-graph-crud.md

@@ -27,15 +27,25 @@ In this topic, we will use the following dataset to demonstrate basic CRUD opera
 
 ## Manage the Storage services in a Nebula Graph cluster
 
-First, add the Storage services to a Nebula Graph cluster. For more information, see [Manage zone](../4.deployment-and-installation/5.zone.md)。
+First, add the Storage services to a Nebula Graph cluster. 
+
+<!--
+For more information, see [Manage zone](../4.deployment-and-installation/5.zone.md)。
+-->
 
 !!! compatibility
 
     From Nebula Graph version 3.0.0, the Storage services added in the configuration files **CANNOT** be read or written directly. The configuration files only register the Storage services into the Meta services. You must run the `ADD HOSTS` command to read and write data on Storage servers.
 
+```ngql
+ADD HOSTS <ip>:<port> [,<ip>:<port> ...];
+```
+
+<!--
 ```ngql
 ADD HOSTS <ip>:<port> [,<ip>:<port> ...] [INTO NEW ZONE "<new_zone_name>"];
 ```
+-->
 
 Example：
 

docs-2.0/20.appendix/0.FAQ.md

@@ -74,9 +74,11 @@ It is a known issue. Just retry 1 to N times, where N is the partition number. T
 
 Starting with Nebula Graph 3.0.0, the statements `LOOKUP`, `GO`, and `FETCH` must output results with the `YIELD` clause. For more information, see [YIELD](../3.ngql-guide/8.clauses-and-options/yield.md).
 
+<!--
 ### "How to resolve the error `Zone not enough!`?"
 
 From Nebula Graph version 3.0.0, the Storage services added in the configuration files **CANNOT** be read or written directly. The configuration files only register the Storage services into the Meta services. You must run the `ADD HOSTS` command to read and write data on Storage servers. For more information, see [Manage logical rack](../4.deployment-and-installation/5.zone.md)。
+-->
 
 ### "How to resolve the error `To get the property of the vertex in 'v.age', should use the format 'var.tag.prop'`?"
 

docs-2.0/3.ngql-guide/9.space-statements/1.create-space.md

@@ -16,11 +16,7 @@ CREATE SPACE [IF NOT EXISTS] <graph_space_name> (
     [replica_factor = <replica_number>,]
     vid_type = {FIXED_STRING(<N>) | INT[64]}
     )
-    [ON zone_list]
     [COMMENT = '<comment>'];
-
-zone_list:
-    "zone_name" [,"zone_name" ...]
 ```
 
 |Parameter|Description|
@@ -30,9 +26,12 @@ zone_list:
 |`partition_num`|Specifies the number of partitions in each replica. The suggested number is five times the number of the hard disks in the cluster. For example, if you have 3 hard disks in the cluster, we recommend that you set 15 partitions. The default value is 100.|
 |`replica_factor`|Specifies the number of replicas in the cluster. The suggested number is 3 in a production environment and 1 in a test environment. The replica number must be an **odd number** for the need of quorum-based voting. The default value is 1.|
 |`vid_type`|A required parameter. Specifies the VID type in a graph space. Available values are `FIXED_STRING(N)` and `INT64`. `INT` equals to `INT64`. `FIXED_STRING(<N>)` specifies the VID as a string, while `INT64` specifies it as an integer. `N` represents the maximum length of the VIDs. If you set a VID that is longer than `N` characters, Nebula Graph throws an error.|
-|`zone_list`|Specifies the zone list to which space belongs. Nebula Graph will create partitions and replicas in these zones. The number of replicas can not exceed the number of zones. If `zone_list` is not specified, it belongs to all zones by default. For more information, see [Manage zone](../../4.deployment-and-installation/5.zone.md).|
 |`COMMENT`|The remarks of the graph space. The maximum length is 256 bytes. By default, there is no comments on a space.|
 
+<!--
+|`zone_list`|Specifies the zone list to which space belongs. Nebula Graph will create partitions and replicas in these zones. The number of replicas can not exceed the number of zones. If `zone_list` is not specified, it belongs to all zones by default. For more information, see [Manage zone](../../4.deployment-and-installation/5.zone.md).|
+-->
+
 !!! caution
 
     If the replica number is set to one, you will not be able to load balance or scale out the Nebula Graph Storage Service with the [BALANCE](../../8.service-tuning/load-balance.md) statement.

mkdocs.yml

@@ -307,7 +307,7 @@ nav:
       - Deploy license: 4.deployment-and-installation/deploy-license.md
       - Manage Service: 4.deployment-and-installation/manage-service.md
       - Connect to Service: 4.deployment-and-installation/connect-to-nebula-graph.md
-      - Manage zone: 4.deployment-and-installation/5.zone.md
+#      - Manage zone: 4.deployment-and-installation/5.zone.md
       - Upgrade:
           - Upgrade Nebula Graph to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md
           - Upgrade Nebula Graph from v2.0.x to the current version: 4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md
@@ -548,6 +548,7 @@ plugins:
         - CHANGELOG.md
         - spark-connector/*
         - nebula-operator/*
+        - 4.deployment-and-installation/5.zone.md
 # Exclude the file with the following file name.
 #        - abc.md
 # Exclude files with regular expressions (regexes)