Update the CDK deploy method description.

KristinaPeterson · KristinaPeterson · commit 3658f084dc08 · 2025-07-29T13:42:55.000-07:00
diff --git a/build b/build
@@ -1 +1 @@
-/workplace/pgasca/AWSCDKDocs_1/build/AWSCDKDocs/AWSCDKDocs-3.0/AL2_x86_64/DEV.STD.PTHREAD/build
+/Users/kripet/Workplace/AWSCDKDocs/build/AWSCDKDocs/AWSCDKDocs-3.0/AL2_x86_64/DEV.STD.PTHREAD/build
diff --git a/v2/guide/ref-cli-cmd-deploy.adoc b/v2/guide/ref-cli-cmd-deploy.adoc
@@ -187,7 +187,7 @@ Configure the method to perform a deployment.
 +
 --
 * `change-set` – Default method. The CDK CLI creates a CloudFormation change set with the changes that will be deployed, then performs deployment.
-* `direct` – Do not create a change set. Instead, apply the change immediately. This is typically faster than creating a change set, but you lose progress information.
+* `direct` – Do not create a change set. Instead, apply the change immediately. This is typically faster than creating a change set, but you lose deployment progress details in the CLI output.
 * `prepare-change-set` – Create change set but don't perform deployment. This is useful if you have external tools that will inspect the change set or if you have an approval process for change sets.
 --
 +

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-/workplace/pgasca/AWSCDKDocs_1/build/AWSCDKDocs/AWSCDKDocs-3.0/AL2_x86_64/DEV.STD.PTHREAD/build`
	`1`	`+/Users/kripet/Workplace/AWSCDKDocs/build/AWSCDKDocs/AWSCDKDocs-3.0/AL2_x86_64/DEV.STD.PTHREAD/build`
Original file line number	Diff line number	Diff line change
`@@ -187,7 +187,7 @@ Configure the method to perform a deployment.`
`187`	`187`	`+`
`188`	`188`	`--`
`189`	`189`	* `change-set` – Default method. The CDK CLI creates a CloudFormation change set with the changes that will be deployed, then performs deployment.
`190`		-* `direct` – Do not create a change set. Instead, apply the change immediately. This is typically faster than creating a change set, but you lose progress information.
	`190`	+* `direct` – Do not create a change set. Instead, apply the change immediately. This is typically faster than creating a change set, but you lose deployment progress details in the CLI output.
`191`	`191`	* `prepare-change-set` – Create change set but don't perform deployment. This is useful if you have external tools that will inspect the change set or if you have an approval process for change sets.
`192`	`192`	`--`
`193`	`193`	`+`