Merge pull request #367 from HoomanDgtl/main

remove: duplicate

src/content/Docs/other-resources/marketplace/index.md

@@ -33,6 +33,8 @@ In a very simple reverse auction:
 2. Providers bid on orders.
 3. Tenants choose winning bids and create leases.
 
+### Lifecycle of a Deployment
+
 A typical application deployment on Akash will follow this flow:
 
 1. The tenant describes their desired deployment in \[SDL], called a [deployment](#deployment).
@@ -51,20 +53,6 @@ The general workflow is:
 2. Providers bid on orders.
 3. Tenants choose winning bids and create leases.
 
-### Lifecycle of a Deployment
-
-The lifecycle of a typical application deployment is as follows:
-
-1. The tenant describes their desired deployment in \[SDL], called a [deployment](#deployment).
-2. The tenant submits that definition to the blockchain.
-3. Their submission generates an [order](#order) on the marketplace.
-4. Providers that would like to fulfill that order [bid](#bid) on it.
-5. After some period of time, a winning [bid](#bid) for the [order](#order) is chosen, and a [lease](#lease) is created.
-6. Once a [lease](#lease) has been created, the tenant submits a [manifest](/docs/getting-started/stack-definition-language/) to the provider.
-7. The provider executes workloads as instructed by the [manifest](/docs/getting-started/stack-definition-language/).
-8. The workload is running - if it is a web application it can be visited
-9. The provider or tenant eventually closes the [lease](#lease), shutting down the workload.
-
 ## Payments
 
 Leases are paid from deployment owner (tenant) to the provider through a deposit & withdraw mechanism.