From 5733790973f48c8771d8f0aee17455059b41ecd7 Mon Sep 17 00:00:00 2001
From: Alex Morris <37120777+alexander-morris@users.noreply.github.com>
Date: Thu, 3 Dec 2020 11:22:45 -0400
Subject: [PATCH] more typos

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

diff --git a/content/concepts/compute-to-data.md b/content/concepts/compute-to-data.md
index 1bdda340..460c6797 100644
--- a/content/concepts/compute-to-data.md
+++ b/content/concepts/compute-to-data.md
@@ -36,7 +36,7 @@ in charge of managing the workflow executing requests.
 
 Typically the Operator Service is integrated from Ocean Provider, but can be called independently if it.
 
-The Operator Service is in charge of stablishing the communication with the K8s cluster, allowing to:
+The Operator Service is in charge of establishing the communication with the K8s cluster, allowing it to:
 
 - Register workflows as K8s objects
 - List the workflows registered in K8s
@@ -65,7 +65,7 @@ The main responsibilities are:
 In the above diagram you can see the initial integration supported. It involves the following components/actors:
 
 - Data Scientists/Consumers - The end users who need to use some computing services offered by the same Publisher as the data Publisher.
-- Ocean Keeper - In charge of enforcing the Service Agreement by tracing conditions.
+- Ocean Keeper - In charge of enforcing the Service Agreement by tracking conditions.
 - Operator-Service - Micro-service that is handling the compute requests.
 - Operator-Engine - The computing systems where the compute will be executed.