diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-clickhouse.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-clickhouse.md
index cf4cc3bd7fc..e36e6d9ca4a 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-clickhouse.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-clickhouse.md
@@ -306,7 +306,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-csv.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-csv.md
index 1bc41ec9c45..7f542151a2f 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-csv.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-csv.md
@@ -391,7 +391,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hbase.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hbase.md
index d7040cecc74..c89bb72bef5 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hbase.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hbase.md
@@ -336,7 +336,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hive.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hive.md
index aaed44f2f3f..3bcde16d450 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hive.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hive.md
@@ -362,7 +362,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md
index 8c1bd861e61..d163d312a1f 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md
@@ -371,7 +371,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-json.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-json.md
index a131dca183d..3adffebfde8 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-json.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-json.md
@@ -390,7 +390,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-kafka.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-kafka.md
index 1e691c64c56..48a74f0dc45 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-kafka.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-kafka.md
@@ -298,7 +298,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md
index 25d278803bc..124716f1a07 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md
@@ -332,7 +332,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-mysql.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-mysql.md
index 6dace844f71..b23bcf80122 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-mysql.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-mysql.md
@@ -344,7 +344,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-neo4j.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-neo4j.md
index ceff54fa526..f840360fc3c 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-neo4j.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-neo4j.md
@@ -311,7 +311,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-oracle.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-oracle.md
index 8614e2a5829..3104e0fd72a 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-oracle.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-oracle.md
@@ -343,7 +343,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-orc.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-orc.md
index 8403ac8bf22..238f4e03be5 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-orc.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-orc.md
@@ -356,7 +356,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-parquet.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-parquet.md
index 8060c015004..71ea17006b2 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-parquet.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-parquet.md
@@ -357,7 +357,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md
index decf08c5857..038e5925603 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md
@@ -307,7 +307,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.
diff --git a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-sst.md b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-sst.md
index 962b41aa6d8..61f8e979e6e 100644
--- a/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-sst.md
+++ b/docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-sst.md
@@ -530,7 +530,7 @@ Connect to the NebulaGraph database using the client tool and import the SST fil
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.