From 0c3d42962447b5c59cad756e3269cdc4f5255344 Mon Sep 17 00:00:00 2001
From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com>
Date: Wed, 9 Mar 2022 17:08:03 +0800
Subject: [PATCH] Update 2.match.md

---
 docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md b/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
index 67b56d7c8d8..27337fe6af0 100644
--- a/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
+++ b/docs-2.0/3.ngql-guide/7.general-query-statements/2.match.md
@@ -96,7 +96,9 @@ nebula> SHOW JOB 122;
 
 !!! compatibility "Legacy version compatibility"
 
-    In Nebula Graph versions earlier than 3.0.0, nGQL does not support `MATCH (v) RETURN v`. As of version 3.0.0, nGQL support `MATCH (v) RETURN v`, there is no need to create an index, but you need to use `LIMIT` to limit the number of output results.
+    In Nebula Graph versions earlier than 3.0.0, nGQL does not support `MATCH (v) RETURN v`.
+    
+    As of version 3.0.0, nGQL support `MATCH (v) RETURN v LIMIT n`, there is no need to create an index, but you must use `LIMIT` to limit the number of output results. nGQL still does not support `MATCH (v) RETURN v`.
 
 You can use a user-defined variable in a pair of parentheses to represent a vertex in a pattern. For example: `(v)`.