From 7b77a44e6e90bd4479681fca2e09dcf865a2f41a Mon Sep 17 00:00:00 2001
From: Rose M Koron <32436232+rkoron007@users.noreply.github.com>
Date: Tue, 25 Feb 2025 02:21:29 -0800
Subject: [PATCH] add the feature name (#36573)

---
 website/docs/language/stacks/deploy/pass-data.mdx | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/website/docs/language/stacks/deploy/pass-data.mdx b/website/docs/language/stacks/deploy/pass-data.mdx
index f3f1fb146b..1f8d6e2921 100644
--- a/website/docs/language/stacks/deploy/pass-data.mdx
+++ b/website/docs/language/stacks/deploy/pass-data.mdx
@@ -1,12 +1,11 @@
 ---
 page_title: Pass data from one Stack to another
-description: Learn how to pass data from one Stack to another using `publish_output` blocks to output data from one Stack, and `upstream_input` blocks to input that data into another Stack.
+description: Learn how to link Stacks together to pass data from one Stack to another using `publish_output` blocks to export data and `upstream_input` blocks to consume that data. 
 ---
 
 # Pass data from one Stack to another
 
-If you have multiple Stacks that do not share a provisioning lifecycle, you can export data from one Stack for another Stack to consume. If the output value of a Stack changes after a run, HCP Terraform automatically triggers runs for any Stacks that depend on those outputs.
-
+If you have multiple Stacks that do not share a provisioning lifecycle, you can link Stacks together to export data from one Stack for another to consume. If the output value of a Stack changes after a run, HCP Terraform automatically triggers runs for any Stacks that depend on those outputs.
 
 ## Background