Fix pom/gradle extracts to have the right artifactId

_includes/build.gradle

@@ -8,7 +8,7 @@ apply plugin: "io.spring.dependency-management"
 
 dependencyManagement {
   imports {
-    mavenBom '{@= groupId @}:{@= artifactId @}:{@= version @}'
+    mavenBom '{@= groupId @}:spring-cloud-starter-parent:{@= version @}'
   }
 }
 

_includes/pom.xml

@@ -1,6 +1,6 @@
 <parent>
     <groupId>{@= groupId @}</groupId>
-    <artifactId>{@= artifactId @}</artifactId>
+    <artifactId>spring-cloud-starter-parent</artifactId>
     <version>{@= version @}</version>
 </parent>
 <dependencies>

index.html

@@ -96,9 +96,12 @@ a critical mass, or if there is a critical bug in one of them that needs to be a
 the release train will push out "service releases" with names ending ".SRX", where "X"
 is a number.
 
-To use Spring Cloud in a traditional Java or Groovy project using
-Maven or Gradle, you can use the BOM only for dependency management or as a parent POM (Maven
-only). Example using the latest version with the config client and eureka (change the 
+The release train label is actually only used
+explicitly in one artifact: "spring-cloud-starter-parent" (all the
+others have normal "Spring" release labels tied to their parent
+project). The starter parent is the one you can use as a BOM for
+dependency management or as a parent POM (Maven only). Example using
+the latest version with the config client and eureka (change the
 artifact ids to pull in other starters):
 
 {% include download_widget.md %}