Clarify why you might not use the starter parent

Update reference documentation to make it clearer why you might not
always want to use the spring-boot-starter-parent.

Fixes gh-774

spring-boot-docs/src/main/asciidoc/getting-started.adoc

@@ -147,6 +147,12 @@ endif::[]
 	</project>
 ----
 
+TIP: The `spring-boot-starter-parent` is a great way to use Spring Boot, but it might
+not be suitable all of the time. Sometimes you may need to inherit from a different
+parent POM, or you might just not like our default settings. See
+<<using-boot-maven-without-a-parent>> for an alternative solution that uses an `import`
+scope.
+
 
 
 [[getting-started-gradle-installation]]

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

@@ -64,11 +64,15 @@ If you import additional starters, you can safely omit the version number.
 
 
 
-[[using-boot-maven-your-own-parent]]
-==== Using your own parent POM
-If you don't want to use the Spring Boot starter parent, you can use your own and still
-keep the benefit of the dependency management (but not the plugin management) using a
-`scope=import` dependency:
+[[using-boot-maven-without-a-parent]]
+==== Using Spring Boot without the parent POM
+No everyone likes inheriting from the `spring-boot-starter-parent` POM. You may have your
+own corporate standard parent that you need to use, or you may just prefer to explicitly
+declare all your Maven configuration.
+
+If you don't want to use the `spring-boot-starter-parent`, you can still keep the benefit
+of the dependency management (but not the plugin management) by using a `scope=import`
+dependency:
 
 [source,xml,indent=0,subs="verbatim,quotes,attributes"]
 ----