From 04280b3e882994f2ea0d2c056b94c2ab6b882786 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Tue, 1 Oct 2024 18:55:53 -0400
Subject: [PATCH] Update marketplace.md

---
 specs/marketplace.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/specs/marketplace.md b/specs/marketplace.md
index 5acce4b..87178a1 100644
--- a/specs/marketplace.md
+++ b/specs/marketplace.md
@@ -33,17 +33,6 @@ Implemented as a smart contract on an EVM-compatible blockchain,
 the marketplace enables various scenarios where nodes assume one or
 more roles to maintain a reliable persistence layer for users.
 
-### Definitions
-
-| Terminology               | Description                                                                                                               |
-|---------------------------|---------------------------------------------------------------------------------------------------------------------------|
-| Storage Provider (SP)      | A node in the Codex network that provides storage services to the marketplace.                                             |
-| Validator                  | A node that assists in identifying missing storage proofs.                                                                |
-| Client                     | A node that interacts with other nodes in the Codex network to store, locate, and retrieve data.                           |
-| Storage Request or Request | A request created by a client node to persist data on the Codex network.                                                  |
-| Slot or Storage Slot       | A space allocated by the storage request to store a piece of the request's dataset.              |
-| Smart Contract             | A smart contract implementing the marketplace functionality.                                                               |
-| token               | ERC20-based token used within the Codex network.     |
 
 ## Semantics 
 
@@ -56,6 +45,18 @@ collaterals, and storage proofs.
 A node that wishes to participate in the Codex persistence layer MUST implement one or
 more roles described below.
 
+### Definitions
+
+| Terminology               | Description                                                                                                               |
+|---------------------------|---------------------------------------------------------------------------------------------------------------------------|
+| Storage Provider (SP)      | A node in the Codex network that provides storage services to the marketplace.                                             |
+| Validator                  | A node that assists in identifying missing storage proofs.                                                                |
+| Client                     | A node that interacts with other nodes in the Codex network to store, locate, and retrieve data.                           |
+| Storage Request or Request | A request created by a client node to persist data on the Codex network.                                                  |
+| Slot or Storage Slot       | A space allocated by the storage request to store a piece of the request's dataset.              |
+| Smart Contract             | A smart contract implementing the marketplace functionality.                                                               |
+| token               | ERC20-based token used within the Codex network.     |
+
 ### Roles
 
 A node can assume one of the three main roles in the network: the client, SP node, and validator.