Polish asciidoctor links

Update `<<..>>` links to include the page.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/anchor-rewrite.properties

@@ -74,6 +74,8 @@ using-boot-devtools-customizing-classload=using.devtools.restart.customizing-the
 using-boot-devtools-known-restart-limitations=using.devtools.restart.limitations
 using-boot-devtools-livereload=using.devtools.livereload
 using-boot-devtools-globalsettings=using.devtools.globalsettings
+using-spring-boot-restart-vs-reload=using.devtools.restart.restart-vs-reload
+
 configuring-file-system-watcher=using.devtools.globalsettings.configuring-file-system-watcher
 using-boot-devtools-remote=using.devtools.remote-applications
 running-remote-client-application=using.devtools.remote-applications.client

spring-boot-project/spring-boot-docs/src/docs/asciidoc/io/caching.adoc

@@ -22,7 +22,7 @@ Otherwise, the method is invoked, and the cache is updated before returning the
 CAUTION: You can also use the standard JSR-107 (JCache) annotations (such as `@CacheResult`) transparently.
 However, we strongly advise you to not mix and match the Spring Cache and JCache annotations.
 
-If you do not add any specific cache library, Spring Boot auto-configures a <<io.caching.provider.simple,simple provider>> that uses concurrent maps in memory.
+If you do not add any specific cache library, Spring Boot auto-configures a <<io#io.caching.provider.simple,simple provider>> that uses concurrent maps in memory.
 When a cache is required (such as `piDecimals` in the preceding example), this provider creates it for you.
 The simple provider is not really recommended for production usage, but it is great for getting started and making sure that you understand the features.
 When you have made up your mind about the cache provider to use, please make sure to read its documentation to figure out how to configure the caches that your application uses.
@@ -39,18 +39,18 @@ The cache abstraction does not provide an actual store and relies on abstraction
 
 If you have not defined a bean of type `CacheManager` or a `CacheResolver` named `cacheResolver` (see {spring-framework-api}/cache/annotation/CachingConfigurer.html[`CachingConfigurer`]), Spring Boot tries to detect the following providers (in the indicated order):
 
-. <<io.caching.provider.generic,Generic>>
-. <<io.caching.provider.jcache,JCache (JSR-107)>> (EhCache 3, Hazelcast, Infinispan, and others)
-. <<io.caching.provider.ehcache2,EhCache 2.x>>
-. <<io.caching.provider.hazelcast,Hazelcast>>
-. <<io.caching.provider.infinispan,Infinispan>>
-. <<io.caching.provider.couchbase,Couchbase>>
-. <<io.caching.provider.redis,Redis>>
-. <<io.caching.provider.caffeine,Caffeine>>
-. <<io.caching.provider.simple,Simple>>
+. <<io#io.caching.provider.generic,Generic>>
+. <<io#io.caching.provider.jcache,JCache (JSR-107)>> (EhCache 3, Hazelcast, Infinispan, and others)
+. <<io#io.caching.provider.ehcache2,EhCache 2.x>>
+. <<io#io.caching.provider.hazelcast,Hazelcast>>
+. <<io#io.caching.provider.infinispan,Infinispan>>
+. <<io#io.caching.provider.couchbase,Couchbase>>
+. <<io#io.caching.provider.redis,Redis>>
+. <<io#io.caching.provider.caffeine,Caffeine>>
+. <<io#io.caching.provider.simple,Simple>>
 
 TIP: It is also possible to _force_ a particular cache provider by setting the configprop:spring.cache.type[] property.
-Use this property if you need to <<io.caching.provider.none,disable caching altogether>> in certain environments (such as tests).
+Use this property if you need to <<io#io.caching.provider.none,disable caching altogether>> in certain environments (such as tests).
 
 TIP: Use the `spring-boot-starter-cache` "`Starter`" to quickly add basic caching dependencies.
 The starter brings in `spring-context-support`.

spring-boot-project/spring-boot-docs/src/docs/asciidoc/using/devtools.adoc

@@ -95,7 +95,7 @@ NOTE: DevTools needs to customize the `ResourceLoader` used by the `ApplicationC
 If your application provides one already, it is going to be wrapped.
 Direct override of the `getResource` method on the `ApplicationContext` is not supported.
 
-[[using-spring-boot-restart-vs-reload]]
+[[using.devtools.restart.restart-vs-reload]]
 .Restart vs Reload
 ****
 The restart technology provided by Spring Boot works by using two classloaders.
@@ -212,7 +212,7 @@ For IntelliJ IDEA, you can follow the https://www.jetbrains.com/help/idea/spring
 
 [[using.devtools.restart.customizing-the-classload]]
 ==== Customizing the Restart Classloader
-As described earlier in the <<using-spring-boot-restart-vs-reload>> section, restart functionality is implemented by using two classloaders.
+As described earlier in the <<using#using.devtools.restart.restart-vs-reload>> section, restart functionality is implemented by using two classloaders.
 For most applications, this approach works well.
 However, it can sometimes cause classloading issues.
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/web/servlet.adoc

@@ -631,7 +631,7 @@ JSPs are not supported when using an executable jar.
 
 * Undertow does not support JSPs.
 
-* Creating a custom `error.jsp` page does not override the default view for <<web.servlet.spring-mvc.error-handling,error handling>>.
-  <<web.servlet.spring-mvc.error-handling.error-pages,Custom error pages>> should be used instead.
+* Creating a custom `error.jsp` page does not override the default view for <<web#web.servlet.spring-mvc.error-handling,error handling>>.
+  <<web#web.servlet.spring-mvc.error-handling.error-pages,Custom error pages>> should be used instead.