Edit Javadoc in the EnableClusterAware annotation.

Author: jxblum

spring-geode-project/spring-geode/src/main/java/org/springframework/geode/config/annotation/EnableClusterAware.java

@@ -56,17 +56,17 @@
 	 * before the cluster aware logic considers that a cluster actually exists.
 	 *
 	 * Previously, in cloud-managed environments (e.g. VMware Tanzu Application Service (TAS) for VMs, formerly known as
-	 * Pivotal Platform or Pivotal CloudFoundry (PCF), or Kubernetes, known as VMware Tanzu Application Service for K8S)
+	 * Pivotal Platform or Pivotal CloudFoundry (PCF), or Kubernetes, known as VMware Tanzu Application Platform for K8S)
 	 * it was assumed that a cluster would be provisioned and available, and that the Spring Boot, Apache Geode
 	 * {@link ClientCache} application would connect to the cluster on deployment (push).
 	 *
 	 * However, is entirely possible that users may push Spring Boot, Apache Geode {@link ClientCache} applications
-	 * to a cloud-managed environment where not cluster was provisioned and is available, and user simply want their
+	 * to a cloud-managed environment where no cluster was provisioned and is available, and users simply want their
 	 * apps to run in local-only mode.
 	 *
-	 * The strict match configuration setting absolutely requires that at least 1 connection must be established. Use
-	 * of this configuration setting also promotes a fail-fast protocol, or at least early detection (when log levels
-	 * are adjusted accordingly) that a cluster is not available.
+	 * The strict match configuration setting absolutely requires at least 1 connection must be established. Use of this
+	 * configuration setting also promotes a fail-fast protocol, or at least early detection (when log levels are
+	 * adjusted accordingly) that a cluster is not available.
 	 *
 	 * Use {@literal spring.boot.data.gemfire.cluster.condition.match.strict}
 	 * in Spring Boot {@literal application.properties}.