Apply suggestions from code review

Co-authored-by: Michelle Purcell <[email protected]>

docs/src/main/asciidoc/security-jpa-concept.adoc

@@ -17,7 +17,7 @@ Quarkus security offers a JPA integration to collect usernames, passwords, and r
 The following JPA entity specification demonstrates how users' information needs to be stored in a JPA entity and properly mapped so that Quarkus can retrieve this information from a database.
 
 
-* The `@UserDefinition` annotation must be present on a JPA entity, no matter if link:https://quarkus.io/guides/hibernate-orm-panache[simplified Hibernate ORM with Panache] is used or not.
+* The `@UserDefinition` annotation must be present on a JPA entity, regardless of whether link:https://quarkus.io/guides/hibernate-orm-panache[simplified Hibernate ORM with Panache] is used or not.
 
 * The `@Username` and `@Password` field types are always `String`.
 
@@ -127,7 +127,7 @@ In cryptography, a salt is a name for random data used as an additional input to
 
 For manual password hashing, create a class that implements the `CustomPasswordProvider`as shown in the example below.
 
-This is an example of providing a custom password provider using the SHA256 hashing algorithm.
+The following snippet shows how to set a custom password provider that uses the SHA256 hashing algorithm.
 
 [source,java]
 ----
@@ -170,7 +170,7 @@ This method also allows specifying the desired amount of iterations and the salt
 ====
 Never store passwords as a plain text for applications already running in production.
 
-However, it is possible to store passwords as a plain text with the `@Password(PasswordType.CLEAR)` annotation when operating in a test environment.
+However, it is possible to store passwords as plain text with the `@Password(PasswordType.CLEAR)` annotation when operating in a test environment.
 ====
 
 == References