From 3a63179d81403905b07a84a90d6355ea8796d558 Mon Sep 17 00:00:00 2001 From: Johnny Lim Date: Fri, 20 Sep 2019 11:52:18 +0900 Subject: [PATCH] Fix a broken Asciidoctor syntax Along the way, this commit also fixes a typo. Closes gh-18325 --- .../src/main/asciidoc/spring-boot-features.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index 2fa5a0e97bc..13612887cfc 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -5674,8 +5674,8 @@ Testing within a mocked environment is usually faster than running with a full S However, since mocking occurs at the Spring MVC layer, code that relies on lower-level Servlet container behavior cannot be directly tested with MockMvc. For example, Spring Boot's error handling is based on the "`error page`" support provided by the Servlet container. -This means that, whilst you can test your MVC layer throws and handles exceptions as expected, you cannot directly test that a specific <<#boot-features-error-handling-custom-error-pages, custom error page>> is rendered. -If you need to tests these lower-level concerns, you can start a fully running server as described in the next section. +This means that, whilst you can test your MVC layer throws and handles exceptions as expected, you cannot directly test that a specific <> is rendered. +If you need to test these lower-level concerns, you can start a fully running server as described in the next section. ====