From 2f281389d0576510bbca1e255bbe79a34c334f9d Mon Sep 17 00:00:00 2001 From: Celso Martinho Date: Tue, 22 Jul 2025 12:23:02 +0100 Subject: [PATCH] typo --- .../docs/email-routing/setup/email-routing-addresses.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/email-routing/setup/email-routing-addresses.mdx b/src/content/docs/email-routing/setup/email-routing-addresses.mdx index 999a654b71be7f..656fa72e7002e3 100644 --- a/src/content/docs/email-routing/setup/email-routing-addresses.mdx +++ b/src/content/docs/email-routing/setup/email-routing-addresses.mdx @@ -73,7 +73,7 @@ You can enable subaddressing at **Email** > **Email Routing** > **Settings**. Once enabled, you can use subaddressing with any of your custom addresses. For example, if you send an email to `user+detail@example.com` it will be captured by the `user@example.com` custom address. The `+detail` part is ignored by Email Routing, but it can be captured next in the processing chain in the logs, an [Email Worker](/email-routing/email-workers/) or an [Agent application](https://github.com/cloudflare/agents/tree/main/examples/email-agent). -If a custom address 'user+detail@example.com` already exists, it will take precedence over 'user@example.com'. This prevents breaking existing routing rules for users, and allows certain sub-addresses to be captured by a specific rule. +If a custom address `user+detail@example.com` already exists, it will take precedence over `user@example.com`. This prevents breaking existing routing rules for users, and allows certain sub-addresses to be captured by a specific rule. ## Destination addresses