Apply suggestions from code review

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

Author: geoffw0

swift/ql/src/queries/Security/CWE-116/BadTagFilter.qhelp

@@ -38,15 +38,15 @@ the function, and <code>alert(1)</code> will be executed by a browser if the str
 </p>
 
 <p>
-Other corner cases include that HTML comments can end with <code>--!&gt;</code>,
-and that HTML tag names can contain upper case characters.
+Other corner cases include HTML comments ending with <code>--!&gt;</code>,
+and HTML tag names containing uppercase characters.
 </p>
 </example>
 
 <references>
 <li>Securitum: <a href="https://research.securitum.com/the-curious-case-of-copy-paste/">The Curious Case of Copy &amp; Paste</a>.</li>
 <li>stackoverflow.com: <a href="https://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags#answer-1732454">You can't parse [X]HTML with regex</a>.</li>
 <li>HTML Standard: <a href="https://html.spec.whatwg.org/multipage/parsing.html#comment-end-bang-state">Comment end bang state</a>.</li>
-<li>stackoverflow.com: <a href="https://stackoverflow.com/questions/25559999/why-arent-browsers-strict-about-html">Why aren't browsers strict about HTML?</a>.</li>
+<li>stackoverflow.com: <a href="https://stackoverflow.com/questions/25559999/why-arent-browsers-strict-about-html">Why aren't browsers strict about HTML?</a></li>
 </references>
 </qhelp>

swift/ql/src/queries/Security/CWE-116/BadTagFilter.ql

@@ -1,6 +1,6 @@
 /**
  * @name Bad HTML filtering regexp
- * @description Matching HTML tags using regular expressions is hard to do right, and can easily lead to security issues.
+ * @description Matching HTML tags using regular expressions is hard to do right, and can lead to security issues.
  * @kind problem
  * @problem.severity warning
  * @security-severity 7.8