Skip to content

Commit 96b827f

Browse files
authored
fix: small errors
1 parent 91999f6 commit 96b827f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,12 +136,12 @@ nodeVar2->nodeVar3
136136

137137
Connection syntax is as follows:
138138

139-
`<node variable name>[(<specificaion1>[, <specification2])]-><node variable name>[[(<specificaion1>[, <specification2])]-><node variable name>]`
139+
`<node variable name>[(<specification1>[, <specification2])]-><node variable name>[[(<specification1>[, <specification2])]-><node variable name>]`
140140

141141
Items in `[]` are optional.
142142

143143
### Directions
144-
The following directions are availiable and define the direction the connection will leave the node from. If there are more than one specifiers, it is always the last. All nodes have a default direction making this an optional specification. `<direction>` will be used to indicate that one of the below should be used in its place.
144+
The following directions are available and define the direction the connection will leave the node from. If there are more than one specifiers, it is always the last. All nodes have a default direction making this an optional specification. `<direction>` will be used to indicate that one of the below should be used in its place.
145145

146146
* left
147147
* right
@@ -154,7 +154,7 @@ Each node variables has optional specifiers, like direction, and some have speci
154154
### start
155155
Optional direction
156156

157-
`startVar(<dirction>)->nextNode`
157+
`startVar(<direction>)->nextNode`
158158

159159
### end
160160
No specifications because connections only go to the end node and do not leave from it.

0 commit comments

Comments
 (0)