diff --git a/using-ocean-market/asset-hosting.md b/using-ocean-market/asset-hosting.md
index 45ea3873..119e152c 100644
--- a/using-ocean-market/asset-hosting.md
+++ b/using-ocean-market/asset-hosting.md
@@ -3,15 +3,6 @@ title: Publish assets using hosting services
 description: Tutorial to publish assets using hosting services like Arweave, AWS, and Azure.
 ---
 
-## Table of contents
-
-1. [Overview](#overview)
-2. [Decentralized hosting](#decentralized-hosting)
-   - [Arweave](#arweave)
-3. [Centralized hosting](#centralized-hosting)
-   - [AWS](#aws)
-   - [Azure](#azure-storage)
-
 ## Overview
 
 To publish on the Ocean Marketplace, publishers must first host their assets. It is up to the asset publisher to decide where to host the asset. For example, a publisher can store the content on decentralized storage like Arweave or choose a centralized solution like their AWS server, private cloud server, or other third-party hosting services. Through publishing, the information required to access the asset is encrypted and stored as a part of DDO on the blockchain. Buyers don't have access directly to this information, but they interact with the Provider, which decrypts it and acts as a proxy to serve the asset. The DDO only stores the location of the file, which is accessed on-demand by the Provider. Implementing a security policy that allows only the Provider to access the file and blocks requests from other unauthorized actors is recommended. One of the possible ways to achieve this is to allow only the Provider's IP address to access the data. But, not all hosting services provide this feature. So, the publishers must consider the security features while choosing a hosting service.