Update neps/nep-0541.md

Co-authored-by: Jakob Meier <jakob@near.org>

neps/nep-0541.md

@@ -136,7 +136,7 @@ they won't be able to do it.
 
 ## Future possibilities
 
-This NEP should be combined with [NEP-513](https://github.com/near/NEPs/pull/539). They together redefine how congestion is handled and how users can still send transactions during congestion. It is possible to explore more complex mechanism on priority fees when there is congestion. For example, the protocol could require that transactions to a congested shard must attach a priority fee and even place a minimum on the priority fee based on previous chunk's priority fees.
+This NEP should be combined with [NEP-539](https://github.com/near/NEPs/pull/539). They together redefine how congestion is handled and how users can still send transactions during congestion. It is possible to explore more complex mechanism on priority fees when there is congestion. For example, the protocol could require that transactions to a congested shard must attach a priority fee and even place a minimum on the priority fee based on previous chunk's priority fees.
 
 ## Consequences