From 2b8673c3555532a0bdd933103d6c63d1ad7763b1 Mon Sep 17 00:00:00 2001 From: Amarantha Kulkarni Date: Tue, 12 Aug 2025 16:23:50 -0700 Subject: [PATCH] Update docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md Co-authored-by: Rome Reginelli --- .../tokens/decentralized-exchange/permissioned-dexes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md b/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md index 73e7ff575b..e9a3e8bf58 100644 --- a/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md +++ b/docs/concepts/tokens/decentralized-exchange/permissioned-dexes.md @@ -94,7 +94,7 @@ Reasons a permissioned offer can become invalid include: Like with unfunded offers, it is possible for an offer to become temporarily invalid and then become valid again. For example, if a trader's credential that grants access to a permissioned domain expires, their offers in the corresponding permissioned DEX would be invalid; but if they get the credential renewed, any offers that hadn't already been removed automatically become valid again. -### Limitations for Permissioned DEXes +### Limitations of Permissioned DEXes The permissioned DEXes feature is enabled by the **PermissionedDEX** amendment, and relies on the [Credentials](../../decentralized-storage/credentials.md) and [Permissioned Domains](./permissioned-domains.md) amendments, so it cannot be used until _all_ of those amendments have been enabled.