From 8ef6b2a434862f8bd58fa12d7e2df5e248fbae9b Mon Sep 17 00:00:00 2001 From: Ana Loznianu Date: Thu, 19 Oct 2023 15:17:45 +0300 Subject: [PATCH] updated intro --- developers/compute-to-data/compute-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/compute-to-data/compute-workflow.md b/developers/compute-to-data/compute-workflow.md index c224f1a2..452b8d54 100644 --- a/developers/compute-to-data/compute-workflow.md +++ b/developers/compute-to-data/compute-workflow.md @@ -4,7 +4,7 @@ section: developers description: Understanding the Compute-to-Data (C2D) Workflow --- -🚀 Now that we've introduced the key actors and provided an overview of the process, it's time to delve into the nitty-gritty of the compute workflow.🌟 We'll dissect each step, examining the inner workings of Compute-to-Data (C2D). From data selection to secure computations, we'll leave no stone unturned in this exploration. 💫 Get ready to uncover the intricacies of C2D and how it utilizes various actors and components for a blend of privacy and efficiency. +🚀 Now that we've introduced the key actors and provided an overview of the process, it's time to delve into the nitty-gritty of the compute workflow. We'll dissect each step, examining the inner workings of Compute-to-Data (C2D). From data selection to secure computations, we'll leave no stone unturned in this exploration. For visual clarity, here's an image of the workflow in action! 🖼️✨