ERC-6860: Renaming of "ERC" to "EIP" inside.

EIPS/eip-6860.md

@@ -23,7 +23,7 @@ EVMMessage {
 }
 ```
 
-⚠️ This proposal updates [ERC-4804](./eip-4804.md) with minor corrections, clarifications and modifications.
+⚠️ This proposal updates [EIP-4804](./eip-4804.md) with minor corrections, clarifications and modifications.
 
 ## Motivation
 
@@ -54,6 +54,7 @@ where
 - **query** is an optional component containing a sequence of attribute-value pairs separated by "&".
 
 The URL must be encoded with URI percent-encoding (RFC 3968) with rules very similar to the RFC. Per component, the rules are :
+
 - **userinfo** : Identical to **userinfo** as defined in RFC 3986 Appendix A.
 - **contractName** : Identical to **reg-name** as defined in RFC 3986 Appendix A.
 - **chainid** : Identical to **port** as defined in RFC 3986 Appendix A.
@@ -129,7 +130,7 @@ In the auto mode, if **path** is empty or "/", then the protocol will call the t
       - Quantities (integers) will be encoded as hex, prefix with "0x", the most compact representation (slight exception: zero should be represented as "0x0")
       - Boolean and strings will be native JSON boolean and strings
 
-    If multiple **returns** attributes are present, the value of the last **returns** attribute will be applied. Note that **returnTypes** is the alias of **returns**, but it is not recommended to use and is mainly for [ERC-4804](./eip-4804.md) backward-compatible purpose.
+    If multiple **returns** attributes are present, the value of the last **returns** attribute will be applied. Note that **returnTypes** is the alias of **returns**, but it is not recommended to use and is mainly for [EIP-4804](./eip-4804.md) backward-compatible purpose.
 
 ### Examples
 
@@ -203,26 +204,26 @@ where the contract ”0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48“ is in auto m
 
 The protocol will find the address of **vitalik.eth** from ENS on chainid 1 (Mainnet) and then call the method "balanceOf(address)" of the address. The returned data from the call of the contract will be treated as raw bytes and will be encoded in JSON format like `["0x000000000000000000000000000000000000000000000000000009184e72a000"]` and returned to the frontend, with the information that the MIME type is ``application/json``.
 
-### Changes versus [ERC-4804](./eip-4804.md)
+### Changes versus [EIP-4804](./eip-4804.md)
 
 #### Corrections
 
-- Manual mode : [ERC-4804](./eip-4804.md) stipulates that there is no interpretation of the path [ "?" query ]. This ERC indicates that there is in fact an interpretation of the path, for MIME type determination purpose.
-- Auto mode : If there is no **returns** attribute in **query**, [ERC-4804](./eip-4804.md) stipulates that the returned data is treated as ABI-encoded bytes32. This ERC indicates that in fact the returned data is treated as ABI-encoded bytes.
+- Manual mode : [EIP-4804](./eip-4804.md) stipulates that there is no interpretation of the path [ "?" query ]. This EIP indicates that there is in fact an interpretation of the path, for MIME type determination purpose.
+- Auto mode : If there is no **returns** attribute in **query**, [EIP-4804](./eip-4804.md) stipulates that the returned data is treated as ABI-encoded bytes32. This EIP indicates that in fact the returned data is treated as ABI-encoded bytes.
 
 #### Clarifications
 
-- URL format: This ERC indicates that the URL should be in ASCII format.
-- Resolve mode: This ERC indicates more details on how the resolve mode is determined.
-- Manual mode : This ERC indicates how to deal with URI-percent-encoding, the return data, and how the MIME type is determined.
-- Auto mode : This ERC indicates in more details the encoding of the argument values, as well as the format and handling of the **returns** value.
-- Examples : This ERC add more details to the examples.
+- URL format: This EIP indicates that the URL should be in ASCII format.
+- Resolve mode: This EIP indicates more details on how the resolve mode is determined.
+- Manual mode : This EIP indicates how to deal with URI-percent-encoding, the return data, and how the MIME type is determined.
+- Auto mode : This EIP indicates in more details the encoding of the argument values, as well as the format and handling of the **returns** value.
+- Examples : This EIP add more details to the examples.
 
 #### Modifications
 
-- Protocol name: [ERC-4804](./eip-4804.md) mentionned ``ethereum-web3://`` and ``eth-web3://``, these are removed.
-- Auto mode: Supported types: [ERC-4804](./eip-4804.md) supported only uint256, bytes32, address, bytes, and string. This ERC add more types.
-- Auto mode: Encoding of returned integers when a **returns** attribute is specified: [ERC-4804](./eip-4804.md) suggested in example 5 to encode integers as strings. This ERC indicates to follow the Ethereum JSON RPC spec and encode integers as a hex string, prefixed with "0x".
+- Protocol name: [EIP-4804](./eip-4804.md) mentionned ``ethereum-web3://`` and ``eth-web3://``, these are removed.
+- Auto mode: Supported types: [EIP-4804](./eip-4804.md) supported only uint256, bytes32, address, bytes, and string. This EIP add more types.
+- Auto mode: Encoding of returned integers when a **returns** attribute is specified: [EIP-4804](./eip-4804.md) suggested in example 5 to encode integers as strings. This EIP indicates to follow the Ethereum JSON RPC spec and encode integers as a hex string, prefixed with "0x".
 
 ## Rationale