From 4b92383fe4121aa9e7a70b20ec24142e3bd62dee Mon Sep 17 00:00:00 2001
From: Kenichi Ishigaki <ishigaki@cpan.org>
Date: Sat, 18 Apr 2015 16:32:39 +0900
Subject: [PATCH] might be better to use the same word class to avoid confusion

---
 lib/DBD/SQLite.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/DBD/SQLite.pm b/lib/DBD/SQLite.pm
index 2d017cf..9a18362 100644
--- a/lib/DBD/SQLite.pm
+++ b/lib/DBD/SQLite.pm
@@ -1373,7 +1373,7 @@ operation, and thus it is possible that another thread or process
 could create a separate transaction and write to the database after
 the C<BEGIN> on the current thread has executed, and eventually
 cause a "deadlock". To avoid this, DBD::SQLite internally issues
-a C<BEGIN IMMEDIATE> if you begin a transaction by
+a C<BEGIN IMMEDIATE> if you begin a transaction by calling
 C<begin_work> or by turning off C<AutoCommit> (since 1.38_01).
 
 If you really need to turn off this feature for some reasons,