From d2e2f24ccbe1739ac4b7ccea304dc40708431d29 Mon Sep 17 00:00:00 2001 From: John Blum Date: Tue, 15 Jun 2021 17:18:28 -0700 Subject: [PATCH] Polish to the edits in Chapter 19 - Apache Geode API Extentions. Resolves gh-106. --- .../src/docs/asciidoc/_includes/geode-api-ext.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-geode-docs/src/docs/asciidoc/_includes/geode-api-ext.adoc b/spring-geode-docs/src/docs/asciidoc/_includes/geode-api-ext.adoc index d49f15d3..23f97e05 100644 --- a/spring-geode-docs/src/docs/asciidoc/_includes/geode-api-ext.adoc +++ b/spring-geode-docs/src/docs/asciidoc/_includes/geode-api-ext.adoc @@ -9,8 +9,8 @@ to make use of the {geode-name} {apache-geode-javadoc}[APIs] in a Spring and non effective. While this module is relatively new, it already contains several necessary API extensions. {geode-name} {apache-geode-javadoc}[APIs] can be complex and difficult to use properly, especially without prior -knowledge or experience. Users often get things wrong, which is why Spring's APIs -for {geode-name} are invaluable. They lead users to do the right thing from the start, first and foremost. +knowledge or experience. Users often get things wrong, which is why Spring's APIs for {geode-name} are invaluable. +They lead users to do the right thing from the start, first and foremost. However, this module does not exist only to help users use {geode-name}'s APIs more effectively. In fact, with Spring's abstractions, it should not be necessary to use {geode-name} APIs at all -- for example, when using the Spring Cache