Apply suggestions from code review

Co-authored-by: kingthorin <[email protected]>

Author: preetkaran20

src/main/resources/org/zaproxy/zap/extension/jwt/resources/Messages.properties

@@ -84,7 +84,7 @@ jwt.scanner.server.vulnerability.signatureAttack.jwkCustomKey.desc=JWT library i
 jwt.scanner.server.vulnerability.signatureAttack.jwkCustomKey.refs=https://nvd.nist.gov/vuln/detail/CVE-2018-0114
 jwt.scanner.server.vulnerability.signatureAttack.jwkCustomKey.soln=Validating Library should not depend on user provided input
 
-jwt.scanner.server.vulnerability.signatureAttack.publiclyKnownSecrets.name=Publicly well known HMac secret attack
+jwt.scanner.server.vulnerability.signatureAttack.publiclyKnownSecrets.name=Publicly Well Known HMac Secret Attack
 jwt.scanner.server.vulnerability.signatureAttack.publiclyKnownSecrets.desc=JWT tokens signed using HMac algorithm requires secret key and there are publicly well known secret keys which should not be used for signing the JWT token as it can cause various attacks like identity theft, user impersonation etc. 
 jwt.scanner.server.vulnerability.signatureAttack.publiclyKnownSecrets.refs=https://lab.wallarm.com/340-weak-jwt-secrets-you-should-check-in-your-code
 jwt.scanner.server.vulnerability.signatureAttack.publiclyKnownSecrets.soln=Secret keys used for signing should not be publicly well known or easy to guess. 
@@ -101,4 +101,4 @@ jwt.scanner.server.vulnerability.miscAttack.emptyTokens.soln=Tokens even if empt
 
 # JWT scanner references and solutions
 jwt.scanner.refs=https://cheatsheetseries.owasp.org/cheatsheets/JSON_Web_Token_Cheat_Sheet_for_Java.html
-jwt.scanner.soln=See reference for further information. The solution depends on implementation details
+jwt.scanner.soln=See reference for further information. The solution depends on implementation details