From a0e95558909f0be376fc09095ddb222052e1ba95 Mon Sep 17 00:00:00 2001 From: apoorve73 Date: Fri, 3 May 2024 18:45:15 +0530 Subject: [PATCH] fix: example heading under new enemy problem section --- pages/spicedb/concepts/zanzibar.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/spicedb/concepts/zanzibar.mdx b/pages/spicedb/concepts/zanzibar.mdx index e0036f61..d1fc11e0 100644 --- a/pages/spicedb/concepts/zanzibar.mdx +++ b/pages/spicedb/concepts/zanzibar.mdx @@ -58,7 +58,7 @@ This term was first introduced in the Zanzibar paper where solving this problem >Specifically, our clients care about preventing the "new enemy" problem, which can arise when we fail to respect the ordering between ACL updates or when we apply old ACLs to new content. >Consider these two examples: > ->**Example B: Misapplying old ACL to new content** +>**Example A: Neglecting ACL update order** > >1. Alice removes Bob from the ACL of a folder; >2. Alice then asks Charlie to move new documents to the folder, where document ACLs inherit from folder ACLs;