From 04e283b258aa3e049e728189024a37bbf8151467 Mon Sep 17 00:00:00 2001
From: hanako mumei <81144685+2501babe@users.noreply.github.com>
Date: Mon, 21 Oct 2024 07:48:25 -0700
Subject: [PATCH] edits for clarity

---
 proposals/0186-transaction-data-size-specification.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/proposals/0186-transaction-data-size-specification.md b/proposals/0186-transaction-data-size-specification.md
index 7d0e23d6..b01b483a 100644
--- a/proposals/0186-transaction-data-size-specification.md
+++ b/proposals/0186-transaction-data-size-specification.md
@@ -16,7 +16,8 @@ Before a transaction can be executed, every account it may read from or write to
 must be loaded, including any programs it may call. The amount of data a
 transaction is allowed to load is capped, and if it exceeds that limit, loading
 is aborted. This functionality is already implemented in the validator. The
-purpose of this SIMD is to explicitly define how transaction size is calculated.
+purpose of this SIMD is to explicitly define how loaded transaction data size is
+calculated.
 
 ## Motivation
 
@@ -139,5 +140,5 @@ This SIMD requires a feature gate.
 
 ## Backwards Compatibility
 
-Transactions that call LoaderV3 programs via CPI and are extremely close to the
-64MiB limit may now exceed it.
+Transactions that currently have a total transaction data size close to the
+64MiB limit, which call LoaderV3 programs via CPI, may now exceed it and fail.