From 054192b453840a1a0174562857cbdb8090780016 Mon Sep 17 00:00:00 2001 From: Jon Dufresne Date: Sat, 6 Jun 2026 09:34:43 -0700 Subject: [PATCH] Fix a couple typos in docs --- CHANGELOG.md | 2 +- README.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 164031c..91dc541 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -72,7 +72,7 @@ ### Features -* use current connnection instead of the one in ActiveRecord::Base ([#90](https://github.com/ClosureTree/with_advisory_lock/issues/90)) ([c28a172](https://github.com/ClosureTree/with_advisory_lock/commit/c28a172a5a64594448b6090501fc0b8cbace06f6)) +* use current connection instead of the one in ActiveRecord::Base ([#90](https://github.com/ClosureTree/with_advisory_lock/issues/90)) ([c28a172](https://github.com/ClosureTree/with_advisory_lock/commit/c28a172a5a64594448b6090501fc0b8cbace06f6)) ### Bug Fixes diff --git a/README.md b/README.md index efad627..900ce33 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ called. > If a non-nil value is provided for `timeout_seconds`, the block will *not* be invoked if the lock cannot be acquired within that time-frame. In this case, `with_advisory_lock` will return `false`, while `with_advisory_lock!` will raise a `WithAdvisoryLock::FailedToAcquireLock` error. -For backwards compatability, the timeout value can be specified directly as the +For backwards compatibility, the timeout value can be specified directly as the second parameter. ### Shared locks @@ -194,4 +194,3 @@ You will want to wrap your block within a transaction to ensure consistency. ### Is clustered MySQL supported? [No.](https://github.com/ClosureTree/with_advisory_lock/issues/16) -