remove terminology.md and all links to it

content/concepts/terminology.md

@@ -1,39 +0,0 @@
----
-title: Terminology
-description: Terminology specific to Ocean Protocol.
----
-
-## Ocean Network
-
-An _Ocean network_ is any EVM-compatible network where [Ocean smart contracts](https://github.com/oceanprotocol/ocean-contracts) are deployed. These include:
-
-- [Ethereum Mainnet](https://www.ethereum.org)
-- Ethereum [test networks](/concepts/testnets/)
-
-## Data Service, Data Asset, Datatoken
-
-A _data service_ may serve up a dataset or a compute service like Compute-to-Data. It's characterized by a url.
-
-Each _data asset_ is represented by an ERC20 _datatoken_.
-
-You can access a data service if you send 1.0 datatokens to the Provider.
-
-## Data Publisher, Provider
-
-A _data publisher_ is someone who has data services that they want to sell. An example is an almond distributor with 30 years of data about almond sales.
-
-A _Provider_ is a service that mediates access to assets on behalf of data owners or data service providers.
-
-> Initially, most data publishers will also be Providers.
-
-## Data Consumer
-
-A _data consumer_ is someone who buys a data asset, then consumes it by interacting with the _Provider_.
-
-## Data Market
-
-A data market is a service where publishers can list what assets they have, and consumers can see what's available then buy it.
-
-## Metadata
-
-Metadata is information about the data asset. In Ocean, metadata is stored on-chain, but marketplaces may have a local cache for faster search.

content/setup/marketplace.md

@@ -3,18 +3,18 @@ title: Set Up a Marketplace
 description: Set up and run a data marketplace in an Ocean network.
 ---
 
-In Ocean Protocol, marketplaces and publishers play different roles (outlined in the [Terminology page](/concepts/terminology/)), but both roles can be played by the same person or organization. Initially, we anticipate that will be the most common setup. As a result, this guide explains how to set up and run a combined marketplace/publisher (for now).
+In Ocean Protocol, marketplaces and publishers are different roles, but one person or organization can play both roles. Initially, we anticipate that will be the most common setup. As a result, this guide explains how to set up and run a combined marketplace/publisher (for now).
 
 ## An Outline of the Steps
 
-1. Have [assets](/concepts/terminology/#asset-or-data-asset) to offer in your marketplace.
+1. Have data assets to offer in your marketplace.
 1. Prepare those assets to work with Ocean Protocol.
 1. Develop a marketplace/publisher app.
 1. Run everything you need to run in production.
 
 ## Prepare Assets
 
-At the time of writing, the following kinds of [assets](/concepts/terminology/#asset-or-data-asset) were supported:
+At the time of writing, the following kinds of assets were supported:
 
 - data sets stored in Azure Storage (i.e. with "core.windows.net" in their URL). See [the tutorial about setting up Azure Storage to work with Ocean Protocol](/tutorials/azure-for-brizo/).
 - data sets stored in Amazon S3 storage (i.e. with "s3://" in their URL). See [the tutorial about setting up Amazon S3 storage to work with Ocean Protocol](/tutorials/amazon-s3-for-brizo/).

content/tutorials/react-publish-algorithm.md

@@ -13,7 +13,7 @@ Open `src/Compute.js` from your `marketplace/` folder.
 
 ## Define Asset
 
-First, let's add the [asset](/concepts/terminology/#asset-or-data-asset) that we want to publish.
+First, let's add the data asset that we want to publish.
 
 To do that, we need to define the Algorithm asset based on the [OEP-08](https://github.com/oceanprotocol/OEPs/tree/master/8) metadata structure. An algorithm asset can have multiple `files` attached to it and each file's `url` value will be encrypted during the publish process.
 

content/tutorials/react-publish-data-set.md

@@ -13,7 +13,7 @@ Open `src/index.js` from your `marketplace/` folder.
 
 ## Define Asset
 
-First, let's add the [asset](/concepts/terminology/#asset-or-data-asset) that we want to publish.
+First, let's add the asset that we want to publish.
 
 To do that, we need to define the asset based on the [OEP-08](https://github.com/oceanprotocol/OEPs/tree/master/8) metadata structure. An asset can have multiple `files` attached to it and each file's `url` value will be encrypted during the publish process. To download that file later on, this value will be decrypted during the consume process.
 

docs/content.md

@@ -99,7 +99,7 @@ Note: The `description` value will be rendered on-page below the title, and it w
 1. Don't include the page title or description in the Markdown section. That is, don't begin the Markdown content with `# This is the Title in Title Case`. Just write as if that were already there.
 2. start your heading levels with `h2`, so `## My heading`
 3. Internal links to other docs pages should be:
-   - to a absolute URL without the host, that looks like `/concepts/terminology/` with slashes on the beginning and end, and with no `.md` or `.html` at the end (before the last slash).
+   - to a absolute URL without the host, that looks like `/concepts/introduction/` with slashes on the beginning and end, and with no `.md` or `.html` at the end (before the last slash).
    - when linking from external repos, to the _full absolute URL_, such as `https://docs.oceanprotocol.com/hello/you-are-awesome/`
 4. no TOC please, this will be generated automatically from all headings
 5. for images and media, you can keep them in the original repo. Images will be automatically grabbed by the docs site on querying. When doing that, docs site will generate all sorts of image sizes to handle proper responsive images, so no need to keep an eye on image dimensions or file sizes