Draft for Spring Boot 3 WAR post

posts/2024-05-01-spring-boot-3.adoc

@@ -180,7 +180,7 @@ The server is configured with the https://openliberty.io/docs/latest/reference/f
 
 If you're wondering, yes, while a Spring Boot WAR must be repackaged as an executable WAR to use the optimized deployment, that executable WAR could still be deployed as a standard WAR.
 
-=== Build container image with efficient layering
+=== Part 3: Build container image with efficient layering
 
 Now that we have used the optimized Spring Boot deployment, we can efficiently build a container image.  This image uses an indexed cache at `/lib.index.cache` to store Spring Boot dependencies in their own layer, separate from your application code.
 
@@ -234,6 +234,6 @@ Though much of the programming model is the same across the two cases, there are
 (**Note:** the flow through Parts 1 and 2 of this blog post are a bit contrived to show the two deployment options, and your real development workflow would probably look a bit different. When using a traditional WAR deployment you would likely maintain your own `server.xml` file rather than continuing to use the template configuration. When using the optimized Liberty deployment there's no need to do a traditional deployment first.)
 
 == References
-* Clone the link:https://github.com/scottkurz/spring-liberty[repository](https://github.com/scottkurz/spring-liberty) with the finished code for the sample app in this blog.
+* Clone the link:https://github.com/scottkurz/spring-liberty[repository] with the finished code for the sample app in this blog.
 * Docs: link:https://openliberty.io/docs/latest/deploy-spring-boot.html[Configure and Deploy Spring Boot applications to Open Liberty]   
 * Guide: link:https://openliberty.io/guides/spring-boot.html[Containerizing, packaging, and running a Spring Boot application]