Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: escape token (#46313)

Vaibhaved90d2aa50ed
diff --git a/apps/docs/content/guides/local-development/customizing-email-templates.mdx b/apps/docs/content/guides/local-development/customizing-email-templates.mdx
index 99698c89298..7316d957249 100644
--- a/apps/docs/content/guides/local-development/customizing-email-templates.mdx
+++ b/apps/docs/content/guides/local-development/customizing-email-templates.mdx
@@ -101,7 +101,7 @@ There are several authentication-related email templates which can be configured
### `auth.email.template.reauthentication`
-**Default subject**: "{{ .Token }} is your verification code"
+**Default subject**: "`{{ .Token }} is your verification code`"
**When sent**: When a user needs to re-authenticate for sensitive operations
**Purpose**: Ask users to verify their identity before a sensitive operation
**Content**: Contains a 6-digit OTP code for verification
diff --git a/apps/docs/content/guides/telemetry/client-side-tracing.mdx b/apps/docs/content/guides/telemetry/client-side-tracing.mdx
index b2fc7c54805..e2e8250c708 100644
--- a/apps/docs/content/guides/telemetry/client-side-tracing.mdx
+++ b/apps/docs/content/guides/telemetry/client-side-tracing.mdx
@@ -73,7 +73,7 @@ Once trace context is flowing through, the `trace_id` appears in:
- **API Gateway logs** — every request to PostgREST, Auth, Storage, and Realtime
- **Edge Function logs** — invocations and any structured logs emitted from within the function
-If you forward Supabase logs to a third-party backend via [Log Drains](/guides/telemetry/log-drains), you can join Supabase logs to your own client and server traces using the shared `trace_id`. This is especially useful for self-hosted setups where you already operate your own OpenTelemetry collector — Supabase logs become first-class citizens in your existing tracing UI.
+If you forward Supabase logs to a third-party backend via [Log Drains](/docs/guides/telemetry/log-drains), you can join Supabase logs to your own client and server traces using the shared `trace_id`. This is especially useful for self-hosted setups where you already operate your own OpenTelemetry collector — Supabase logs become first-class citizens in your existing tracing UI.
## Using a vendor tracing SDK