Security/NonceVerification: various documentation tweaks

WordPress/Sniffs/Security/NonceVerificationSniff.php

@@ -31,6 +31,7 @@
  * @since   0.5.0
  * @since   0.13.0 Class name changed: this class is now namespaced.
  * @since   1.0.0  This sniff has been moved from the `CSRF` category to the `Security` category.
+ * @since   3.0.0  This sniff has received significant updates to its logic and structure.
  *
  * @uses    \WordPressCS\WordPress\Helpers\SanitizingFunctionsTrait::$customSanitizingFunctions
  * @uses    \WordPressCS\WordPress\Helpers\SanitizingFunctionsTrait::$customUnslashingSanitizingFunctions
@@ -275,7 +276,7 @@ private function has_nonce_check( $stackPtr, array $cache_keys, $allow_nonce_aft
 		if ( false !== $current_cache['nonce'] ) {
 			// If we have already found an nonce check in this scope, we just
 			// need to check whether it comes before this token. It is OK if the
-			// check is after the token though, if this was only a isset() check.
+			// check is after the token though, if this was only an isset() check.
 			return ( true === $allow_nonce_after || $current_cache['nonce'] < $stackPtr );
 		} elseif ( $end <= $current_cache['end'] ) {
 			// If not, we can still go ahead and return false if we've already