Apply suggestions from code review

Co-authored-by: Ben Ahmady <[email protected]>

Author: geoffw0

swift/ql/src/queries/Security/CWE-328/WeakPasswordHashing.qhelp

@@ -4,8 +4,7 @@
 <qhelp>
     <overview>
         <p>
-            Using a insufficiently computationally hard hash function can leave data
-            vulnerable, and should not be used for password hashing.
+            Hash functions that are not sufficiently computationally hard can leave data vulnerable. You should not use such functions for password hashing.
         </p>
 
         <p>
@@ -34,14 +33,14 @@
         </p>
 
         <p>
-            Password hashing algorithms are designed to be slow and/or memory intenstive to compute, which makes brute force attacks more difficult.
+            Password hashing algorithms should be slow and/or memory intensive to compute, to make brute force attacks more difficult.
         </p>
 
     </overview>
     <recommendation>
 
         <p>
-            Ensure that for password storage you should use a computationally hard cryptographic hash function, such as:
+            For password storage, you should use a computationally hard cryptographic hash function, such as one of the following:
         </p>
 
         <ul>
@@ -63,9 +62,9 @@
     <example>
 
         <p>
-            The following examples show a function that hashes a password using a cryptographic hashing algorithm.
+            The following examples show two versions of the same function. In both cases, a password is hashed using a cryptographic hashing algorithm.
 
-            In the first case the SHA-512 hashing algorithm is used. It is vulnerable to offline brute force attacks:
+            In the first case, the SHA-512 hashing algorithm is used. It is vulnerable to offline brute force attacks:
         </p>
         <sample src="WeakPasswordHashingBad.swift"/>
         <p>