Clarify documentation on how to trigger a restart with Dev Tools

Closes gh-4679

spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc

@@ -943,14 +943,13 @@ on the classpath change. This can be a useful feature when working in an IDE as
 a very fast feedback loop for code changes. By default, any entry on the classpath that
 points to a folder will be monitored for changes.
 
-.Triggering a change
+.Triggering a restart
 ****
-As DevTools _only_ monitors classpath resources, the only way to trigger a change is to
+As DevTools _only_ monitors classpath resources, the only way to trigger a restart is to
-update the classpath. On Eclipse, saving is actually updating the project, compiling or
+update the classpath. In Eclipse, saving a modified file triggers an increment build which
-copying resources for you as part of the save action. If you are using IntelliJ IDEA,
+updates the classpath automatically. If you are using IntelliJ IDEA, you will have to
-there is no such thing as a save action since the resources are saved automatically.
+manually run a build using `Build` -> `Make Project`. This will update the classpath and
-IntelliJ IDEA users should use the `Build` -> `Make Project` action to achieve the same
+trigger a restart.
-result.
 ****
 
 NOTE: You can also start your application via the supported build plugins (i.e. Maven and