fix: rename lenient to relaxed

website/advanced/match-algorithm.md

@@ -1,11 +1,14 @@
 # Deep Dive into ast-grep's Match Algorithm
 
-In descending order of strict-ness
 
-* CST: all nodes are matched
-* Smart: all nodes except source trivial nodes are matched.
-* Significant: only significant nodes are matched
-* AST: only ast nodes are matched
-* Lenient: ast-nodes excluding comments are matched
+By default, ast-grep uses a smart strategy to match pattern against the AST node. All nodes in the pattern must be matched, but it will skip unnamed nodes in target code.
 
-Currently ast-grep only supports Smart.
+For the definition of __*named*__ and __*unnamed*__ nodes, please refer to the [core concepts](/advanced/core-concepts.html) doc.
+
+* `cst`: All nodes in the pattern and target code must be matched. No node is skipped.
+* `smart`: All nodes in the pattern must be matched, but it will skip unnamed nodes in target code. This is the default behavior.
+* `ast`: Only named AST nodes in both pattern and target code are matched. All unnamed nodes are skipped.
+* `relaxed`: Named AST nodes in both pattern and target code are matched. Comments and unnamed nodes are ignored.
+* `signature`: Only named AST nodes' kinds are matched. Comments, unnamed nodes and text are ignored.
+
+Currently ast-grep only supports Smart.

website/guide/rule-config/atomic-rule.md

@@ -198,4 +198,4 @@ const foo = () => {
 The first step to compose a rule is to find the target. In this case, we can first use kind: `arrow_function` to find function node. Then we can use other rules to filter candidate nodes that does have return type.
 
 Another trick to write cleaner rule is to use sub-rules as fields.
-Please refer to [composite rule](/guide/rule-config/composite-rule.html#combine-different-rules-as-fields) for more details.
+Please refer to [composite rule](/guide/rule-config/composite-rule.html#combine-different-rules-as-fields) for more details.