Update EIPS/eip-4812.md

Co-authored-by: Pandapip1 <45835846+Pandapip1@users.noreply.github.com>
ethereum · Jul 19, 2022 · 9cf1224 · 9cf1224
1 parent 99909f4
commit 9cf1224
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/EIPS/eip-4812.md b/EIPS/eip-4812.md
@@ -23,7 +23,7 @@ There is currently no standard in place to codify how to ingest blockchain data.
 We aim to facilitate testing and formulation of tests through an explicit format developers can use to represent contracts and transactions in detail, as well as the expected outcomes.
 
 ## Specification
-The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC 2119](#ref-RFC2119) and [RFC 8174](#ref-RFC8174)
+The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119
 
 ## Rationale
 The EEA is aiming to standardize Enterprise Ethereum clients, including facets like cross-chain activities and secure deployment of smart contracts. The Testing and Certification Working Group is working in earnest towards creating a test suite that allows developers to certify their implementation is matching the specification of the Enterprise Ethereum standard.