diff --git a/bip-0322.mediawiki b/bip-0322.mediawiki
index 20b68c85..75b0ff51 100644
--- a/bip-0322.mediawiki
+++ b/bip-0322.mediawiki
@@ -186,7 +186,7 @@ Validation consists of the following steps:
##* to_sign has exactly one output, as specified above
## Confirm that the two transactions together satisfy all consensus rules, except for to_spend's missing input, and except that ''nSequence'' of to_sign's first input and ''nLockTime'' of to_sign are not checked.
# (Optional) If the validator does not have a full script interpreter, it should check that it understands all scripts being satisfied. If not, it should stop here and output ''inconclusive''.
-# Check the **required rules**:
+# Check the '''required rules''':
## All signatures must use the SIGHASH_ALL flag.
## The use of CODESEPARATOR or FindAndDelete is forbidden.
## LOW_S, STRICTENC and NULLFAIL: valid ECDSA signatures must be strictly DER-encoded and have a low-S value; invalid ECDSA signature must be the empty push
@@ -194,10 +194,10 @@ Validation consists of the following steps:
## CLEANSTACK: require that only a single stack element remains after evaluation
## MINIMALIF: the argument of IF/NOTIF must be exactly 0x01 or empty push
## If any of the above steps failed, the validator should stop and output the ''invalid'' state.
-# Check the **upgradeable rules**
+# Check the '''upgradeable rules'''
## The version of to_sign must be 0 or 2.
## The use of NOPs reserved for upgrades is forbidden.
-## The use of segwit versions greater than 1 are forbidden.
+## The use of Segwit versions greater than 1 are forbidden.
## If any of the above steps failed, the validator should stop and output the ''inconclusive'' state.
# Let ''T'' by the nLockTime of to_sign and ''S'' be the nSequence of the first input of to_sign. Output the state ''valid at time T and age S''.
@@ -212,7 +212,8 @@ Signers who control an address ''A'' who wish to sign a message ''m'' act as fol
message_hash.
to_sign or nSequence of its first input.
+ Optionally, they may set nVersion/nLockTime of to_sign or nSequence of its first
+ input.
to_sign that they wish to prove
@@ -227,8 +228,8 @@ They then encode their signature, choosing either ''simple'' or ''full'' as foll
to_sign, left nSequence and nLockTime at 0, and ''A'' is a
- Segwit address (either pure or P2SH-wrapped), then they may base64-encode
+ If they added no inputs to to_sign, left nVersion, nSequence and nLockTime at 0, and
+ ''A'' is a "native" Segwit address (P2WPKH, P2WSH, P2TR), then they may base64-encode
message_signature