From 75c262693064ed6376d02936f1209f436e6bff9a Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Wed, 9 Oct 2024 20:37:03 -0400
Subject: [PATCH] Update marketplace.md

---
 specs/marketplace.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/specs/marketplace.md b/specs/marketplace.md
index 242c67d..94827fc 100644
--- a/specs/marketplace.md
+++ b/specs/marketplace.md
@@ -257,8 +257,8 @@ In response, the SP node SHOULD stop its current operation and attempt to fill a
 
 ### Proving
 
-
-Once an SP node fills a slot, it MUST submit proofs to the smart contract when a challenge is issued by the contract. SP nodes SHOULD detect that a proof is required for the current period using the `isProofRequired(slotId)` function, 
+Once an SP node fills a slot, it MUST submit proofs to the smart contract when a challenge is issued by the contract.
+SP nodes SHOULD detect that a proof is required for the current period using the `isProofRequired(slotId)` function, 
 or that it will be required using the `willProofBeRequired(slotId)` function in the case that the [pointer is in downtime](https://github.com/codex-storage/codex-research/blob/41c4b4409d2092d0a5475aca0f28995034e58d14/design/storage-proof-timing.md).
 
 Once an SP node knows it has to provide a proof,