Issue-#960: Use word 'buy'/'download' instead of

content/tutorials/asset-level-permissions.md

@@ -17,7 +17,7 @@ Since asset-level permissions are in the DDO, and the DDO is controlled by the p
 All and deny lists are not enabled by default in Ocean Market. You need to edit the environmental variables to enable this feature in your fork of Ocean Market:
 
 - To enable allow and deny lists you need to add the following environmental variable to your .env file in your fork of Ocean Market: `GATSBY_ALLOW_ADVANCED_SETTINGS="true"`
-- Publishers in your market will now have the ability to restrict who can consume their datasets.
+- Publishers in your market will now have the ability to restrict who can buy their datasets.
 
 ## Usage 
 

content/tutorials/market-level-permissions.md

@@ -1,13 +1,13 @@
 ---
 title: Market-Level Permissions
-description: Control who can publish, consume or browse data
+description: Control who can publish, buy or browse data
 ---
 
 ## Introduction
 
 For market-level permissions, Ocean implements a role-based access control server (RBAC server). It implements restrictions at the user level, based on the user’s role (credentials). The RBAC server is run & controlled by the marketplace owner. Therefore permissions at this level are at the discretion of the marketplace owner. 
 
-The RBAC server is the primary mechanism for restricting your users ability to publish, consume, or browse assets in the market.  
+The RBAC server is the primary mechanism for restricting your users ability to publish, buy, or browse assets in the market.  
 
 ## Roles
 
@@ -20,7 +20,7 @@ The RBAC server defines four different roles:
 
 ### Admin/ Publisher
 
-Currently users with either the admin or publisher roles will be able to use the Market without any restrictions. They can publish, consume and browse datasets. 
+Currently users with either the admin or publisher roles will be able to use the Market without any restrictions. They can publish, buy and browse datasets. 
 
 ### Consumer
 

content/tutorials/permissions.md

@@ -1,15 +1,15 @@
 ---
 title: Fine-Grained Permissions 
-description: Control who can publish, consume or browse data
+description: Control who can publish, download or browse data
 ---
 
 
 A large part of Ocean is about access control, which is primarily handled by datatokens. Users can access a resource (e.g. a file) by redeeming datatokens for that resource. We recognize that enterprises and other users often need more precise ways to specify and manage access, and we have introduced fine-grained permissions for these use cases. 
 Fine-grained permissions mean that access can be controlled precisely at two levels:
 
-- [Marketplace-level permissions](./market-level-permissions) for browsing, consuming or publishing within a marketplace frontend.
+- [Marketplace-level permissions](./market-level-permissions) for browsing, downloading or publishing within a marketplace frontend.
 
-- [Asset-level permissions](./asset-level-permissions) on consuming a specific asset.
+- [Asset-level permissions](./asset-level-permissions) on downloading a specific asset.
 
 The fine-grained permissions features are designed to work in forks of Ocean Market. We have not enabled them in Ocean Market itself, to keep Ocean Market open for everyone to use. On the front end, the permissions features are easily enabled by setting environment variables.