Merge branch 'master' into add-exchange-doc

docs-2.0/nebula-exchange/parameter-reference/ex-ug-para-import-command.md

@@ -46,3 +46,4 @@ The following table lists command parameters.
 |-r / --reload | No  |  -  |  Specify the path of the reload file that needs to be reloaded. |
 
 For more Spark parameter configurations, see [Spark Configuration](https://spark.apache.org/docs/latest/configuration.html#runtime-environment).
+

docs-2.0/nebula-exchange/parameter-reference/ex-ug-parameter.md

@@ -24,7 +24,7 @@ This document lists only some Spark parameters. For more information, see [Spark
 |:---|:---|:---|:---|:---|
 |`spark.app.name`|string|-|No|The drive name in Spark.|
 |`spark.driver.cores`|int|`1`|No|The number of CPU cores used by a driver, only applicable to a cluster mode.|
-|`spark.driver.maxResultSize`|string|`1G`|No|The total size limit (in bytes) of the serialized results of all partitions in a single Spark operation（such as collect）. The minimum value is 1M, and 0 means unlimited|
+|`spark.driver.maxResultSize`|string|`1G`|No|The total size limit (in bytes) of the serialized results of all partitions in a single Spark operation（such as collect）. The minimum value is 1M, and 0 means unlimited|
 |`spark.executor.memory`|string|`1G`|No|The amount of memory used by a Spark driver which can be specified in units, such as 512M or 1G.|
 |`spark.cores.max`|int|`16`|No|The maximum number of CPU cores of applications requested across clusters (rather than from each node) when a driver runs in a coarse-grained sharing mode on a standalone cluster or a Mesos cluster. The default value is `spark.deploy.defaultCores` on a Spark  standalone cluster manager or the value of the `infinite` parameter (all available cores) on Mesos.|
 
@@ -70,7 +70,7 @@ For different data sources, the vertex configurations are different. There are m
 |:---|:---|:---|:---|:---|
 |`tags.name`|string|-|Yes|The tag name defined in Nebula Graph.|
 |`tags.type.source`|string|-|Yes|Specify a data source. For example, `csv`.|
-|`tags.type.sink`|string|`client`|Yes|Specify an import method. Optional values ​​are `client` and `SST`.|
+|`tags.type.sink`|string|`client`|Yes|Specify an import method. Optional values are `client` and `SST`.|
 |`tags.fields`|list\[string\]|-|Yes|The header or column name of the column corresponding to properties. If there is a header or a column name, please use that name directly. If a CSV file does not have a header, use the form of `[_c0, _c1, _c2]` to represent the first column, the second column, the third column, and so on.|
 |`tags.nebula.fields`|list\[string\]|-|Yes|Property names defined in Nebula Graph, the order of which must correspond to `tags.fields`. For example, `[_c1, _c2]` corresponds to `[name, age]`, which means that values in the second column are the values of the property `name`, and values in the third column are the values of the property `age`.|
 |`tags.vertex.field`|string|-|Yes|The column of vertex IDs. For example, when a CSV file has no header, users can use `_c0` to indicate values in the first column are vertex IDs.|
@@ -187,11 +187,11 @@ For the specific parameters of different data sources for edge configurations, p
 |:---|:---|:---|:---|:---|
 |`edges.name`| string|-|Yes|The edge type name defined in Nebula Graph.|
 |`edges.type.source`|string|-|Yes|The data source of edges. For example, `csv`.|
-|`edges.type.sink`|string|`client`|Yes|The method specified to import data. Optional values ​​are `client` and `SST`.|
+|`edges.type.sink`|string|`client`|Yes|The method specified to import data. Optional values are `client` and `SST`.|
 |`edges.fields`|list\[string\]|-|Yes|The header or column name of the column corresponding to properties. If there is a header or column name, please use that name directly. If a CSV file does not have a header, use the form of `[_c0, _c1, _c2]` to represent the first column, the second column, the third column, and so on.|
 |`edges.nebula.fields`|list\[string\]|-|Yes|Edge names defined in Nebula Graph, the order of which must correspond to `edges.fields`. For example, `[_c2, _c3]` corresponds to `[start_year, end_year]`, which means that values in the third column are the values of the start year, and values in the fourth column are the values of the end year.|
 |`edges.source.field`|string|-|Yes|The column of starting vertices of edges. For example, `_c0` indicates a value in the first column that is used as a starting vertex of an edge.|
 |`edges.target.field`|string|-|Yes|The column of destination vertices of edges. For example, `_c0` indicates a value in the first column that is used as a destination vertex of an edge.|
-|`edges.ranking`|int|-|No|The column of rank values. If not specified, all rank values ​​are `0` by default.|
+|`edges.ranking`|int|-|No|The column of rank values. If not specified, all rank values are `0` by default.|
 |`edges.batch`|int|`256`|Yes|The maximum number of edges written into Nebula Graph in a single batch.|
 |`edges.partition`|int|`32`|Yes|The number of Spark partitions.|