#5832, #5833, #5835

modules/ROOT/pages/jakarta-ee10-diff.adoc

@@ -26,6 +26,7 @@ The following sections describe updates for different Jakarta EE 10.0 features
 * <<appAuthz,Jakarta Authorization 2.1>>
 * <<appAuthn,Jakarta Authentication 3.0>>
 * <<el,Jakarta Expression Language 5.0>>
+* <<pages,Jakarta Server Pages 3.1>>
 
 [#cdi]
 == Differences between Jakarta Contexts and Dependency Injection 4.0 and 3.0
@@ -141,7 +142,7 @@ For more information, see the https://jakarta.ee/specifications/cdi/4.0/apidocs/
 [#servlet]
 == Differences between Jakarta Servlet 6.0 and 5.0
 
-The feature:servlet-6.0[display=Jakarta Servlet 6.0] feature (`servlet-6.0`) provides new APIs and new configurations to set any attribute on a response cookie.
+The feature:servlet-6.0[display=Jakarta Servlet 6.0] feature (`servlet-6.0`) provides new APIs and new configurations to set attributes on a response cookie.
 
 === New ways to configure cookie attributes
 
@@ -211,7 +212,7 @@ For example, consider the following HTTP request, which includes a cookie header
 Cookie: $Version=1; name1=value1; $Path=/Dollar_Path; $Domain=localhost; $NAME2=DollarNameValue;Domain=DomainValue
 ----
 
-Before Servlet 6.0, the server creates the following three request cookies from this request.
+Before Servlet 6.0, the server created the following three request cookies from this request.
 
 ----
 cookie1: name1 with the associated attributes: Path=/Dollar_Path; Domain=localhost
@@ -311,7 +312,7 @@ For more information, see the https://jakarta.ee/specifications/authentication/3
 [#el]
 == Differences between Jakarta Expression Language 5.0 and 4.0
 
-The feature:expressionLanguage-5.0[Jakarta Expression Language 5.0] feature adds support for Java Generics and includes updates to Type coercion, the Expression Language resolver, and more.
+The feature:expressionLanguage-5.0[display=Jakarta Expression Language 5.0] feature adds support for Java Generics and includes updates to type coercion, the Expression Language resolver, and more.
 
 === Support for Java Generics
 
@@ -333,19 +334,20 @@ A new `MethodReference` class provides access to details of the method to which
 
 === Deprecations and removals
 
-The `ELResolver ` `getFeatureDescriptors()` method is deprecated in Expression Language 5.0, with remvoal planned for Expression Language 6.0. A new default implementation that returns null is added. This update ensures that custom `ELResolver` implementations do not need to implement the method.
+The `ELResolver` `getFeatureDescriptors()` method is deprecated in Expression Language 5.0, with remvoal planned for Expression Language 6.0. A new default implementation that returns null is added. This update ensures that custom `ELResolver` implementations do not need to implement the method.
 
 The deprecated and misspelled `MethodExpression.isParmetersProvided()` method is removed from the API.
 
 For more information, see the https://jakarta.ee/specifications/expression-language/5.0/apidocs/jakarta.el/module-summary.html[Jakarta Expression Language 5.0 Javadoc].
 
-== Differences between Jakarta Pages and 3.1 and 3.0 
+[#pages]
+== Differences between Jakarta Server Pages and 3.1 and 3.0 
 
-The feature:pages-3.1[display=Jakarta Server Pages 3.1] featutre provides support for the Jakarta Server Pages 3.1 and Jakarta Standard Tag Library 3.0 specifications. This release includes updates for Expression Language identifiers and resolvers, new tag URIs, and more.
+The feature:pages-3.1[display=Jakarta Server Pages 3.1] featutre provides support for the https://jakarta.ee/specifications/pages/3.1/jakarta-server-pages-spec-3.1.html[Jakarta Server Pages 3.1] and https://jakarta.ee/specifications/tags/3.0/jakarta-tags-spec-3.0.html[Jakarta Standard Tag Library 3.0] specifications. This release includes updates for Expression Language identifiers and resolvers, new tag URIs, and more.
 
 === Finding unknown identifiers
 
-A new option is added to find unknown Expression Language identifiers. When this option is enabled, a `PropertyNotFoundException` occur sif an unknown identifier is found. Previously, unknown identifiers were rendered as empty strings (""), and where difficult to identify. You can enable this option by using page directives, tag directives, or as a jsp-property-group in the `web.xml` file. 
+This release adds a new option to find unknown Expression Language identifiers. When this option is enabled, a `PropertyNotFoundException` occurs if an unknown identifier is found. Previously, unknown identifiers were rendered as empty strings ("") and were difficult to identify. You can enable this option by using page directives, tag directives, or as a JSP Property Group in the `web.xml` file. 
 
 To enable this option by using page or tag directives, set the `errorOnELNotFound` attribute to `true`, as shown in the following example.
 
@@ -363,11 +365,11 @@ To enable this option byn using a JSP Property Group in the `web.xml` file, set
 </jsp-property-group>
 ----
 
-For more information, see https://jakarta.ee/specifications/pages/3.1/jakarta-server-pages-spec-3.1.html#_Unknown_EL_Identifiers[Unknown EL Identifiers] in the Jakarta Server Pages specification
+For more information, see https://jakarta.ee/specifications/pages/3.1/jakarta-server-pages-spec-3.1.html#_Unknown_EL_Identifiers[Unknown EL Identifiers] in the Jakarta Server Pages specification.
 
 === Namespace updates
 
-The Jakarta Tag URIs now use the `jakarta.tags.*` pattern. Although support for the previous `\http://xmlns.jcp.org/jsp/jstl/*` pattern is maintained for backwards compatibility, it is recommended to update your applications to use these new URIs. The following example shows the `taglib` directive using the new URIs.
+The Jakarta Tag URIs now use the `jakarta.tags.\*` pattern. Although support for the previous `\http://xmlns.jcp.org/jsp/jstl/*` pattern is maintained for backwards compatibility, it is recommended to update your applications to use these new URIs. The following example shows the `taglib` directive with the new URIs.
 
 ----
 <%@ taglib prefix="c" uri="jakarta.tags.core" %> 
@@ -380,7 +382,7 @@ For more information, see the https://jakarta.ee/specifications/tags/3.0/tagdocs
 
 === Deprecations
 
-The `isThreadSafe` directive is deprecated due to the removal of the `SingleThreadModel` interface in the Servlet 6.0 API. A workaround is implemented, but significant performance impact might occur. Use of the `isThreadSafe` directive in Pages 3.1 is discouraged.
+The `isThreadSafe` directive is deprecated due to the removal of the `SingleThreadModel` interface in the Servlet 6.0 API. A workaround is implemented, but significant performance impacts might occur. Use of the `isThreadSafe` directive in Pages 3.1 is discouraged.
 
 The `jsp:plugin`, `jsp:params`, and `jsp:fallback` actions are deprecated and are not operational because current browsers no longer support the elements that are generated by the `jsp:plugin` and related actions.