Automatic import step 7 update

solutions/security/get-started/automatic-migration.md

@@ -56,14 +56,17 @@ You can ingest your data before migrating your rules, or migrate your rules firs
 
 6. After you upload your Splunk rules, Automatic Migration will detect whether they use any Splunk macros or lookups. If so, follow the instructions which appear to export and upload them. Alternatively, you can complete this step later — however, until you upload them, some of your migrated rules will have a `partially translated` status. If you upload them now, you don't have to wait on the page for them to be processed — a notification will appear when processing is complete.
 
-7. Click **Translate** to start the rule translation process. You don't need to stay on this page. A notification will appear when the process is complete. A name for this migration is automatically created. If necessary, use the **More actions** ({icon}`boxes_vertical`) button to rename or pause the migration. 
+7. Click **Translate** to start the rule translation process. A name for this migration is automatically created, and you can track its progress on this page. The **More actions** ({icon}`boxes_vertical`) button lets you rename or pause the migration. 
 
    ::::{image} /solutions/images/security-siem-migration-rule-status-more-actions.png
    :alt: The rule migration status view
    :width: 850px
    :screenshot:
    ::::
 
+   You don't need to stay on this page. A notification will appear when the migration is complete.
+
+
 8. Use the **Add SIEM data with Integrations** section to set up data ingestion from third-party sources. If at least one rule migration has completed, the **Recommended** tab shows integrations that provide the data needed by your translated rules. These include both Elastic-managed integrations and any applicable custom creations you made using [automatic import](/solutions/security/get-started/automatic-import.md).
 
    ::::{image} /solutions/images/security-siem-migration-integrations-panel.png