Replace all references to Pivotal GemFire with VMware Tanzu GemFire.

CONTRIBUTING.adoc

@@ -1,6 +1,6 @@
-= Contributing to Spring Session for Apache Geode & Pivotal GemFire
+= Contributing to Spring Session for Apache Geode & VMware Tanzu GemFire
 
-Spring Session for Apache Geode & Pivotal GemFire is released under the Apache 2.0 license. If you would like to
+Spring Session for Apache Geode & VMware Tanzu GemFire is released under the Apache 2.0 license. If you would like to
 contribute something, or simply want to hack on the code this document should help you get started.
 
 == Sign the Contributor License Agreement

README.adoc

@@ -19,8 +19,8 @@ in a neutral way along with providing HTTP Session IDs in the HTTP Header to wor
 
 * `WebSocket` - keeps the `HttpSession` active when receiving WebSocket messages.
 
-On top of the core _Spring Session_ features, _Spring Session for Apache Geode and Pivotal GemFire_ (SSDG) positions
-either https://geode.apache.org/[Apache Geode] or https://pivotal.io/pivotal-gemfire[Pivotal GemFire]
+On top of the core _Spring Session_ features, _Spring Session for Apache Geode and VMware Tanzu GemFire_ (SSDG)
+positions either https://geode.apache.org/[Apache Geode] or https://pivotal.io/pivotal-gemfire[VMware Tanzu GemFire]
 as a session repository provider and adds additional capabilities required by enterprise class solutions:
 
 * Custom `Expiration Policies` - in addition to the default, 30 minute session _idle expiration timeout_ (TTI), which
@@ -46,18 +46,18 @@ and use that to determine if your application domain objects are indeed dirty be
 implement the `Delta` interface, or the object is not the same, then it functions like all other Spring Session providers.
 If you prefer, you may specify your own rules composed with the `IsDirtyPredicate` strategy interface.
 
-* Powerful `Pub/Sub` - Apache Geode and Pivotal GemFire both provide a very powerful and robust client/server
+* Powerful `Pub/Sub` - Apache Geode and VMware Tanzu GemFire both provide a very powerful and robust client/server
 https://geode.apache.org/docs/guide/{geode-version}/developing/events/chapter_overview.html[event distribution and handling sub-system]
 leveraged by SSDG in order to reliably manage session state, especially in a distributed/clustered environment.
 
-These and many more Apache Geode or Pivotal GemFire features may be leveraged in your application environment to
+These and many more Apache Geode or VMware Tanzu GemFire features may be leveraged in your application environment to
 achieve resilient, highly available (HA), durable, consistent, and even multi-clustered (WAN), persistent
 session statement management.
 
-The best part, SSDG allows you to use either Apache Geode or Pivotal GemFire interchangeably without having to change
+The best part, SSDG allows you to use either Apache Geode or VMware Tanzu GemFire interchangeably without having to change
 a single line of code.  Simply change your dependency from `org.springframework.session:spring-session-data-geode`
 to `org.springframework.session:spring-session-data-gemfire`, or vice versa, and you can seemlessly move between
-either Apache Geode or Pivotal GemFire, or even PCC.
+either Apache Geode or VMware Tanzu GemFire, or even PCC.
 
 No other Spring Session provider offers you the same type of flexibility and power in 1 solution, especially as
 your requirements and UC change (e.g. from simple session caching to a full on _System of Record_ with
@@ -70,7 +70,7 @@ You can find the documentation, issue management, support, samples, and guides f
 at https://projects.spring.io/spring-session/.
 
 Additionally, you can find documentation, issue management, support, samples and guides using _Spring Session
-for Apache Geode & Pivotal GemFire_ at https://spring.io/projects/spring-session-data-geode.
+for Apache Geode & VMware Tanzu GemFire_ at https://spring.io/projects/spring-session-data-geode.
 
 [[documentation]]
 === Documentation

docs/src/docs/asciidoc/guides/boot-gemfire-with-scoped-proxies.adoc

@@ -25,7 +25,7 @@ to process client HTTP requests.
 This sample is based on a https://stackoverflow.com/questions/45674137/can-session-scope-beans-be-used-with-spring-session-and-gemfire[_StackOverflow_ post],
 which posed the following question...
 
-> _Can session scope beans be used with Spring Session and Pivotal GemFire?_
+> _Can session scope beans be used with Spring Session and VMware Tanzu GemFire?_
 
 The poster of the question when on to state and ask...
 
@@ -70,7 +70,7 @@ If you are using _Maven_, include the following `dependencies` in your `pom.xml`
 </dependencies>
 ----
 
-NOTE: If you are using Pivotal GemFire instead of Apache Geode, you may substitute the `spring-session-data-gemfire`
+NOTE: If you are using VMware Tanzu GemFire instead of Apache Geode, you may substitute the `spring-session-data-gemfire`
 artifact for `spring-session-data-geode`.
 
 ifeval::["{version-snapshot}" == "true"]
@@ -174,7 +174,7 @@ in the Apache Geode User Guide.
 
 NOTE: For more information on configuring _Spring Data for Apache Geode_, refer to the {sdg-docs}[Reference Guide].
 
-==== Enabling Pivotal GemFire HttpSession Management
+==== Enabling VMware Tanzu GemFire HttpSession Management
 
 The `@EnableGemFireHttpSession` annotation enables developers to configure certain aspects of both Spring Session
 and Apache Geode out-of-the-box using the following attributes:

docs/src/docs/asciidoc/guides/xml-gemfire-clientserver.adoc

@@ -102,7 +102,7 @@ include::{samples-dir}xml/gemfire-clientserver/src/main/webapp/WEB-INF/spring/se
 ----
 
 <1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode `ClientCache`
-using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
+using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
 setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
 if unspecified.
 <2> We must create an instance of an Apache Geode `ClientCache`.  We initialize it with our `gemfireProperties`.
@@ -134,7 +134,7 @@ include::{samples-dir}xml/gemfire-clientserver/src/main/resources/META-INF/sprin
 ----
 
 <1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode peer `Cache`
-using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
+using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
 setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
 if unspecified.
 <2> We must configure an Apache Geode peer `Cache` instance. We initialize it with the Apache Geode properties.

docs/src/docs/asciidoc/guides/xml-gemfire-p2p.adoc

@@ -103,7 +103,7 @@ include::{samples-dir}xml/gemfire-p2p/src/main/webapp/WEB-INF/spring/session.xml
 ----
 
 <1> (Optional) First, we can include a `Properties` bean to configure certain aspects of the Apache Geode peer `Cache`
-using {data-store-docs}/reference/topics/gemfire_properties.html[Pivotal GemFire Properties]. In this case, we are just
+using {data-store-docs}/reference/topics/gemfire_properties.html[VMware Tanzu GemFire Properties]. In this case, we are just
 setting Apache Geode's "`log-level`" using an application-specific System property, defaulting to "`warning`"
 if unspecified.
 <2> We must configure an Apache Geode peer `Cache` instance. We initialize it with the Apache Geode properties.

etc/build-notes.adoc

@@ -1,5 +1,5 @@
 [[build-notes]]
-= Gradle Build Notes for Spring Session for Apache Geode & Pivotal GemFire (SSDG)
+= Gradle Build Notes for Spring Session for Apache Geode & VMware Tanzu GemFire (SSDG)
 
 This document contains notes on running specific Gradle (i.e. `gradlew`) build tasks.