more

Author: waleedlatif1

apps/docs/content/docs/en/credentials/index.mdx

@@ -37,7 +37,7 @@ Keys must use only letters, numbers, and underscores — no spaces or special ch
 
 ### Bulk Import
 
-You can populate multiple secrets at once by pasting `.env`-style content directly into any value field. The parser supports standard `KEY=VALUE` pairs, quoted values, comments (`#`), and blank lines.
+You can populate multiple secrets at once by pasting `.env`-style content into any key or value field. The parser supports standard `KEY=VALUE` pairs, `export KEY=VALUE`, quoted values, and inline comments.
 
 ### Editing and Deleting
 
@@ -116,6 +116,6 @@ When a workflow runs, secrets resolve in this order:
   { question: "Are my secrets encrypted at rest?", answer: "Yes. Secret values are encrypted before being stored in the database using server-side encryption, so raw values are never persisted in plaintext. They are also never exposed in the workflow editor, logs, or API responses." },
   { question: "What happens if both a workspace secret and a personal secret have the same key name?", answer: "The workspace secret takes precedence. During execution, the resolver checks workspace secrets first and uses personal secrets only as a fallback. This ensures production workflows use the shared, team-managed value." },
   { question: "Who determines which personal secret is used for automated runs?", answer: "For manual runs, the personal secrets of the user who clicked Run are used as fallback. For automated runs triggered by API, webhook, or schedule, the personal secrets of the workflow owner are used instead." },
-  { question: "Can I import secrets from a .env file?", answer: "Yes. Paste .env-style content (KEY=VALUE format) directly into a value field and the secrets will be auto-populated. The parser supports quoted values, comments (lines starting with #), and blank lines." },
+  { question: "Can I import secrets from a .env file?", answer: "Yes. Paste .env-style content (KEY=VALUE format) into any key or value field and the secrets will be auto-populated. The parser supports export KEY=VALUE, quoted values, and inline comments." },
   { question: "What happens if I delete a secret that is used in a workflow?", answer: "The workflow will fail at any block that references the deleted secret during execution because the value cannot be resolved. Update any references before deleting a secret." },
 ]} />

apps/docs/content/docs/en/integrations/index.mdx

@@ -60,7 +60,7 @@ Blocks that require authentication (e.g. Gmail, Slack, Google Sheets) display a
   height={350}
 />
 
-You can also connect additional accounts directly from the block by selecting **Connect another account** at the bottom of the dropdown.
+You can also connect additional accounts directly from the block by selecting **Connect another [service] account** at the bottom of the dropdown.
 
 <Callout type="info">
 If a block requires an integration and none is selected, the workflow will fail at that step.