diff -u b/core/modules/dblog/src/Logger/DbLog.php b/core/modules/dblog/src/Logger/DbLog.php
--- b/core/modules/dblog/src/Logger/DbLog.php
+++ b/core/modules/dblog/src/Logger/DbLog.php
@@ -84,7 +84,7 @@
         ->execute();
     }
     catch (\Exception $e) {
-      // When running Drupal on MySQL or Maria DB you can run in several errors
+      // When running Drupal on MySQL or MariaDB you can run into several errors
       // that corrupt the database connection. Some examples for these kind of
       // errors on the database layer are "1100 - Table 'xyz' was not locked
       // with LOCK TABLES" and "1153 – Got a packet bigger than
diff -u b/core/modules/dblog/src/Tests/ConnectionFailureTest.php b/core/modules/dblog/src/Tests/ConnectionFailureTest.php
--- b/core/modules/dblog/src/Tests/ConnectionFailureTest.php
+++ b/core/modules/dblog/src/Tests/ConnectionFailureTest.php
@@ -11,7 +11,7 @@
 use Drupal\simpletest\WebTestBase;
 
 /**
- * Tests loging of connection failures.
+ * Tests logging of connection failures.
  *
  * @group dblog
  */
@@ -20,14 +20,14 @@
   public static $modules = array('dblog');
 
   /**
-   * Tests loging of connection failures.
+   * Tests logging of connection failures.
    */
   function testConnectionFailureLogging() {
     $logger = \Drupal::service('logger.factory');
 
-    // MySQL erros like "1153 – Got a packet bigger than ‘max_allowed_packet’
+    // MySQL errors like "1153 – Got a packet bigger than ‘max_allowed_packet’
     // bytes" or "1100 - Table 'xyz' was not locked with LOCK TABLES" lead to a
-    // database connection unusable for further request. All further request
+    // database connection unusable for further requests. All further request
     // will result in an "2006 - MySQL server had gone away" error. As a
     // consequence it's impossible to use this connection to log the causing
     // initial error itself. Using Database::closeConnection() we simulate such