jdavidps
diff --git a/‎05_higher_order.md‎
Lines changed: 1 addition & 1 deletion b/‎05_higher_order.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎11_async.md‎
Lines changed: 1 addition & 1 deletion b/‎11_async.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎18_http.md‎
Lines changed: 1 addition & 1 deletion b/‎18_http.md‎
Lines changed: 1 addition & 1 deletion
@@ -612,7 +612,7 @@ In [Chapter ?](values) I mentioned that JavaScript ((string))s are
 encoded as a sequence of 16-bit numbers called _((code unit))s_. A
 ((Unicode)) ((character)) code was initially supposed to fit within
 such a unit (which gives you a little over 65 thousand characters).
-When it became clear that that wasn't going to be enough, many people
+When it became clear that wasn't going to be enough, many people
 balked at the need to use more memory per character. To address these
 concerns, ((UTF-16)), the format used by JavaScript strings, was
 invented. It describes some characters using a single 16-bit code
 
@@ -347,7 +347,7 @@ This asynchronous function returns a meaningful value. This is the
 main advantage of promises—they simplify the use of asynchronous
 functions. Instead of having to pass around callbacks, promise-based
 functions look similar to regular ones: they take input as arguments,
-and return their output. The only difference is that that the output
+and return their output. The only difference is that the output
 may not have resolved yet.
 
 ## Failure
 
@@ -1201,7 +1201,7 @@ have compared the old list of note names to the new, and avoid
 rebuilding the list of options if it is the same, for example. There
 are various libraries and ((framework))s that aim to making this easy,
 most of which require you to create your HTML elements in a
-library-specific way so that that ((library)) can automatically
+library-specific way so that ((library)) can automatically
 determine what needs to change and what doesn't.
 
 {{index "Object.assign function", object, property, "computed property"}}