aboutsummaryrefslogtreecommitdiff
path: root/src/content/chapter5_advanced_features/lesson07_multi_target_externals
diff options
context:
space:
mode:
Diffstat (limited to 'src/content/chapter5_advanced_features/lesson07_multi_target_externals')
-rw-r--r--src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html b/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html
index 6e02d36..c755ac7 100644
--- a/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html
+++ b/src/content/chapter5_advanced_features/lesson07_multi_target_externals/en.html
@@ -11,10 +11,10 @@
possible due to incompatibilities in how IO and concurreny works in Erlang and
JavaScript. With Erlang concurrent IO is handled transparently by the runtime,
while in JavaScript concurrent IO requires the use of promises or callbacks.
- If your code uses the Erlang style it is typically not possible to implement
- in JavaScript, while if callbacks are used then it won't be compatible with
- most Gleam and Erlang code as it forces any code that calls the function to
- also use callbacks.
+ If your code uses the Erlang style it's typically not possible to implement in
+ JavaScript, while if callbacks are used then it won't be compatible with most
+ Gleam and Erlang code as it forces any code that calls the function to also
+ use callbacks.
</p>
<p>
Libraries that make use of concurrent IO will typically have to decide whether