XMSS/XMSSMT hooks support: small update for requested changes.

Author: philljj

INSTALL

@@ -399,18 +399,19 @@ We also have vcpkg ports for wolftpm, wolfmqtt and curl.
       $ git apply <path to xmss reference patch>
 
     The patch may be found in the wolfssl-examples repo here:
-      pq/stateful_hash_sig/0001-Patch-to-support-xmss-reference-integration.patch
+      pq/stateful_hash_sig/0001-Patch-to-support-wolfSSL-xmss-reference-integration.patch
 
     To build patched xmss-reference:
       $ make xmss_lib.a
 
     To build verify-only patched xmss-reference:
       $ make xmss_verify_lib.a
 
-    Note that this patch adds wolfCrypt SHA256 hashing to xmss-reference, and
+    Note that this patch changes xmss-reference to use wolfCrypt SHA256 hashing,
+    by registering a SHA callback function in xmss-reference. It
     thus benefits from all the same asm speedups as wolfCrypt SHA hashing.
     Depending on architecture you may build with --enable-intelasm, or
-    and --enable-armasm, and see 30-40% speedups in XMSS/XMSS^MT.
+    --enable-armasm, and see 30-40% speedups in XMSS/XMSS^MT.
 
     For full keygen, signing, verifying, and benchmarking support, build
     wolfSSL with:

wolfcrypt/benchmark/benchmark.c

@@ -8313,7 +8313,7 @@ void bench_xmss(void)
     /* All NIST SP 800-208 approved SHA256 XMSS/XMSS^MT parameter
      * sets.
      *
-     * note: not testing "XMSS-SHA2_16_256", "XMSS-SHA2_20_256",
+     * Note: not testing "XMSS-SHA2_16_256", "XMSS-SHA2_20_256",
      * and "XMSSMT-SHA2_60/3_256", because their keygen can be
      * very slow, their signatures and private keys quite large,
      * and xmss private keys are not portable across different