From 617752afda1b89b69d76af4b48ae700baea51a0d Mon Sep 17 00:00:00 2001 From: Mark Krasner <70119343+mzkrasner@users.noreply.github.com> Date: Mon, 21 Oct 2024 12:19:48 -0400 Subject: [PATCH] Slight formatting modifications for method arguments Co-authored-by: Arjun Hassard --- docs/composedb/examples/taco-access-control.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/composedb/examples/taco-access-control.mdx b/docs/composedb/examples/taco-access-control.mdx index c551149..3504533 100644 --- a/docs/composedb/examples/taco-access-control.mdx +++ b/docs/composedb/examples/taco-access-control.mdx @@ -82,10 +82,10 @@ const encryptedMessageHex = toHexString(messageKit.toBytes()); Data consumers interact with the TACo API via the `decrypt` function. They include the following arguments: -a. Provider -b. Domain -c. EncryptedMessage -d. ConditionContext +a. `provider` +b. `domain` +c. `encryptedMessage` +d. `conditionContext` `conditionContext` is a way for developers to programmatically map methods for authenticating a data consumer to specific access conditions – all executable at decryption time. For example, if the condition involves proving ownership of a social account, authenticate via OAuth.