Skip to content

Commit 967243e

Browse files
authored
Merge pull request #239 from kant/patch-1
Typo on #162 & 283
2 parents 694b153 + eca2848 commit 967243e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/HowItWorks.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ Node: {
159159
```
160160

161161
#### Notes
162-
In order to reduce memory usage, we plan to remove the NodeKind property, and instead rely soley on
162+
In order to reduce memory usage, we plan to remove the NodeKind property, and instead rely solely on
163163
subclasses in order to represent the Node's kind. This should reduce memory usage by ~16 bytes per
164164
Node.
165165

@@ -182,7 +182,7 @@ WIDTH(T) -> T.Width
182182
#### Invariants
183183
* Invariants for all Tokens hold true
184184
* The tree contains every token
185-
* span of any node is sum of spans of child nodes and tokens
185+
* Span of any node is sum of spans of child nodes and tokens
186186
* The tree length exactly matches the file length
187187
* Every leaf node of the tree is a token
188188
* Every Node contains at least one Token
@@ -222,7 +222,7 @@ if ($expression // ) <- MissingToken
222222
```
223223

224224
In this case, `eat(")")` will generate a `MissingToken` because the grammar expects a
225-
token to be there, but it does not exist.
225+
token to be there, but it does not exist.
226226

227227
##### Example 2
228228
```php
@@ -280,7 +280,7 @@ if ($a >
280280
281281
In this case, the user likely intended the type of `$b` to be `MyClass`. However,
282282
because under normal circumstances, parsers will ignore whitespace, the example above
283-
would produce the following tree, whic himplies that the `$b` assignment never happens.
283+
would produce the following tree, which implies that the `$b` assignment never happens.
284284
```
285285
SourceFileNode
286286
- IfNode
@@ -389,4 +389,4 @@ significant boost and works on a wide variety of machine configurations.
389389
* Fuzz testing - test the parser against automatically generated inputs to exercise edge cases in a bulk fashion, and
390390
and ensure expected properties of the tree.
391391
* Community feedback - try and get the parser in the hands of as many people as possible so we can validate a
392-
wide range of use cases. The Syntax Visualizer tool is one tool to help us increase reach.
392+
wide range of use cases. The Syntax Visualizer tool is one tool to help us increase reach.

0 commit comments

Comments
 (0)