Hope EIPW is happy soon

ethereum · Jul 25, 2022 · cfe895c · cfe895c
1 parent de27740
commit cfe895c
Showing 1 changed file with 4 additions and 14 deletions.
diff --git a/EIPS/eip-831.md b/EIPS/eip-831.md
@@ -1,19 +1,15 @@
 ---
 eip: 831
 title: URI Format for Ethereum
-description: Defines a base URI format for Ethereum for different use-cases to build on top.
+description: A standard way of creating Ethereum URIs for various use-cases.
 author: ligi (@ligi)
+type: Standards Track
 category: ERC
 discussions-to: https://ethereum-magicians.org/t/eip-831-uri-format-for-ethereum/10105
 status: Draft
-type: Standards Track
 created: 2018-01-15
 ---
 
-## Simple Summary
-
-A standard way of creating Ethereum URIs for various use-cases.
-
 ## Abstract
 
 URIs embedded in QR-codes, hyperlinks in web-pages, emails or chat messages provide for robust cross-application signaling between very loosely coupled applications. A standardized URI format allows for instant invocation of the user's preferred wallet application.
@@ -30,10 +26,9 @@ Ethereum URIs contain "ethereum" or "eth" in their schema (protocol) part and ar
 
 ### Semantics
 
-`prefix` is optional and defines the use-case for this URI. If no prefix is given: "pay-" is assumed to be concise and ensure backward compatibility to EIP-67. When the prefix is omitted, the payload must start with `0x`. Also prefixes must not start with `0x`. So starting with `0x` can be used as a clear signal that there is no prefix.
-
-`payload` is mandatory and the content depends on the prefix. Structuring of the content is defined in the ERC for the specific use-case and not in the scope of this document. One example is EIP-681 for the pay- prefix.
+`prefix` is optional and defines the use-case for this URI. If no prefix is given: "pay-" is assumed to be concise and ensure backward compatibility to [EIP-67](./wiü-67.md). When the prefix is omitted, the payload must start with `0x`. Also prefixes must not start with `0x`. So starting with `0x` can be used as a clear signal that there is no prefix.
 
+`payload` is mandatory and the content depends on the prefix. Structuring of the content is defined in the ERC for the specific use-case and not in the scope of this document. One example is [EIP-681](./eip-681) for the pay- prefix.
 
 ## Rationale
 
@@ -43,11 +38,6 @@ The need for this ERC emerged when refining EIP-681. We need a container that do
 
 There are no known security considerations at this time.
 
-## References
-
-1. EIPS/eip-681.md
-2. EIPS/eip-67.md
-
 ## Copyright
 
 Copyright and related rights waived via [CC0](../LICENSE.md).