From 25305ccfdb86a33b2cc0ea468d1f85f6f2121f2f Mon Sep 17 00:00:00 2001
From: Malte Poll <1780588+malt3@users.noreply.github.com>
Date: Wed, 17 Apr 2024 15:31:25 +0200
Subject: [PATCH] [wip] remove kata-cc-isolation from docs

---
 dev-docs/coco/policy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-docs/coco/policy.md b/dev-docs/coco/policy.md
index 9e4b91b1c5..6439d9a1de 100644
--- a/dev-docs/coco/policy.md
+++ b/dev-docs/coco/policy.md
@@ -26,7 +26,7 @@ To trust the agent, we need to ensure that the agent only serves permitted reque
 For Contrast, the chain of trust looks like this:
 
 1. The CLI generates a policy and attaches it to the pod definition.
-2. Kubernetes schedules the pod on a node with `kata-cc-isolation` runtime.
+2. Kubernetes schedules the pod on a node with a CoCo runtime.
 3. Containerd takes the node, starts the Kata Shim and creates the pod sandbox.
 4. The Kata runtime starts a CVM with the policy's digest as `HOSTDATA`.
 5. The Kata runtime sets the policy using the `SetPolicy` method.