cleanup all the quotes

Author: ericallam

docs/idempotency.mdx

@@ -133,9 +133,9 @@ The `scope` option determines how your idempotency key is processed. When you pr
 | `"attempt"` | `key + parentRunId + attemptNumber` | Key is combined with the parent run ID and attempt number | Allow child tasks to re-run on each retry of the parent |
 | `"global"` | `key` | Key is used as-is, no context added | Ensure a task only runs once ever, regardless of parent |
 
-### `"run"` scope (default)
+### `run` scope (default)
 
-The `"run"` scope makes the idempotency key unique to the current parent task run. This is the default behavior for both raw strings and `idempotencyKeys.create()`.
+The `run` scope makes the idempotency key unique to the current parent task run. This is the default behavior for both raw strings and `idempotencyKeys.create()`.
 
 ```ts
 import { idempotencyKeys, task } from "@trigger.dev/sdk";
@@ -159,11 +159,11 @@ export const processOrder = task({
 });
 ```
 
-With `"run"` scope, if you trigger `processOrder` twice with different run IDs, both will send emails because the idempotency keys are different (they include different parent run IDs).
+With `run` scope, if you trigger `processOrder` twice with different run IDs, both will send emails because the idempotency keys are different (they include different parent run IDs).
 
-### `"attempt"` scope
+### `attempt` scope
 
-The `"attempt"` scope makes the idempotency key unique to each attempt of the parent task. Use this when you want child tasks to re-execute on each retry.
+The `attempt` scope makes the idempotency key unique to each attempt of the parent task. Use this when you want child tasks to re-execute on each retry.
 
 ```ts
 import { idempotencyKeys, task } from "@trigger.dev/sdk";
@@ -188,9 +188,9 @@ export const syncData = task({
 });
 ```
 
-### `"global"` scope
+### `global` scope
 
-The `"global"` scope makes the idempotency key truly global across all runs. Use this when you want to ensure a task only runs once ever (until the TTL expires), regardless of which parent task triggered it.
+The `global` scope makes the idempotency key truly global across all runs. Use this when you want to ensure a task only runs once ever (until the TTL expires), regardless of which parent task triggered it.
 
 ```ts
 import { idempotencyKeys, task } from "@trigger.dev/sdk";
@@ -213,7 +213,7 @@ export const onboardUser = task({
 ```
 
 <Note>
-Even with `"global"` scope, idempotency keys are still isolated to the specific task and environment. Using the same key to trigger *different* tasks will not deduplicate - both tasks will run. See [Environment and task scoping](#environment-and-task-scoping) for more details.
+Even with `global` scope, idempotency keys are still isolated to the specific task and environment. Using the same key to trigger *different* tasks will not deduplicate - both tasks will run. See [Environment and task scoping](#environment-and-task-scoping) for more details.
 </Note>
 
 ## Default behavior
@@ -222,7 +222,7 @@ Understanding the default behavior is important to avoid unexpected results:
 
 ### Passing a raw string
 
-When you pass a raw string directly to the `idempotencyKey` option, it is automatically processed with `"run"` scope:
+When you pass a raw string directly to the `idempotencyKey` option, it is automatically processed with `run` scope:
 
 ```ts
 // These two are equivalent when called inside a task:
@@ -231,7 +231,7 @@ await childTask.trigger(payload, { idempotencyKey: await idempotencyKeys.create(
 ```
 
 <Warning>
-**Breaking change in v4.3.1:** In v4.3.0 and earlier, raw strings defaulted to `"global"` scope. Starting in v4.3.1, raw strings now default to `"run"` scope. If you're upgrading and relied on the previous global behavior, you must now explicitly use `idempotencyKeys.create("key", { scope: "global" })`.
+**Breaking change in v4.3.1:** In v4.3.0 and earlier, raw strings defaulted to `global` scope. Starting in v4.3.1, raw strings now default to `run` scope. If you're upgrading and relied on the previous global behavior, you must now explicitly use `idempotencyKeys.create("key", { scope: "global" })`.
 </Warning>
 
 This means raw strings are scoped to the parent run by default. If you want global behavior, you must explicitly create the key with `scope: "global"`:
@@ -244,7 +244,7 @@ await childTask.trigger(payload, { idempotencyKey });
 
 ### Triggering from backend code
 
-When triggering tasks from your backend code (outside of a task), there is no parent run context. In this case, `"run"` and `"attempt"` scopes behave the same as `"global"` since there's no run ID or attempt number to inject:
+When triggering tasks from your backend code (outside of a task), there is no parent run context. In this case, `run` and `attempt` scopes behave the same as `global` since there's no run ID or attempt number to inject:
 
 ```ts
 // In your backend code (e.g., an API route)