From dcd0f743646a13ce9f71a9541014e97f9b56e4b7 Mon Sep 17 00:00:00 2001 From: Jay Bryant Date: Thu, 25 Jun 2020 15:12:07 -0500 Subject: [PATCH] Wording change Changed "executs" to the more friendly "runs". --- src/main/asciidoc/reference/data-solr.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/reference/data-solr.adoc b/src/main/asciidoc/reference/data-solr.adoc index de7d650ca..a8cb5663e 100644 --- a/src/main/asciidoc/reference/data-solr.adoc +++ b/src/main/asciidoc/reference/data-solr.adoc @@ -349,7 +349,7 @@ Page findByNameLike(Collection name); [[solr.query-methods.at-query]] === Using the `@Query` Annotation -Using named queries (see "`<>`") to declare queries for entities is a valid approach and works fine for a small number of queries. As the queries themselves are tied to the Java method that executes them, you actually can bind them directly by using the Spring Data Solr `@Query` annotation. The following example uses the `@Query` annotation to declare a query: +Using named queries (see "`<>`") to declare queries for entities is a valid approach and works fine for a small number of queries. As the queries themselves are tied to the Java method that runs them, you actually can bind them directly by using the Spring Data Solr `@Query` annotation. The following example uses the `@Query` annotation to declare a query: .Declare query at the method using the `@Query` annotation. ====