Skip to content

Commit 3217cb3

Browse files
authored
Fix some spelling erors
1 parent d5e3fe1 commit 3217cb3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/guides/clj_datatype_constructs.adoc

+3-3
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
99

1010
== Goals of this guide
1111

12-
Clojue supports several constructs for speaking to the Java world
12+
Clojure supports several constructs for speaking to the Java world
1313
and creating types for polymorphic dispatch. +
1414
Because these constructs have overlapping capabilities, it may be confusing to know which construct to use at a given situation. +
1515
Hopefully this guide clarifies what each construct is good at, while presenting minimal usage examples.
@@ -142,12 +142,12 @@ user=> (.close rf)
142142
nil
143143
----
144144

145-
One might ask "Doesn't proxy achieves the same if you do not need to extend a concrete Type?" +
145+
One might ask "Doesn't proxy achieve the same if you do not need to extend a concrete Type?" +
146146
The answer is reify has better performance.
147147

148148
== Take away
149149
To wrap up, here are some rules of thumb:
150150

151151
* Prefer protocols and records over Java Types; stay in Clojure
152152
* If you must extend a Java Class, use proxy
153-
* If you want a on-off implementation of a Protocol/Interface, use reify
153+
* If you want a on-off implementation of a Protocol/Interface, use reify

0 commit comments

Comments
 (0)