Skip to content

Fix typos in documentation #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 10, 2023
Merged

Fix typos in documentation #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/DatabaseInterface.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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;
* });
* ```
Expand Down Expand Up @@ -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();
Expand Down
2 changes: 1 addition & 1 deletion src/Factory.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down