diff --git a/modules/drivers/druid/src/metabase/driver/druid.clj b/modules/drivers/druid/src/metabase/driver/druid.clj
index 9f4dc39a642623d98394666fe4e7eefd233ecd44..906ed8441ecec55df05574460e06797d81d3aff3 100644
--- a/modules/drivers/druid/src/metabase/driver/druid.clj
+++ b/modules/drivers/druid/src/metabase/driver/druid.clj
@@ -83,7 +83,7 @@
         (if-not query-id
           (log/warn interrupted-ex "Client closed connection, no queryId found, can't cancel query")
           (ssh/with-ssh-tunnel [details-with-tunnel details]
-            (log/warnf "Client closed connection, cancelling Druid queryId '%s'" query-id)
+            (log/warnf "Client closed connection, canceling Druid queryId '%s'" query-id)
             (try
               ;; If we can't cancel the query, we don't want to hide the original exception, attempt to cancel, but if
               ;; we can't, we should rethrow the InterruptedException, not an exception from the cancellation
diff --git a/modules/drivers/presto/src/metabase/driver/presto.clj b/modules/drivers/presto/src/metabase/driver/presto.clj
index 349f0add4cb4a0d8125e579a163a27bf83b24282..74e9dbd426a9c1c8001096646ff94c4212ba46c4 100644
--- a/modules/drivers/presto/src/metabase/driver/presto.clj
+++ b/modules/drivers/presto/src/metabase/driver/presto.clj
@@ -140,7 +140,7 @@
                     ;; If we fail to cancel the query, log it but propogate the interrupted exception, instead of
                     ;; covering it up with a failed cancel
                     (catch Exception e
-                      (log/error e (trs "Error cancelling query with ID {0}" id))))
+                      (log/error e (trs "Error canceling query with ID {0}" id))))
                   (log/warn (trs "Client connection closed, no query-id found, can't cancel query")))
                 ;; Propogate the error so that any finalizers can still run
                 (throw e)))))))))
diff --git a/src/metabase/async/util.clj b/src/metabase/async/util.clj
index 4a7e671038b344b85cd9a30a3da5e48fce11befd..552e0035543443f90a46ba07c126e40a132375ef 100644
--- a/src/metabase/async/util.clj
+++ b/src/metabase/async/util.clj
@@ -11,8 +11,8 @@
   like.
 
   Returns a channel that will send a single message when such early-closing cancelation occurs. You can listen for
-  this message to implement special cancelation behavior, such as canceling async jobs. This channel automatically
-  closes when either `in-chan` or `out-chan` closes."
+  this message to implement special cancelation/close behavior, such as canceling async jobs. This channel
+  automatically closes when either `in-chan` or `out-chan` closes."
   [in-chan :- ManyToManyChannel, out-chan :- ManyToManyChannel]
   (let [canceled-chan (a/chan 1)]
     ;; fire off a block that will wait for either in-chan to produce a result or out-chan to be closed
diff --git a/src/metabase/driver/sql_jdbc/execute.clj b/src/metabase/driver/sql_jdbc/execute.clj
index 4fa65c7861ca14ff57386297d99abb83ae4d82c6..8a86ac8687c3a918e210c80cb4542eb77948c8c4 100644
--- a/src/metabase/driver/sql_jdbc/execute.clj
+++ b/src/metabase/driver/sql_jdbc/execute.clj
@@ -182,7 +182,7 @@
           @query-future)
         (catch InterruptedException e
           (log/warn e (tru "Client closed connection, cancelling query"))
-          ;; This is what does the real work of cancelling the query. We aren't checking the result of
+          ;; This is what does the real work of canceling the query. We aren't checking the result of
           ;; `query-future` but this will cause an exception to be thrown, saying the query has been cancelled.
           (.cancel stmt)
           (throw e))))))
diff --git a/src/metabase/middleware/auth.clj b/src/metabase/middleware/auth.clj
index e3bcfe8c2edaf0982fde649dcfb411b410335bba..5f63a95f36983a2edd9de25e24dc81d68de99c37 100644
--- a/src/metabase/middleware/auth.clj
+++ b/src/metabase/middleware/auth.clj
@@ -28,7 +28,7 @@
 
 
 (defn enforce-api-key
-  "Middleware that enforces validation of the client via API Key, cancelling the request processing if the check fails.
+  "Middleware that enforces validation of the client via API Key, canceling the request processing if the check fails.
 
   Validation is handled by first checking for the presence of the `:metabase-api-key` on the request.  If the api key
   is available then we validate it by checking it against the configured `:mb-api-key` value set in our global config.