diff --git a/bip-0021.md b/bip-0021.md
index 55d3143..ce5fc4d 100644
--- a/bip-0021.md
+++ b/bip-0021.md
@@ -38,7 +38,7 @@ Graphical bitcoin clients SHOULD register themselves as the handler for the "bit
  labelparam     = "label=" *pchar
  messageparam   = "message=" *pchar
  otherparam     = pchar *pchar "=" *pchar
- reqparam       = "req:" pchar *pchar "=" *pchar
+ reqparam       = "req-" pchar *pchar "=" *pchar
 
 === Query Keys ===
 
@@ -70,10 +70,10 @@ Other proposed names sound much more cryptic; the chance that someone googles th
 Also, very likely, what he will find are mostly technical specifications - not the best introduction to bitcoin.
 
 ==Forward compatibility==
-Variables which are prefixed with a req: are considered required.  If a client does not implement any variables which are prefixed with req:, it MUST consider the entire URI invalid.  Any other variables which are not implemented, but which are not prefixed with a req:, can be safely ignored.  
+Variables which are prefixed with a req- are considered required.  If a client does not implement any variables which are prefixed with req-, it MUST consider the entire URI invalid.  Any other variables which are not implemented, but which are not prefixed with a req-, can be safely ignored.  
 
 ==Backward compatibility==
-As this BIP is written, several clients already implement a bitcoin: URI scheme similar to this one, however usually without the additional "req:" prefix requirement.  Thus, it is recommended that additional variables prefixed with req: not be used in a mission-critical way until a grace period of 6 months from the finalization of this BIP has passed in order to allow client developers to release new versions, and users of old clients to upgrade.
+As this BIP is written, several clients already implement a bitcoin: URI scheme similar to this one, however usually without the additional "req-" prefix requirement.  Thus, it is recommended that additional variables prefixed with req- not be used in a mission-critical way until a grace period of 6 months from the finalization of this BIP has passed in order to allow client developers to release new versions, and users of old clients to upgrade.
 
 == Appendix ==
 
@@ -101,7 +101,7 @@ Request 50 BTC with message:
  bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?amount=50&label=Luke-Jr&message=Donation%20for%20project%20xyz
 
 Some future version that has variables which are (currently) not understood and required and thus invalid:
- bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?req:somethingyoudontunderstand=50&req:somethingelseyoudontget=999
+ bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?req-somethingyoudontunderstand=50&req-somethingelseyoudontget=999
 
 Some future version that has variables which are (currently) not understood but not required and thus valid:
  bitcoin:175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W?somethingyoudontunderstand=50&somethingelseyoudontget=999
@@ -110,7 +110,7 @@ Characters must be URI encoded properly.
 
 == Reference Implementations ==
 === Bitcoin clients ===
-* [[Bitcoin-Qt]] supports the old version of Bitcoin URIs (ie without the req: prefix), with Windows and KDE integration as of commit 70f55355e29c8e45b607e782c5d76609d23cc858.
+* [[Bitcoin-Qt]] supports the old version of Bitcoin URIs (ie without the req- prefix), with Windows and KDE integration as of commit 70f55355e29c8e45b607e782c5d76609d23cc858.
 
 [[Category:Developer]]
 [[Category:Technical]]