From 794f34bd32b95650bc1af39ad6596f10ee82ff0f Mon Sep 17 00:00:00 2001
From: Trent McConaghy <5305452+trentmc@users.noreply.github.com>
Date: Tue, 24 Aug 2021 10:34:11 +0200
Subject: [PATCH] Fix #738

---
 content/concepts/compute-to-data.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/concepts/compute-to-data.md b/content/concepts/compute-to-data.md
index 62b6e71c..798bd5f7 100644
--- a/content/concepts/compute-to-data.md
+++ b/content/concepts/compute-to-data.md
@@ -31,11 +31,11 @@ All implementations should set permissions to private by default: upon publishin
 
 ## Architecture Overview
 
-The architecture follows [OEP-12: Compute-to-Data](https://github.com/oceanprotocol/OEPs/tree/master/12) as a spec.
+Here is a sequence diagram for starting a new compute job.
 
 ![Sequence Diagram for computing services](images/Starting New Compute Job.png)
 
-In the above diagram you can see the initial integration supported. It involves the following components/actors:
+This sequence involves the following components/actors:
 
 - Consumers - The end users who need to use some computing services offered by the same Publisher as the data Publisher.
 - Operator-Service - Micro-service that is handling the compute requests.
@@ -109,3 +109,4 @@ The Operator Engine is in charge of retrieving all the workflows registered in a
 - [Tutorial: Writing Algorithms](/tutorials/compute-to-data-algorithms/)
 - [Tutorial: Set Up a Compute-to-Data Environment](/tutorials/compute-to-data/)
 - [Compute-to-Data in Ocean Market](https://blog.oceanprotocol.com)
+- [(Old) Compute-to-Data specs](https://github.com/oceanprotocol-archive/OEPs/tree/master/12) (OEP12)