updates for 4638 incl build issues (#4713)

docs/config/io_helidon_microprofile_jwt.adoc

@@ -26,11 +26,11 @@
 
 // tag::config[]
 
-== Configuration options
+== Configuration Options
 
 
-.MicroProfile configuration options:
-[cols="3,3,2,5a"]
+MicroProfile configuration options:
+[cols="3,3,2,5"]
 
 |===
 |key |type |default value |description
@@ -41,8 +41,8 @@
 
 |===
 
-.Optional configuration options:
-[cols="3,3,2,5a"]
+Optional configuration options:
+[cols="3,3,2,5"]
 
 |===
 |key |type |default value |description
@@ -52,7 +52,7 @@ an important distinction when more than one provider is used
 |`authenticate` |boolean |`true` |Whether to attempt authentication
 |`propagate`|boolean |`true` |Whether to attempt identity propagation/JWT creation
 |`principal-type`|string |`USER` |Whether we authenticate a user or a service (other option is SERVICE)
-|`atn-token` |string |{nbsp} |A group for configuring authentication of the request
+|`atn-token` |string ||A group for configuring authentication of the request
 |`atn-token.verify-signature`|boolean |`true` |Whether to verify signature in incoming JWT. If disabled, _ANY_ JWT will be accepted
 |`atn-token.jwt-audience`|string |{nbsp} |Expected audience of the JWT. If not defined, any audience is accepted (and we may accept JWT not inteded for us)
 |`atn-token.jwk.resource.*`|string |{nbsp} |Configuration of the JWK to obtain key(s) to validate signatures of inbound token. The JWK should contain public keys. This may be: jwk.resource.path, jwk.resource.resource-path, jwk.resource.url, jwk.resource.content-plain (actual JSON string), jwk.resource.content (base64)

docs/mp/jwt.adoc

@@ -42,7 +42,7 @@ include::{rootdir}/includes/mp.adoc[]
 
 JSON Web Tokens (JWT) are an open, industry standard https://datatracker.ietf.org/doc/html/rfc7519[(RFC 7519)] method for representing claims securely between two parties.
 
-JSON Web Token defines a compact and self-contained way for securely transmitting information between parties as a JSON object. With JWT Auth you can integrate security features such as single sign on into your Helidon MP applications.
+JWT defines a compact and self-contained way for securely transmitting information between parties as a JSON object. With JWT Auth you can integrate security features such as single sign on into your Helidon MP applications.
 
 
 include::{rootdir}/includes/dependencies.adoc[]
@@ -135,7 +135,7 @@ Obtain the Security Token from external issuer:
 TOKEN=sdf4dDSWFcswdsffDSasEgv...
 ----
 
-Run the application and execute an http request against it:
+Run the application and execute an HTTP request against it:
 
 [source, bash]
 ----