quickstart changes

content/setup/keeper.md

@@ -18,4 +18,4 @@ Barge deploys the keeper contracts to whatever keeper nodes are deployed locally
 
 If you're interested in running a keeper node (as a voting _authority node_) in the [Pacific Network](/concepts/pacific-network/) or the [Nile Testnet](/concepts/testnets/#the-nile-testnet), then email <a href="mailto:info@oceanprotocol.com">info@oceanprotocol.com</a>.
 
-Note: The dev-ocean repository contains [a guide for running a keeper node in the Nile Testnet](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/devops/keeper-setup.md).
+> The dev-ocean repository contains a guide for [running a keeper node in the Nile Testnet](https://github.com/oceanprotocol/dev-ocean/blob/master/doc/devops/keeper-setup.md).

content/setup/marketplace.md

@@ -50,8 +50,6 @@ Of course, you could always write your own Squid library in the language of your
 
 ## Run Everything You Need to Run in Production
 
-**At the time of writing, there was no production-ready Ocean Protocol network, but once one _does_ exist, the following must be done to run your marketplace/publisher app in production.**
-
 When developing your marketplace/publisher app, you will probably use Barge to run all the Ocean Protocol components on your local machine. When it comes time to go to production, you will have to run some of those components in production:
 
 - Your marketplace/publisher app

content/setup/quickstart.md

@@ -1,15 +1,11 @@
 ---
 title: Quickstart
-description: Do a quick test drive.
+description: Do a quick test drive of Ocean Protocol components or interact with the network by using Jupyter notebooks.
 ---
 
-## Option 1
+## 🐳 Developers: Barge
 
-You can [try some free, online Jupyter notebooks](/tutorials/jupyter-notebooks/) that connect to a live Ocean test network.
-
-## Option 2
-
-You can run and try every [Ocean software component](/concepts/components/) in your local machine, all at once, using Docker Compose. Ocean Protocol software developers do this often, to test their code against all the other Ocean components.
+Developers can run and try every [Ocean software component](/concepts/components/) on their local machine, all at once, using Docker Compose. Ocean Protocol software developers do this often, to test their code against all the other Ocean components.
 
 ```bash
 git clone https://github.com/oceanprotocol/barge.git
@@ -19,16 +15,18 @@ cd barge/
 
 Seeing the dolphin means it's working:
 
-![start_ocean.sh](images/dolphin.png)
+![Output of start_ocean.sh](images/dolphin.png)
 
-Once everything is up and running, you can interact with the components. For example, to see the Aquarius API docs, go to:
+Once everything is up and running, you can interact with the components. E.g. once [Pleuston](/concepts/components/#pleuston) is running, you can interact with it at:
 
-[http://localhost:5000/api/v1/docs](http://localhost:5000/api/v1/docs)
+- [http://localhost:3000/](http://localhost:3000/)
 
-Once Pleuston is running, you can interact with it at:
-
-[http://localhost:3000/](http://localhost:3000/)
-
-For the details of what components are running, see the [Ocean Protocol barge repository](https://github.com/oceanprotocol/barge).
+For the details of what components are running, see the [`barge` repository](https://github.com/oceanprotocol/barge).
 
 <repo name="barge"></repo>
+
+## 👩‍🔬 Data Science: Jupyter notebooks
+
+You can try some free, online Jupyter notebooks that connect to a live Ocean test network.
+
+- [Tutorial: Jupyter Notebooks](/tutorials/jupyter-notebooks/)

gatsby-config.js

@@ -75,7 +75,7 @@ module.exports = {
                             maxWidth: 666,
                             quality: 80,
                             withWebp: true,
-                            linkImagesToOriginal: true,
+                            linkImagesToOriginal: false,
                             showCaptions: true
                         }
                     },