EDT-3069 Drop the "DRAFT" text from linked standards, so when we go f…

…inal and subsequently they do our text is not out of date. Users can see the current status of those other standards on the landing page for them.

EIPS/eip-1155.md

@@ -475,7 +475,7 @@ fr.json:
 
 ### Approval
 
-The function `setApprovalForAll` allows an operator to manage one's entire set of tokens on behalf of the approver. To permit approval of a subset of token IDs, an interface such as [ERC-1761 Scoped Approval Interface (DRAFT)](https://eips.ethereum.org/EIPS/eip-1761) is suggested.
+The function `setApprovalForAll` allows an operator to manage one's entire set of tokens on behalf of the approver. To permit approval of a subset of token IDs, an interface such as [ERC-1761 Scoped Approval Interface](https://eips.ethereum.org/EIPS/eip-1761) is suggested.
 The counterpart `isAprrovedForAll` provides introspection into status set by `setApprovalForAll`.
 
 An owner SHOULD be assumed to always be able to operate on their own tokens regardless of approval status, so should SHOULD NOT have to call `setApprovalForAll` to approve themselves as an operator before they can operate on them.  
@@ -553,7 +553,7 @@ balanceOf(baseToken + index, msg.sender); // Get balance of the Non-Fungible tok
 **Standards**
 - [ERC-721 Non-Fungible Token Standard](https://eips.ethereum.org/EIPS/eip-721)
 - [ERC-165 Standard Interface Detection](https://eips.ethereum.org/EIPS/eip-165)
-- [ERC-1538 Transparent Contract Standard (DRAFT)](https://eips.ethereum.org/EIPS/eip-1538)
+- [ERC-1538 Transparent Contract Standard](https://eips.ethereum.org/EIPS/eip-1538)
 - [JSON Schema](https://json-schema.org/)
 - [RFC 2119 Key words for use in RFCs to Indicate Requirement Levels](https://www.ietf.org/rfc/rfc2119.txt)