From 7976dc2d759e48fe9a5e578be04318e863a64d34 Mon Sep 17 00:00:00 2001 From: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> Date: Tue, 27 Aug 2024 13:56:27 +0200 Subject: [PATCH] Update platform-includes/enriching-events/add-attachment/python.mdx Co-authored-by: Liza Mock --- platform-includes/enriching-events/add-attachment/python.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-includes/enriching-events/add-attachment/python.mdx b/platform-includes/enriching-events/add-attachment/python.mdx index ee503ed1889d1..8cfcb99e7c913 100644 --- a/platform-includes/enriching-events/add-attachment/python.mdx +++ b/platform-includes/enriching-events/add-attachment/python.mdx @@ -1,4 +1,4 @@ -Attachments live on the [`Scope`](/platforms/python/enriching-events/scopes/). The SDK sends all attachments on a given `Scope` with every non-transaction event captured within the `Scope`. Optionally, an attachment can be sent with all events, including transactions, when the attachment is added with the `add_to_transactions` option set to `True`. +Because attachments live on the [`Scope`](/platforms/python/enriching-events/scopes/), the SDK sends all attachments on a given `Scope` with every non-transaction event captured within the `Scope`. It's also possible to send an attachment with all events, including transactions by setting the `add_to_transactions` option to `True`. ```python # Add an attachment