#1016 - Polishing.

Fixed link to the section on the EntityLinks interface from the section of the LinkRelationProvider documentation.
spring-projects · Jul 9, 2019 · 4c434aa · 4c434aa
1 parent 36d2e8c
commit 4c434aa
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/main/asciidoc/server.adoc b/src/main/asciidoc/server.adoc
@@ -493,6 +493,6 @@ When building links, you usually need to determine the relation type to be used
 . If the type is annotated with `@Relation`, we use the values configured in the annotation.
 . If not, we default to the uncapitalized simple class name plus an appended `List` for the collection `rel`.
 . If the https://github.com/atteo/evo-inflector[EVO inflector] JAR is in the classpath, we use the plural of the single resource `rel` provided by the pluralizing algorithm.
-. `@Controller` classes annotated with `@ExposesResourceFor` (see <<fundamentals.obtaining-links.entity-links>> for details) transparently look up the relation types for the type configured in the annotation, so that you can use `LinkRelationProvider.getItemResourceRelFor(MyController.class)` and get the relation type of the domain type exposed.
+. `@Controller` classes annotated with `@ExposesResourceFor` (see <<server.entity-links>> for details) transparently look up the relation types for the type configured in the annotation, so that you can use `LinkRelationProvider.getItemResourceRelFor(MyController.class)` and get the relation type of the domain type exposed.
 
 A `LinkRelationProvider` is automatically exposed as a Spring bean when you use `@EnableHypermediaSupport`. You can plug in custom providers by implementing the interface and exposing them as Spring beans in turn.