2nd draft of 26.0.0.5 GA blog

Author: navaneethsnair1

posts/2026-05-19-26.0.0.5.adoc

@@ -6,8 +6,8 @@ categories: blog
 author_picture: https://avatars3.githubusercontent.com/navaneethsnair1
 author_github: https://github.com/navaneethsnair1
 seo-title: Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5- OpenLiberty.io
-seo-description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats.
-blog_description: This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats.
+seo-description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
+blog_description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
 open-graph-image: https://openliberty.io/img/twitter_card.jpg
 open-graph-image-alt: Open Liberty Logo
 ---
@@ -49,7 +49,7 @@ Navaneeth S Nair <https://github.com/navaneethsnair1>
 // change the "IMAGE CAPTION" to a couple words of what the image is
 // // // // // // // //
 
-This release adds support for Jakarta EE 11 and Spring Boot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying Spring Boot 4.x applications in both JAR and WAR formats.
+This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
 
 // // // // // // // //
 // In the preceding section:
@@ -161,9 +161,9 @@ image::img/blog/blog_btn_stack.svg[Ask a question on Stack Overflow, align="cent
 
 Jakarta EE 11 Core Profile, Web Profile and Platform are now officially supported in Open Liberty! We’d like to start by thanking all those who provided feedback throughout our various betas.
 
-Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing spJavaecifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features.
+Jakarta EE 11 marks a major milestone. It is the first Jakarta release to add a new specification to the platform since Java EE 8 in 2017 and, therefore, the first to provide a new component specification since the platform was taken over by the Eclipse Foundation. Among the many updates to existing Java specifications, it also removes all optional specifications and functions from the Platform. Liberty continues to support those optional specifications and functions when combined with Jakarta EE 11 features.
 
-The Core Profile specification was introduced in Jakarta EE 10 to provide a profile for lightweight cloud native applications such as MicroProfile-based applications.  With the introduction of Jakarta EE 11 support in this release, the MicroProfile 7.0 and 7.1 features also now work with Jakarta EE 11 so that you can run your MicroProfile 7 applications using either Jakarta EE 10 or Jakarta EE 11 features.
+The Core Profile specification was introduced in Jakarta EE 10 to provide a profile for lightweight cloud native applications such as MicroProfile-based applications.  With the introduction of Jakarta EE 11 support in this release, the MicroProfile 7.0 and 7.1 features also now work with Jakarta EE 11. You can run your MicroProfile 7 applications using either Jakarta EE 10 or Jakarta EE 11 features.
 
 The following specifications make up the Jakarta Platform and the Core and Web profiles:
 
@@ -223,7 +223,7 @@ The following specifications make up the Jakarta Platform and the Core and Web p
 | link:https://jakarta.ee/specifications/messaging/3.1/[Messaging 3.1] |Unchanged | link:https://openliberty.io/docs/latest/reference/feature/messaging-3.1.html[messaging-3.1]
 |===
 
-* Enterprise Beans 4.0 is unchanged, but the optional EJB 2.x function is no longer enabled when the `enterpriseBeans-4.0` feature is configured with other Jakarta EE 11 features and now requires the user to also add `enterpriseBeansHome-4.0` feature if they want to use EJB 2.x APIs.
+* Enterprise Beans 4.0 is unchanged, but the optional EJB 2.x function is no longer enabled when the enterpriseBeans-4.0 feature is configured with other Jakarta EE 11 features. Users who want to use EJB 2.x APIs must also add the enterpriseBeansHome-4.0 feature.
 
 Liberty provides convenience features for running all of the component specifications that are contained in the Jakarta EE 11 Web Profile (link:https://openliberty.io/docs/latest/reference/feature/webProfile-11.0.html[webProfile-11.0]) and the Jakarta EE 11 Platform (link:https://openliberty.io/docs/latest/reference/feature/jakartaee-11.0.html[jakartaee-11.0]). These convenience features enable you to rapidly develop applications using all of the APIs contained in their respective specifications. For Jakarta EE 11 features in the application client, use the link:https://openliberty.io/docs/latest/reference/feature/jakartaeeClient-11.0.html[jakartaeeClient-11.0] Liberty feature.
 
@@ -281,11 +281,11 @@ To run Jakarta EE 11 features on the Application Client Container, add the follo
 // // // // // // // // 
 [#springboot]
 == SpringBoot 4.0
-Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications by enabling this feature. While Liberty consistently supports Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications.
+Open Liberty currently supports running SpringBoot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy SpringBoot 4.x applications. While Liberty has consistently supported SpringBoot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for SpringBoot 4.x applications.
 
-The `springBoot-4.0` feature provides complete support for running a Sprint Boot 4.x application on Open Liberty as well as having the capability to thin the application when creating applications in containers.
+The `springBoot-4.0` feature provides complete support for running a SpringBoot 4.x application on Open Liberty, as well as the ability to thin the application when building containerized applications.
 
-To use this feature, the user must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to define the settings.
+To use this feature, users must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to configure the server.
 
 [source, xml]
 ----
@@ -295,14 +295,14 @@ To use this feature, the user must be running `Java 17` or later with EE11 featu
 </features>
 ----
 
-The `server.xml` configuration for deploying a Spring Boot application follows the same approach as in earlier Liberty Spring Boot versions.
+The `server.xml` configuration for deploying a SpringBoot application follows the same approach used in earlier Liberty SpringBoot versions.
 
 [source, xml]
 ---- 
 <springBootApplication id="spring-boot-app" location="spring-boot-app-0.1.0.jar" name="spring-boot-app" />
 ----
 
-As in earlier versions, the Spring Boot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when using this deployment method.
+As in earlier versions, the SpringBoot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when this deployment method is used.
 
 // DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>