fix: add suggestions

Author: jainpawan21

content/docs/platform/workflow/build-a-workflow.mdx

@@ -17,7 +17,7 @@ icon: 'Wrench'
     - Description of the workflow (optional)
     - Enable [translations](/platform/workflow/translations) (optional)
 
-    Once you've filled in the required fields, click on **Create Workflow**.
+    Once you've filled in the required fields, click **Create Workflow**.
 
   </Step>
   <Step title="Add a workflow step">

content/docs/platform/workflow/translations.mdx

@@ -9,54 +9,55 @@ icon: 'Languages'
 Novu supports multi-language translations for workflows, allowing your notifications to dynamically adapt to your users' preferred language. This documentation covers everything you need to know to enable, configure, and manage translations for your workflows.
 
 <Callout type="info">
-  Translations feature is currently in `beta` and is available for `Team` and `Enterprise` plans.
+  The translations feature is currently in `beta` and is available for `Team` and `Enterprise` plans.
 </Callout>
 
-## Introduction
-
-Workflow translation allows each notification workflow (e.g., onboarding, password reset, OTP, etc.) to support multiple locales. When a subscriber (user) receives a notification, Novu selects the appropriate translation based on the subscriber’s locale.
+Workflow translations allow each notification workflow, such as onboarding, password reset, and one time password (OTP), to support multiple locales. When a subscriber receives a notification, Novu selects the appropriate translation based on the subscriber's locale.
 
 This feature helps teams:
 
 - Reach users in their native language.
 - Customize language per workflow or layout.
 - Reduce friction in communication across geographies.
 
-Translations can be managed on the [translation page](https://dashboard.novu.co/translations) on Novu dashboard. Select the default language and add the target languages you wish to support.
+You can manage translations on the[translation page](https://dashboard.novu.co/translations) on Novu dashboard. Select the default language and add the target languages that you wish to support.
 
 ![Translation page](/images/platform/workflow/translations/translations-page.png)
 
 ## Enabling translations
 
-1. **While creating a new workflow**
+To use translations for a workflow, you need to enable them on the workflow level.
+
+### While creating a new workflow
 
-- Check the **Enable Translations** toggle.
-- Set the default locale (e.g., `en_US`).
-- Add target locales you wish to support (e.g., `fr_FR`, `es_ES`, `ja_JP`, etc.).
+- Turn on the **Enable Translations** toggle
+- Set the default locale, such as `en_US` or `en_GB`
+- Add the target locales you wish to support, such as `fr_FR`, `es_ES`, `ja_JP`
 
-2. **While editing an existing workflow**
+### While editing an existing workflow
 
-- Open an existing workflow.
-- Click the **Enable Translations** option in the right panel
-- Enable the toggle if not already enabled.
+- Open an existing workflow
+- Turn on the **Enable Translations** toggle
+- You don't need to take any action if the toggle is already on
 
-Default and targeted locales can be configured on the translation page.
+You can configure the default and targeted locales on the [translation page](https://dashboard.novu.co/translations).
 
 ![Translation locale](/images/platform/workflow/translations/translations-default-and-target-locale.gif)
 
-## Translation Groups
+## Translation groups
 A translation group contains all language variants for a workflow identified by a unique workflow ID.
 
 You can:
 
-- Search for groups on the **Translations** page.
-- View status per locale ('Outdated' or 'Up to date').
-- Import or export translations for a specific locale (e.g., `en_US`).
-- Import or export translations for all workflows where translations are enabled.
+- Search for groups on the translations page
+- View status per locale ('Outdated' or 'Up to date')
+- Import or export translations for a specific locale, such as `en_US
+- Import or export translations for all workflows where translations are enabled
 
 ## Translation JSON format
 
-Each locale supports JSON-based translation files. For example, `en_US.json` file contains the default translations for the workflow. Translation JSON files can be updated using the JSON editor on the translation page.
+Each locale supports JSON-based translation files. For example, the `en_US.json` file contains the default translations for the workflow. You can update the translation JSON files using the JSON editor on the translation page.
+
 ```json
 {
   "in-app": {
@@ -70,19 +71,19 @@ Each locale supports JSON-based translation files. For example, `en_US.json` fil
 }
 ```
 
-You can export and re-upload these JSON files when translation updates are needed or use the JSON editor on the translation page to update the translations.
+You can update translations by editing the JSON files in the editor on the translations page or by exporting and re-uploading them.
 
 ![Translation JSON format](/images/platform/workflow/translations/translations_locale_content_edit.gif)
 
-### Exporting and importing translations
+## Exporting and importing translations
 
-#### Export
+### Export
 
 - Navigate to the Translations section.
 - Click **Export en_US.json** to download the latest default file.
 - Use this as a base for other translations.
 
-#### Import
+### Import
 
 - Click **Import locale(s)**.
 - Upload JSON files (e.g., fr_FR.json, es_ES.json).