From e7097844dc7e59d7171d8b107566d82012ffd7ea Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Fri, 20 Oct 2017 17:31:28 +0200 Subject: [PATCH] Polish --- spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc index b189c915dfc..9c956266a0f 100644 --- a/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc +++ b/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc @@ -6045,7 +6045,7 @@ for it. Your could define your `@SpringBootApplication` as follows: ---- Because this class is the source configuration for the test, any slice test will actually -attempt to start Spring Batch, which is definitely now what you want to do. A recommended +attempt to start Spring Batch, which is definitely not what you want to do. A recommended approach is to move that area-specific configuration to a separate `@Configuration` class at the same level as your application. @@ -6074,7 +6074,7 @@ application may look like this: This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you've chosen. For instance a -`@DataJpaTest` will all the sudden scan components and user configurations of your +`@DataJpaTest` will all of a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue.