From 56fa823e7d39bf8ebf79a33ad28fadbf1ac16068 Mon Sep 17 00:00:00 2001
From: Kolby Moroz Liebl <31669092+KolbyML@users.noreply.github.com>
Date: Wed, 23 Oct 2024 17:56:10 -0600
Subject: [PATCH] Update ping-custom-payload-extensions.md

---
 ping-payload-extensions/ping-custom-payload-extensions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ping-payload-extensions/ping-custom-payload-extensions.md b/ping-payload-extensions/ping-custom-payload-extensions.md
index ce46c6e..be5cce1 100644
--- a/ping-payload-extensions/ping-custom-payload-extensions.md
+++ b/ping-payload-extensions/ping-custom-payload-extensions.md
@@ -88,7 +88,7 @@ It is for Portal implementations which want to see what extensions a peer suppor
 Non-required extension offer a way for Portal implementations to offer extended functionality to its users without requiring every Portal implementing party to agree to a new feature. This allows for a diverse set of use cases to be fulfilled without requiring every implementer implement every extension, or requiring the need to bloat the minimal [Portal-Wire-Protocol](../portal-wire-protocol.md) with new `Message Types`.
 
 ## Does implementing non-standard-extensions require a hardfork?
-No only changing standard extensions requires a hard fork.
+No only changing a sub-networks standard extension requires a hard fork.
 
 
 ## How do sub-network standard extension's work