From a001abdcdb6a57ea046d5df02e52d004f61e8802 Mon Sep 17 00:00:00 2001
From: Derek Strickland <1111455+DerekStrickland@users.noreply.github.com>
Date: Thu, 22 Sep 2022 14:56:21 -0400
Subject: [PATCH] Update multiregion.mdx

---
 .../content/docs/job-specification/multiregion.mdx    | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/website/content/docs/job-specification/multiregion.mdx b/website/content/docs/job-specification/multiregion.mdx
index a34697c36..b2dbb352d 100644
--- a/website/content/docs/job-specification/multiregion.mdx
+++ b/website/content/docs/job-specification/multiregion.mdx
@@ -69,12 +69,11 @@ final region will unblock the regions to mark them as `successful`.
 
 ## Multiregion Parameterized Job Dispatch
 
-While a [parameterized job] can be deployed to multiple [federated regions]
-like any other job, a parameterized job operates much like a function
-definition that takes variable input. Operator's are expected to invoke
-the job by invoking [`job dispatch`] from the CLI or the [HTTP API].
-Job dispatching is region specific. Operators are required to dispatch
-the job for each target region and provide the appropriate dispatch options
+Job dispatching is region specific. While a [parameterized job] can be 
+deployed to multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`] 
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
 for that region.
 
 ## `multiregion` Parameters