Make reference to the redeemScript terminology
Document 520-byte serialized script limit
BIP 21: Add a missing "&" rule to the ABNF grammar

The URI syntax uses an ampersand to separate query parameters,
but the ABNF grammar didn't reflect this fact.

Also, the type of grammar used here is "ABNF" and not "BNF".
BIP 21: Mention RFC 3986 and character set
BIP 21: Precisely define the valid query characters
BIP 72: Reduce the amount of escaping needed

RFC 3986 obsoletes RFC 1738, which this BIP was wrongly referencing.
The new RFC requires far less escaping for query parameters.
Documenting the timestamp for BIP-0030

Per the linked commit, this rule became active for blocks with timestamps after on March 15, 2012 at 00:00 UTC (February 20, 2012 at 00:00 UTC for testnet).
BIP-0030 documentation now reflects reality.
BIP 21: Clarify case-sensitivity

The "bitcoin:" URI scheme needs to be case-insensitive according to the RFC,
but the query parameters should be case-sensitive according to the bitcoin-qt
client implementation.
BIP 21: Allow empty addresses and query parameters

Empty addresses should be valid for compatibility with  BIP 72.

Empty query parameters should also be valid, since they are harmless,
and clients already accept them.

With these changes, bitcoin:?& would be a valid (but useless) URI.
Remove duplicate BIP62 (malleability) entry
Assign BIP63 for Stealth Addresses
Add in-repo BIP70 extension registration page
Merge pull request #30 from swansontec/master

Fix BIP 21 and BIP 72 ambiguities & mistakes
Merge pull request #31 from airbreather/patch-1

Documenting the timestamp for BIP-0030
Merge pull request #24 from petertodd/document-bip16-520-byte-redeemScript-limit

Document BIP16/P2SH 520 byte redeem script limit
Merge pull request #14 from petertodd/stealth-addresses-bip-number-request

Assign BIP62 for Stealth Addresses
Fixed broken links to other BIP pages
Merge pull request #39 from stevenroose/patch-1

Fixed broken links to other BIP pages
Update bip-0070.mediawiki

Slightly re-worded description of the signature field in PaymentRequest

The previous phrasing confused me and I had to check the Bitcoin Core source code to see what it was expecting for a signature.