From 12431735814ed63f8c3e6d3a929adc32c4290bb3 Mon Sep 17 00:00:00 2001
From: Cristian Dominguez <6853656+cristiand391@users.noreply.github.com>
Date: Mon, 7 Jul 2025 09:42:22 -0300
Subject: [PATCH 1/2] chore: update data.export.resume.md

---
 messages/data.export.resume.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/messages/data.export.resume.md b/messages/data.export.resume.md
index 7d432a72..fe84f7df 100644
--- a/messages/data.export.resume.md
+++ b/messages/data.export.resume.md
@@ -6,6 +6,8 @@ Resume a bulk export job that you previously started. Uses Bulk API 2.0.
 
 When the original "data export bulk" command either times out or is run with the --async flag, it displays a job ID. To see the status and get the results of the bulk export, run this command by either passing it the job ID or using the --use-most-recent flag to specify the most recent bulk export job.
 
+Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started based on the cached data by "data export bulk".
+
 # flags.job-id.summary
 
 Job ID of the bulk export.
@@ -16,10 +18,10 @@ Use the job ID of the bulk export job that was most recently run.
 
 # examples
 
-- Resume a bulk export job run on your default org by specifying a job ID:
+- Resume a bulk export job run by specifying a job ID:
 
   sf <%= command.id %> --job-id 750xx000000005sAAA
 
-- Resume the most recently-run bulk export job for an org with alias my-scratch:
+- Resume the most recently-run bulk export job:
 
-  sf data export resume --use-most-recent --target-org my-scratch
+  sf data export resume --use-most-recent

From 456d70f581c0331299bdb67b9ac85ba43da31ec0 Mon Sep 17 00:00:00 2001
From: Cristian Dominguez <6853656+cristiand391@users.noreply.github.com>
Date: Mon, 7 Jul 2025 09:49:05 -0300
Subject: [PATCH 2/2] Update data.update.resume.md

---
 messages/data.update.resume.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/messages/data.update.resume.md b/messages/data.update.resume.md
index c3e7d3a6..3e446106 100644
--- a/messages/data.update.resume.md
+++ b/messages/data.update.resume.md
@@ -6,15 +6,17 @@ Resume a bulk update job that you previously started. Uses Bulk API 2.0.
 
 When the original "sf data update bulk" command either times out or is run with the --async flag, it displays a job ID. To see the status and get the results of the bulk update, run this command by either passing it the job ID or using the --use-most-recent flag to specify the most recent bulk update job.
 
+Using either `--job-id` or `--use-most-recent` will properly resolve to the correct org where the bulk job was started based on the cached data by "data update bulk".
+
 # examples
 
-- Resume a bulk update job of your default org using a job ID:
+- Resume a bulk update job using a job ID:
 
   <%= config.bin %> <%= command.id %> --job-id 750xx000000005sAAA
 
-- Resume the most recently run bulk update job for an org with alias "my-scratch":
+- Resume the most recently run bulk update job:
 
-  <%= config.bin %> <%= command.id %> --use-most-recent --target-org my-scratch
+  <%= config.bin %> <%= command.id %> --use-most-recent
 
 # flags.use-most-recent.summary