From f9bd278269114e09c96a5c07499d55e4b1259755 Mon Sep 17 00:00:00 2001
From: Yada Clintjens <yada@clue.engineering>
Date: Mon, 6 Nov 2023 17:18:07 +0100
Subject: [PATCH] Fix typos in documentation

---
 src/DatabaseInterface.php | 4 ++--
 src/Factory.php           | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/DatabaseInterface.php b/src/DatabaseInterface.php
index 616abce..9b883e3 100644
--- a/src/DatabaseInterface.php
+++ b/src/DatabaseInterface.php
@@ -32,7 +32,7 @@
  *     The `close` event will be emitted once the connection closes (terminates).
  *
  *     ```php
- *     $connecion->on('close', function () {
+ *     $connection->on('close', function () {
  *         echo 'Connection closed' . PHP_EOL;
  *     });
  *     ```
@@ -173,7 +173,7 @@ public function quit();
      * Force-close the connection.
      *
      * Unlike the `quit()` method, this method will immediately force-close the
-     * connection and reject all oustanding commands.
+     * connection and reject all outstanding commands.
      *
      * ```php
      * $db->close();
diff --git a/src/Factory.php b/src/Factory.php
index decb998..8cf5284 100644
--- a/src/Factory.php
+++ b/src/Factory.php
@@ -159,7 +159,7 @@ public function open($filename, $flags = null)
      * From a consumer side this means that you can start sending queries to the
      * database right away while the underlying database process may still be
      * outstanding. Because creating this underlying process may take some
-     * time, it will enqueue all oustanding commands and will ensure that all
+     * time, it will enqueue all outstanding commands and will ensure that all
      * commands will be executed in correct order once the database is ready.
      * In other words, this "virtual" database behaves just like a "real"
      * database as described in the `DatabaseInterface` and frees you from