Update 2.match.md (#688)

vesoft-inc · Sep 2, 2021 · eed0a82 · eed0a82
1 parent e71098b
commit eed0a82
Showing 1 changed file with 3 additions and 3 deletions.
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
@@ -183,7 +183,7 @@ nebula> MATCH (v:player { name: 'Tim Duncan' })--(v2) \
 
 You can use the `--` symbol to represent edges of both directions and match vertices connected by these edges.
 
-!!! Legacy version compatibility
+!!! compatibility "Legacy version compatibility"
 
     In nGQL 1.x, the `--` symbol is used for inline comments. Starting from nGQL 2.x, the `--` symbol represents an incoming or outgoing edge.
 
@@ -284,7 +284,7 @@ nebula> MATCH p=(v:player{name:"Tim Duncan"})-->(v2) \
 +-------------------------------------------+
 ```
 
-!!! note "OpenCypher compatibility"
+!!! compatibility "OpenCypher compatibility"
 
     In nGQL, the `@` symbol represents the rank of an edge, but openCypher has no such concept.
 
@@ -426,7 +426,7 @@ You can use the `:<edge_type>*[minHop]..<maxHop>` pattern to match variable-leng
 |`minHop`|Optional. It represents the minimum length of the path. `minHop` must be a non-negative integer. The default value is 1.|
 |`maxHop`|Required. It represents the maximum length of the path. `maxHop` must be a non-negative integer. It has no default value.|
 
-!!! note "OpenCypher compatibility"
+!!! compatibility "OpenCypher compatibility"
 
     In openCypher, `maxHop` is optional and defaults to infinity. When no bounds are given, `..` can be omitted. However, in nGQL, `maxHop` is required. And `..` cannot be omitted.