diff --git a/content/concepts/components.md b/content/concepts/components.md
index 3f8ad18c..ac841108 100644
--- a/content/concepts/components.md
+++ b/content/concepts/components.md
@@ -7,15 +7,15 @@ Before reading this page, you should understand some [Ocean-specific terminology
## Aquarius
-Aquarius provides an API to an off-chain database ("OceanDB") to store and manage metadata about data assets: the assets listed in that marketplace. Every marketplace must run an instance of Aquarius.
-
-The off-chain database might be MongoDB, Elasticsearch or BigchainDB.
+Marketplaces run Aquarius to store and manage metadata about the data assets available in their marketplace. It provides an HTTP API for interacting with an off-chain database ([OceanDB](/concepts/components/#oceandb-drivers)).
## Brizo
-Publishers run Brizo to manage access control to assets on behalf of asset owners or data service providers.
+Publishers run Brizo to manage interactions with marketplaces and consumers.
+It interacts with the publisher's cloud and/or on-premise infrastructure.
+The most basic scenario for a publisher is to provide access to the assets the publisher owns or manages, but [Brizo can do much more](/concepts/architecture/#brizo).
@@ -29,7 +29,7 @@ where the associated blockchain network is running the Ocean Protocol
-See also: [Set Up a Keeper](/setup/keeper/)
+See also: [Run a Keeper](/setup/keeper/)
## Pleuston
@@ -63,7 +63,7 @@ These drivers are extended from a high-level module implementing OceanDB functio
A [Parity Secret Store](https://wiki.parity.io/Secret-Store): software for distributed key pair generation, distributed key storage, and threshold retrieval. It's used to store asset access-control keys.
-We have created multiple clients for integrating the Parity Secret Store into Ocean:
+There are several clients for integrating the Parity Secret Store into Ocean: