javaee
diff --git a/‎src/main/jbake/content/security-api004.adoc‎
Lines changed: 7 additions & 12 deletions b/‎src/main/jbake/content/security-api004.adoc‎
Lines changed: 7 additions & 12 deletions
diff --git a/‎src/main/jbake/content/security-api005.adoc‎
Lines changed: 6 additions & 6 deletions b/‎src/main/jbake/content/security-api005.adoc‎
Lines changed: 6 additions & 6 deletions
@@ -25,15 +25,15 @@ JSR 375 mandates that a Java EE container MUST support a built-in `IdentityStore
 backed by a database. To support this mandatory requirement, `DatabaseIdentityStore`
 is bundled with the GlassFish-RI.
 
-The source code for this example is in the
-`_tut-install_/examples/security/security-api/built-in-db-identity-store` directory.
-
 This example demonstrates how you can configure a `DatabaseIdentityStore` to point
 to a backend database and then use it as an IdentityStore. The authentication mechanism used is
 `BasicAuthenticationMechanism`.
 
-The high-level process for configuring the DatabaseIdentityStore is shown in the
-following sections. Note that the configuration described in these sections has
+The source code for this example is in the
+`_tut-install_/examples/security/security-api/built-in-db-identity-store` directory.
+
+The following sections describe the high-level process for configuring the
+`DatabaseIdentityStore`. Note that the configuration described in these sections has
 already been completed in the application files, but is provided here to illustrate
 what you need to do to use the built-in database identity store.
 
@@ -74,7 +74,7 @@ Define the Users and Groups in the Identity Store
 
 The following table shows the users, passwords, and groups used in this example.
 
-[width=99%,cols="30%,40%,30%"]
+[width=60%,cols="30%,40%,30%"]
 |=======================================================================
 |*User* |*Password* |*Group*
 |Joe |secret1 |foo, bar
@@ -194,7 +194,7 @@ Declare Roles in the Servlet Container
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 When a request is made to the application, the roles the user is in are returned
 as part of the response. Note that the container needs to be made aware of the
-supported roles, which you specify using the `@DeclareRoles({ "foo", "bar", "kaz" })`
+supported roles, which are defined using the `@DeclareRoles({ "foo", "bar", "kaz" })`
 annotation as shown below.
 
 [source,oac_no_warn]
@@ -224,11 +224,6 @@ public class Servlet extends HttpServlet {
 }
 ----
 
-[source,oac_no_warn]
-----
-@DeclareRoles({ "foo", "bar", "kaz" })
-----
-
 In GlassFish 5.0, group to role mapping is enabled by default. Therefore, you do
 not need to bundle web.xml with the application to provide mapping between
 roles and groups.
 
@@ -25,15 +25,15 @@ As an alternative to using a built-in identity store, an application can provide
 its own IdentityStore. When bundled with the application,
 this custom identity store can then be used for authentication and authorization.
 
-The source code for this example is in the
-`_tut-install_/examples/security/security-api/custom-identity-store` directory.
-
 This example demonstrates how to define a custom identity store, `TestIdentityStore`, and
 provide it as part of the application being deployed. The authentication mechanism used is
 `BasicAuthenticationMechanism`.
 
-The high-level process for defining the `TestIdentityStore` is shown in the
-following sections. Note that the configuration described in these sections has
+The source code for this example is in the
+`_tut-install_/examples/security/security-api/custom-identity-store` directory.
+
+The following sections describe the high-level process for defining
+the `TestIdentityStore`. Note that the configuration described in these sections has
 already been completed in the application files, but is provided here to illustrate
 what you need to do to use a custom identity store.
 
@@ -72,7 +72,7 @@ Define the Users and Groups in the Identity Store
 The following table shows the user, password, and group used in this example.
 
 
-[width=99%,cols="30%,40%,30%"]
+[width=60%,cols="30%,40%,30%"]
 |====================================
 |*User* |*Password* |*Group*