From dbfceddb83ec2f351fcf4ad5f45acd5422e2fd17 Mon Sep 17 00:00:00 2001 From: John Blum Date: Tue, 15 Jun 2021 11:24:31 -0700 Subject: [PATCH] Edit and revise wording in the Apache Geode API Extensions chapter of the Reference Documentation. --- .../docs/asciidoc/_includes/geode-api-ext.adoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 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 74e1d4f5..8a01cee3 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 @@ -5,18 +5,18 @@ The Spring Boot for {geode-name} (SBDG) project includes the `org.springframework.geode:apache-geode-extensions` module -to make the use of {geode-name} {apache-geode-javadoc}[APIs] in a Spring and non-Spring application context more +to make use of the {geode-name} {apache-geode-javadoc}[APIs] in a Spring and non-Spring application context more effective. While this module is relatively new, it contains several, necessary API extensions already. -The {geode-name} {apache-geode-javadoc}[API] is quite complex and difficult to use properly, especially without prior +{geode-name} {apache-geode-javadoc}[APIs] are quite complex and difficult to use properly, especially without prior knowledge or experience to do so. Users very often get things wrong and is the main reason why Spring's APIs -for {geode-name} are invaluable; they lead users to do the right thing, first and foremost, to begin with! +for {geode-name} are invaluable; they lead users to do the right thing from the start, first and foremost. -However, this module and its extensions do not simply exist to only 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, e.g. like when using -the Spring Cache Abstraction for caching or the the Spring Data Repository abstraction for DAO developement. This module -exists and is necessary primarily because it enables Spring for {geode-name} in many capacities do what it needs to do -along with working around the complexities and limitations of {geode-name} APIs in a Spring and application context. +However, this module does not simply 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, e.g. like when using the Spring Cache +Abstraction for caching or the Spring Data Repository abstraction for DAO development. This module is necessary +to enable Spring for {geode-name} to overcome and adapt to the limitations the API in a Spring and application context +in order to do what Spring for {geode-name} needs to do that makes the experience familiar to Spring users. In general, Spring shields users from design problems as well as changes in 3rd party library APIs, which could adversely affect your Spring applications when integrating with these libraries. Spring's APIs provide a layer of