From 012a956454c8492fc00de05d0b750473daf771d6 Mon Sep 17 00:00:00 2001 From: Madhura Bhave Date: Thu, 14 Feb 2019 19:39:01 -0800 Subject: [PATCH] Fix typo in doc --- .../spring-boot-maven-plugin/src/site/apt/usage.apt.vm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm b/spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm index 2ba3a153df..dd3b4c99f7 100644 --- a/spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm +++ b/spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm @@ -62,7 +62,7 @@ Usage Devtools is automatically excluded by default (you can control that using the <<>> property). In order to make that work with <<>> packaging, - the `spring-boot-devtools` dependency must be set as <<>> or with the + the <<>> dependency must be set as <<>> or with the <<>> scope. The original (i.e. non executable) artifact is renamed to <<<.original>>> by default but it is also @@ -219,7 +219,7 @@ spring.devtools.remote.restart.enabled=false * Working with integration tests While you may start your Spring Boot application very easily from your test (or test suite) itself, - it may be desirable to handle that in the build itself. To make sure that the lifecycle of you Spring + it may be desirable to handle that in the build itself. To make sure that the lifecycle of your Spring Boot application is properly managed your integration tests, you can use the <<>> and <<>> goals as described below: