docs(Using parsers): Fix spelling, remove unusual keyword

This commit is contained in:
Nokome Bentley 2021-07-26 11:01:55 +12:00 committed by GitHub
parent d63bbbaadd
commit 12d3e1b898
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -464,7 +464,7 @@ In general, it's a good idea to make patterns more specific by specifying [field
#### Negated Fields
You can also constrain a pattern so that it only mathces nodes that *lack* a certain field. To do this, add a field name prefixed by a `!` within the parent pattern. For example, this pattern would match a class declaration with no type parameters:
You can also constrain a pattern so that it only matches nodes that *lack* a certain field. To do this, add a field name prefixed by a `!` within the parent pattern. For example, this pattern would match a class declaration with no type parameters:
```
(class_declaration
@ -572,7 +572,6 @@ This pattern would match a set of possible keyword tokens, capturing them as `@k
```
[
"break"
" atch"
"delete"
"else"
"for"
@ -630,7 +629,7 @@ The restrictions placed on a pattern by an anchor operator ignore anonymous node
#### Predicates
You can also specify arbitrary metadata and conditions associed with a pattern by adding _predicate_ S-expressions anywhere within your pattern. Predicate S-expressions start with a _predicate name_ beginning with a `#` character. After that, they can contain an arbitrary number of `@`-prefixed capture names or strings.
You can also specify arbitrary metadata and conditions associated with a pattern by adding _predicate_ S-expressions anywhere within your pattern. Predicate S-expressions start with a _predicate name_ beginning with a `#` character. After that, they can contain an arbitrary number of `@`-prefixed capture names or strings.
For example, this pattern would match identifier whose names is written in `SCREAMING_SNAKE_CASE`: