diff --git a/docs/for-app-developers/how-to/build-outputs/specify-launch-process/index.html b/docs/for-app-developers/how-to/build-outputs/specify-launch-process/index.html
index d82541d3a..40c684d91 100644
--- a/docs/for-app-developers/how-to/build-outputs/specify-launch-process/index.html
+++ b/docs/for-app-developers/how-to/build-outputs/specify-launch-process/index.html
@@ -931,14 +931,14 @@ Build a multi-process app
Buildpacks:
ID VERSION HOMEPAGE
- samples/java-maven 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven
+ samples/java-maven 0.0.2 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven
samples/hello-processes 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/hello-process
Processes:
TYPE SHELL COMMAND ARGS
web (default) bash java -jar target/sample-0.0.1-SNAPSHOT.jar
sys-info bash /layers/samples_hello-processes/sys-info/sys-info.sh
-Notice that the default process type is web. This is because pack will always attempt to set the default process type to web unless the --default-process flag is passed.
+
Notice that the java-maven buildpack defined web as the default process type.
If we had run the pack build command above with --default-process sys-info, sys-info would be the default process for the app image!
Run a multi-process app
Buildpacks are designed to give you much flexibility in how you run your app. The lifecycle includes a binary called the launcher which is present in the final app image and is responsible for starting your app.
diff --git a/index.html b/index.html
index 583b36e4e..c67e5f64f 100644
--- a/index.html
+++ b/index.html
@@ -2,7 +2,7 @@
-
+