[3.8] Small documentation enhancement/formating

docs/src/main/asciidoc/config-reference.adoc

@@ -236,7 +236,7 @@ converted default value. However, when the property is explicitly empty, the def
 [source,properties]
 ----
 # missing value, optional property
-greeting.name =
+greeting.name=
 ----
 
 In this case, since `greeting.name` was configured to be `Optional*` up above, the corresponding property value will
@@ -248,7 +248,7 @@ On the other hand, this example:
 [source,properties]
 ----
 # missing value, non-optional
-greeting.suffix =
+greeting.suffix=
 ----
 
 will result in a `java.util.NoSuchElementException: SRCFG02004: Required property greeting.message not found` on

docs/src/main/asciidoc/config.adoc

@@ -58,11 +58,11 @@
 [source,properties]
 ----
 # Your configuration properties
-greeting.message = hello
-greeting.name = quarkus
+greeting.message=hello
+greeting.name=quarkus
 ----
 
 == Create a REST resource
 
 Create the `org.acme.config.GreetingResource` REST resource with the following content:
 

docs/src/main/asciidoc/security-authorize-web-endpoints-reference.adoc

@@ -361,7 +361,7 @@ For more information, see link:https://quarkus.io/blog/path-resolution-in-quarku
 === Map `SecurityIdentity` roles
 
 Winning role-based policy can map the `SecurityIdentity` roles to the deployment-specific roles.
-These roles are then applicable for endpoint authorization by using the @RolesAllowed annotation.
+These roles are then applicable for endpoint authorization by using the `@RolesAllowed` annotation.
 
 [source,properties]
 ----

docs/src/main/asciidoc/security-basic-authentication.adoc

@@ -66,7 +66,7 @@ For more information about how you can secure your Quarkus applications by using
 
 == Role-based access control
 
-{project-name} also includes built-in security to allow for role-based access control (RBAC) based on the common security annotations @RolesAllowed, @DenyAll, @PermitAll on REST endpoints and CDI beans.
+{project-name} also includes built-in security to allow for role-based access control (RBAC) based on the common security annotations `@RolesAllowed`, `@DenyAll`, `@PermitAll` on REST endpoints and CDI beans.
 For more information, see the Quarkus xref:security-authorize-web-endpoints-reference.adoc[Authorization of web endpoints] guide.
 
 == References

docs/src/main/asciidoc/security-jwt.adoc

@@ -252,9 +252,9 @@
 ----
 <1> Here we inject `JsonWebToken`
 <2> This new endpoint will be located at /secured/roles-allowed
-<3> @RolesAllowed is a Jakarta common security annotation that indicates that the given endpoint is accessible by a caller if
+<3> `@RolesAllowed` is a Jakarta common security annotation that indicates that the given endpoint is accessible by a caller if
 they have either a "User" or "Admin" role assigned.
 <4> Here we build the reply the same way as in the `hello` method but also add a value of the JWT `birthdate` claim by directly calling the injected `JsonWebToken`.
 
 After you make this addition to your `TokenSecuredResource`, rerun the `./mvnw compile quarkus:dev` command, and then try `curl -v http://127.0.0.1:8080/secured/roles-allowed; echo` to attempt to access the new endpoint.
 

docs/src/main/asciidoc/spring-boot-properties.adoc

@@ -111,10 +111,10 @@
 [source,properties]
 ----
 # Your configuration properties
-greeting.text = hello
+greeting.text=hello
 ----
 
 Now modify `GreetingResource` to start using the `GreetingProperties`:
 
 [source,java]
 ----
@@ -359,7 +359,7 @@
 [source,properties]
 ----
 # Your configuration properties
-greeting.message.text = hello
+greeting.message.text=hello
 ----
 
 [source,java]