diff --git a/messages/deploy.metadata.quick.md b/messages/deploy.metadata.quick.md
index c818c3ea..c490e789 100644
--- a/messages/deploy.metadata.quick.md
+++ b/messages/deploy.metadata.quick.md
@@ -10,6 +10,8 @@ Executing this quick deploy command takes less time than a standard deploy becau
 
 This command doesn't support source-tracking. The source you deploy overwrites the corresponding metadata in your org. This command doesn’t attempt to merge your source with the versions in your org.
 
+Note: Don't use this command on sandboxes; the command is intended to be used on production orgs.  By default, sandboxes don't run tests during a deploy. Use `sf project deploy start` instead.
+
 # examples
 
 - Run a quick deploy to your default org using a job ID:
diff --git a/messages/deploy.metadata.validate.md b/messages/deploy.metadata.validate.md
index af33017f..03560d79 100644
--- a/messages/deploy.metadata.validate.md
+++ b/messages/deploy.metadata.validate.md
@@ -12,6 +12,8 @@ This command doesn't support source-tracking. When you quick deploy with the res
 
 To validate the deployment of multiple metadata components, either set multiple --metadata <name> flags or a single --metadata flag with multiple names separated by spaces. Enclose names that contain spaces in one set of double quotes. The same syntax applies to --manifest and --source-dir.
 
+Note: Don't use this command on sandboxes; the command is intended to be used on production orgs. By default, sandboxes don't run tests during a deploy.  If you want to validate a deployment with tests on a sandbox, use "sf project deploy start --dry-run --test-level RunLocalTests" instead.
+
 # examples
 
 - NOTE: These examples focus on validating large deployments. See the help for "<%= config.bin %> project deploy start" for examples of deploying smaller sets of metadata which you can also use to validate.