diff --git a/spring-geode-docs/src/docs/asciidoc/guides/boot-configuration.adoc b/spring-geode-docs/src/docs/asciidoc/guides/boot-configuration.adoc index d334d98d..ea4f0c79 100644 --- a/spring-geode-docs/src/docs/asciidoc/guides/boot-configuration.adoc +++ b/spring-geode-docs/src/docs/asciidoc/guides/boot-configuration.adoc @@ -16,7 +16,7 @@ to manage Customer interactions. You should already be familiar with Spring Boot By the end of this lesson, you should have a better understanding of what Spring Boot for Apache Geode's (SBDG) _auto-configuration_ support actually does. -This guide compliments the link:../configuration-annotations.html[Auto-configuration vs. Annotation-based configuration] +This guide compliments the link:../index.html#geode-auto-configuration-annotations[Auto-configuration vs. Annotation-based configuration] chapter with concrete examples. Let's begin. @@ -365,7 +365,7 @@ The client is expecting there to be a cluster of servers to communicate with and are no servers running yet. There are several ways in which to start a cluster. For example, you may use Spring to configure and bootstrap -the cluster, which has been demonstrated link:../appendix.html#geode-cluster-configuration-bootstrapping[here]. +the cluster, which has been demonstrated link:../index.html#geode-cluster-configuration-bootstrapping[here]. Although, for this example, we are going to use the tools provided with Apache Geode, or Pivotal GemFire, i.e. _Gfsh_ (GemFire/Geode Shell) for reasons that will become apparent later. @@ -1041,7 +1041,7 @@ Caused by: org.apache.geode.security.AuthenticationRequiredException: Server exp ---- With very minimal to no configuration, SBDG can automatically configure SSL, as explained in -link:../security.html#geode-security-ssl[Transport Layer Security using SSL] section under Security. In fact, +link:../index.html#geode-security-ssl[Transport Layer Security using SSL] section under Security. In fact, no configuration is actually required if the trusted Java KeyStore file is named "trusted.keystore", is in the root of the classpath and the JKS file is unsecured, i.e. not protected by a password. diff --git a/spring-geode-docs/src/docs/asciidoc/guides/caching-inline.adoc b/spring-geode-docs/src/docs/asciidoc/guides/caching-inline.adoc index e8edb9f1..55222ebc 100644 --- a/spring-geode-docs/src/docs/asciidoc/guides/caching-inline.adoc +++ b/spring-geode-docs/src/docs/asciidoc/guides/caching-inline.adoc @@ -254,7 +254,7 @@ The Region may already exist and have been created some other way. Either way, these Regions for you. TIP: If you have not done so already, you should definitely read about SBDG's support for _Inline Caching_ -in the link:../caching.html#geode-caching-provider-inline-caching[]. +in the link:../index.html#geode-caching-provider-inline-caching[Inline Caching] section. TIP: To learn more about how Apache Geode's (or Pivotal GemFire's) data loading functionality works, or specifically, how to {apache-geode-docs}/developing/outside_data_sources/sync_outside_data.html["Keep the Cache in Sync with Outside diff --git a/spring-geode-docs/src/docs/asciidoc/guides/caching-near.adoc b/spring-geode-docs/src/docs/asciidoc/guides/caching-near.adoc index cbde3d83..553f78a6 100644 --- a/spring-geode-docs/src/docs/asciidoc/guides/caching-near.adoc +++ b/spring-geode-docs/src/docs/asciidoc/guides/caching-near.adoc @@ -163,7 +163,7 @@ include::{samples-dir}/caching/near/src/main/java/example/app/caching/near/serve ---- TIP: For more information on configurating and bootstrapping a small cluster of Apache Geode servers using Spring Boot, -see link:../appendix.html#geode-cluster-configuration-bootstrapping[Running an Apache Geode or Pivotal GemFire Cluster using Spring Boot]. +see link:../index.html#geode-cluster-configuration-bootstrapping[Running an Apache Geode or Pivotal GemFire Cluster using Spring Boot]. [[geode-samples-caching-near-example-client-side]] === Client-side Configuration diff --git a/spring-geode-docs/src/docs/asciidoc/guides/getting-started.adoc b/spring-geode-docs/src/docs/asciidoc/guides/getting-started.adoc index b7277363..76d5fc3f 100644 --- a/spring-geode-docs/src/docs/asciidoc/guides/getting-started.adoc +++ b/spring-geode-docs/src/docs/asciidoc/guides/getting-started.adoc @@ -1488,7 +1488,7 @@ Please see https://run.pivotal.io/[Pivotal Web Services] (PWS) website for more TIP: Alternatively, you can run this example in a locally hosted _Pivotal Platform_ environment called https://docs.pivotal.io/pcf-dev/index.html[PCF Dev]. -See link:../cloudfoundry.html#cloudfoundry-geode[Hybrid Cloud Environments] for more details. +See link:../index.html#cloudfoundry-geode[Hybrid Cloud Environments] for more details. ***** Once you have acquired a _Pivotal Platform_ environment and installed the required tools (e.g. CF CLI), then you can @@ -1521,7 +1521,7 @@ To: ---- -TIP: See the link:../appendix.html#geode-gemfire-switch[Appendix] for more details on making the switch. +TIP: See the link:../index.html#geode-gemfire-switch[Appendix] for more details on making the switch. .Acquiring Pivotal Cloud Cache Bits ***** @@ -1962,7 +1962,7 @@ Indeed, this is perhaps a crucial step in moving to the cloud, being able to mig applicable or possible to do so. You can find more information on running in a Hybrid Cloud Environment, -link:../cloudfoundry.html#cloudfoundry-geode[here]. +link:../index.html#cloudfoundry-geode[here]. [[spring-geode-samples-getting-started-summary]] == Summary