Update eip-5269.md

EIPS/eip-5269.md

@@ -24,6 +24,8 @@ interface as `minorEIPIdentifier= keccak256("ERC721Metadata")`.
 
 It also proposes an event to allow smart contracts to optionally declare the EIPs they support.
 
+This ERC is supersedable, see Specification-0 how it can be superseded.
+
 ## Motivation
 
 This EIP is created as a competing standard for [EIP-165](./eip-165.md).
@@ -56,6 +58,8 @@ convert a function method or whole interface in any EIP/ERC in the bytes4 EIP-16
 
 In the following description, we use EIP and ERC inter-exchangeably. This was because while most of the time the description applies to an ERC category of the Standards Track of EIP, the ERC number space is a subspace of EIP number space and we might sometimes encounter EIPs that aren't recognized as ERCs but has behavior that's worthy of a query.
 
+0. *This ERC is supersedable*. When a new ERC superceeding this ERC is recognized by the Author of this ERC, Author SHOULD update this ERC with an apendix section or a Meta ERC indicating the superceeding ERC. Implementers are strongly RECOMMENDED to check for superceeding ERC if use later superceeding ERC recognized by the author.
+
 1. Any compliant smart contract MUST implement the following interface
 
 ```solidity