typos, other minor fixes

Author: equijano21

docs/users-manual/application-otp/challenge-response.md

@@ -59,8 +59,7 @@ bytes of additional data are not important—they are merely added as padding so
 with a 16-byte key using the AES encryption algorithm (AES requires that data be encrypted in blocks of the same size as
 the encryption key). The resulting Yubico OTP (as a byte array) becomes the response.
 
-For HMAC-SHA1 challenge-response, an application will send the YubiKey a challenge of up to 64 bytes in size, which will be digested (
-hashed) with a 20-byte secret key, resulting in a 20-byte response (the HMAC-SHA1 hash value). Responses can be received 
+For HMAC-SHA1 challenge-response, an application will send the YubiKey a challenge of up to 64 bytes in size, which will be digested (hashed) with a 20-byte secret key, resulting in a 20-byte response (the HMAC-SHA1 hash value). Responses can be received 
 by an application as a byte array or a 6-10 digit numeric code. With HMAC-SHA1, the challenge can be either an 
 application-specified byte array or the current Unix time.
 
@@ -109,7 +108,7 @@ The SDK’s challenge-response functionality centers around the following two me
 
 ``ConfigureChallengeResponse()`` allows you to configure an OTP application slot on a YubiKey to receive a challenge
 from a host and process it based on a specific algorithm and secret key. ``CalculateChallengeResponse()`` allows a host
-to send a challenge to a YubiKey and then receive the response from the YubiKey.
+to send a challenge to a YubiKey and then receive its response.
 
 ### ConfigureChallengeResponse()
 
@@ -176,10 +175,10 @@ The SDK will throw an exception if you call both ``UseTotp()`` and ``UseChalleng
 > slot is configured to perform Yubico OTP, the challenge must
 > be [6 bytes](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.YubicoOtpChallengeSize) long. If the slot
 > is
-> configured for HMAC-SHA1, the HOTP challenge must
+> configured for HMAC-SHA1, the challenge must
 > be [64 bytes](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.MaxHmacChallengeSize) long. However, if
 > the
-> slot has been configured with ``UseSmallChallenge()``, an HOTP challenge smaller than 64 bytes is acceptable. The
+> slot has been configured with ``UseSmallChallenge()``, a challenge smaller than 64 bytes is acceptable. The
 > SDK will throw an exception if the challenge size does not match the YubiKey slot's configuration.
 
 For a full list of the methods in the ``CalculateChallengeResponse`` class, see

docs/users-manual/application-otp/how-to-calculate-a-challenge-response-code.md

@@ -45,7 +45,7 @@ The response from a YubiKey can be received via one of three methods:
 
 1. [GetCode()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.GetCode%28System.Int32%29): returns a
    string object containing [six](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.MinOtpDigits)
-   to [ten](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.MaxOtpDigits) 32-bit integers. A 6-digit code
+   to [ten](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.MaxOtpDigits) numeric digits. A 6-digit code
    will be returned by default unless a larger number is specified when calling this method (for
    example, ``GetCode(8)``).
 1. [GetDataBytes()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.GetDataBytes): returns a byte array.
@@ -109,7 +109,7 @@ var yubiKey = yubiKeyList.First();
 
 In this example, we send an HMAC-SHA1 challenge (``hmacChal``) to the short press slot of the YubiKey
 with [UseChallenge()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.UseChallenge%28System.Byte%5B%5D%29)
-and get the response as a string object containing eight 32-bit integers via ``GetCode()``.
+and get the response as a string object containing eight numeric digits via ``GetCode()``.
 
 In addition, we
 use [UseTouchNotifier()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.UseTouchNotifier%28System.Action%29)

docs/users-manual/application-otp/how-to-program-a-challenge-response-credential.md

@@ -66,8 +66,8 @@ result). Due to this truncation, it’s important to use the setting that will b
 code.
 
 > [!NOTE]
-> You can still use challenges smaller than 64 bytes without setting the short challenge mode by simply padding the end
-> of the challenge with zeros. Again, it’s important that both sides of the operation agree on the length of the
+> You can use challenges smaller than 64 bytes without setting the short challenge mode by padding the end
+> of the challenge with zeros. Regardless, both sides of the operation must agree on the length of the
 > challenge.
 
 ## Requiring touch
@@ -80,11 +80,10 @@ To enable this setting, add
 the [UseButton()](xref:Yubico.YubiKey.Otp.Operations.ConfigureChallengeResponse.UseButton(System.Boolean)) method to
 your ``ConfigureChallengeResponse()`` operation.
 
-> [!NOTE]
-> If a YubiKey has been configured to require a button touch, you must make sure to alert the user of this requirement
-> during a challenge-response operation. This can be accomplished by calling
-> the [UseTouchNotifier()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.UseTouchNotifier(System.Action))
-> method when sending a challenge to a YubiKey via ``CalculateChallengeResponse()``.
+If a YubiKey has been configured to require a button touch, you must make sure to alert the user of this requirement
+during a challenge-response operation. This can be accomplished by calling
+the [UseTouchNotifier()](xref:Yubico.YubiKey.Otp.Operations.CalculateChallengeResponse.UseTouchNotifier(System.Action))
+method when sending a challenge to a YubiKey via ``CalculateChallengeResponse()``.
 
 ## ConfigureChallengeResponse examples