From 61de07e92e8c31395b1213f8a068265a80b36684 Mon Sep 17 00:00:00 2001
From: jcstein <46639943+jcstein@users.noreply.github.com>
Date: Wed, 16 Oct 2024 11:45:25 -0400
Subject: [PATCH] style: add to list

---
 cips/cip-tx-limits.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cips/cip-tx-limits.md b/cips/cip-tx-limits.md
index aeaf961..23b22cf 100644
--- a/cips/cip-tx-limits.md
+++ b/cips/cip-tx-limits.md
@@ -19,7 +19,7 @@ This CIP proposes to set limits for the number of PFBs and non-PFBs per block an
 
 1. The number of non-PFB transactions per block is limited to 200 by setting `NonPFBTransactionCap` to 200. `NonPFBTransactionCap` is the maximum number of SDK messages, aside from PFBs, that a block can contain.
 
-It's important to note that these limits are not strictly enforced. While they are defined by the `celestia-app` implementation, a validator could potentially modify the `PrepareProposal` logic, run a custom binary, and produce blocks that exceed the specified limits for PFB or non-PFB transactions.
+1. It's important to note that these limits are not strictly enforced. While they are defined by the `celestia-app` implementation, a validator could potentially modify the `PrepareProposal` logic, run a custom binary, and produce blocks that exceed the specified limits for PFB or non-PFB transactions.
 
 1. The size of a transaction is limited to 2MiB by setting `MaxTxSize` to 2097152, which is 2MiB in bytes. From version v3 and above, in `CheckTx`, `PrepareProposal`, and `ProcessProposal`, each transaction's size is checked against the `appconsts.MaxTxSize` threshold. This ensures that transactions over the limit are rejected or excluded at all stages, from initial submission to execution.