From 046a9588207ee821a3f801bb26e93fe18b35057d Mon Sep 17 00:00:00 2001 From: William Banfield <4561443+williambanfield@users.noreply.github.com> Date: Mon, 28 Feb 2022 15:40:11 -0500 Subject: [PATCH] Update docs/rfc/rfc-015-abci++-tx-mutation.md Co-authored-by: M. J. Fromberger --- docs/rfc/rfc-015-abci++-tx-mutation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rfc/rfc-015-abci++-tx-mutation.md b/docs/rfc/rfc-015-abci++-tx-mutation.md index d04506440..bedfd927e 100644 --- a/docs/rfc/rfc-015-abci++-tx-mutation.md +++ b/docs/rfc/rfc-015-abci++-tx-mutation.md @@ -10,7 +10,7 @@ The specification of ABCI++ details a mechanism for proposers to replace transactions in the proposed block. This scheme requires the proposer to construct new transactions and mark these new transactions as replacing other removed transactions. The specification -is somewhat ambiguous as to how the replacement may be communicated to peer nodes. +is ambiguous as to how the replacement may be communicated to peer nodes. This RFC discusses issues with this mechanism and possible solutions. ## Background