diff --git a/src/main/asciidoc/jdbc.adoc b/src/main/asciidoc/jdbc.adoc
index f61db854..7a4528a0 100644
--- a/src/main/asciidoc/jdbc.adoc
+++ b/src/main/asciidoc/jdbc.adoc
@@ -22,7 +22,7 @@ Also, things that are really simple conceptually get rather difficult with JPA.
 
 Spring Data JDBC aims to be much simpler conceptually, by embracing the following design decisions:
 
-* If you load an entity, SQL statements get executed.
+* If you load an entity, SQL statements get run.
 Once this is done, you have a completely loaded entity.
 No lazy loading or caching is done.
 
@@ -517,7 +517,7 @@ The instance can be modified by adding or removing {javadoc-base}/org/springfram
 
 Spring Data JDBC does little to no logging on its own.
 Instead, the mechanics of `JdbcTemplate` to issue SQL statements provide logging.
-Thus, if you want to inspect what SQL statements are executed, activate logging for Spring's {spring-framework-docs}/data-access.html#jdbc-JdbcTemplate[`NamedParameterJdbcTemplate`] or https://www.mybatis.org/mybatis-3/logging.html[MyBatis].
+Thus, if you want to inspect what SQL statements are run, activate logging for Spring's {spring-framework-docs}/data-access.html#jdbc-JdbcTemplate[`NamedParameterJdbcTemplate`] or https://www.mybatis.org/mybatis-3/logging.html[MyBatis].
 
 [[jdbc.transactions]]
 == Transactionality
@@ -540,7 +540,7 @@ public interface UserRepository extends CrudRepository<User, Long> {
 ----
 ====
 
-The preceding causes the `findAll()` method to be executed with a timeout of 10 seconds and without the `readOnly` flag.
+The preceding causes the `findAll()` method to be run with a timeout of 10 seconds and without the `readOnly` flag.
 
 Another way to alter transactional behavior is by using a facade or service implementation that typically covers more than one repository. Its purpose is to define transactional boundaries for non-CRUD operations. The following example shows how to create such a facade: