From b507b2ea58658bffde388093895cd49c554957b5 Mon Sep 17 00:00:00 2001
From: VolodymyrBg <aqdrgg19@gmail.com>
Date: Fri, 29 Aug 2025 19:19:31 +0300
Subject: [PATCH] fix: correct RFC reference from 8170 to 8174 in
 eip-template.md

---
 eip-template.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/eip-template.md b/eip-template.md
index f18372645b5b6b..6486e1a8e5e4a5 100644
--- a/eip-template.md
+++ b/eip-template.md
@@ -47,7 +47,7 @@ requires: <EIP number(s)> # Only required when you reference an EIP in the `Spec
 <!--
   The Specification section should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Ethereum platforms (besu, erigon, ethereumjs, go-ethereum, nethermind, or others).
 
-  It is recommended to follow RFC 2119 and RFC 8170. Do not remove the key word definitions if RFC 2119 and RFC 8170 are followed.
+  It is recommended to follow RFC 2119 and RFC 8174. Do not remove the key word definitions if RFC 2119 and RFC 8174 are followed.
 
   TODO: Remove this comment before submitting
 -->