Minor corrections.

otterize · Sep 7, 2023 · f354c0f · f354c0f
1 parent 06419de
commit f354c0f
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/docs/quick-tutorials/k8s-network-policies.mdx b/docs/quick-tutorials/k8s-network-policies.mdx
@@ -237,8 +237,7 @@ If you've attached Otterize OSS to Otterize Cloud, go back to see the [access gr
 It's now clear what happened:
 1. The server is now protected, and is also blocking some of its clients. Click on it to see what to do about it.
 2. Calls from **[client]** are declared and therefore allowed (green line).
-3. Calls from **[client-other]** are not declared and therefore would be blocked (yellow line). Click on the line to see what to do about it.
-4. By the way, the two clients themselves are unprotected -- though we don't detect any traffic to them, we cannot be certain they don't expose addressable endpoints.
+3. Calls from **[client-other]** are not declared and therefore blocked (red line). Click on the line to see what to do about it.
 
 :::tip Done!
 Otterize did its job of both protecting the server *and* allowing intended access.