Start Sarah feedback

Author: rkoron007

content/terraform/v1.13.x/docs/language/block/stack/deploy/store.mdx

@@ -128,11 +128,11 @@ The following examples demonstrate common use cases for `store` blocks.
 
 ### Define a store and access variables
 
-The following example defines a `varset` store named `api_keys` that accesses a variable set using its external ID:
+The following example defines a `varset` store named `api_keys` that accesses a variable set named `api_keys_default_project`:
 
 ```hcl
 store "varset" "api_keys" {
-  id       = "varset-abc123"
+  name       = "api_keys_default_project"
   category = "terraform"
 }
 

content/terraform/v1.13.x/docs/language/stacks/deploy/config.mdx

@@ -85,13 +85,13 @@ Use the following blocks to set up authentication for your deployment's provider
 - The `store` block lets you reference values in an HCP Terraform [variable set](/terraform/cloud-docs/workspaces/variables/managing-variables#variable-sets).
 - The `identity_token` block generates a JSON Web Token (JWT) for OIDC authentication.
 
-The `store` block lets you access a variable set from your deployment configuration. In the following example, the `api_keys` store fetches API keys from a variable set with the ID `varset-abc123456`:
+The `store` block lets you access a variable set from your deployment configuration. In the following example, the `api_keys` store fetches API keys from a variable set named `api_keys_default_project`:
 
 <CodeBlockConfig filename="deployments.tfdeploy.hcl">
 
 ```hcl
 store "varset" "api_keys" {
-  id       = "varset-abc123456"
+  name       = "api_keys_default_project"
   category = "terraform"
 }
 

content/terraform/v1.13.x/docs/language/stacks/index.mdx

@@ -13,7 +13,7 @@ Stacks replace Terraform's traditional root module structure with a new componen
 
 ## Background
 
-Stacks are an alternative way to organize your infrastructure and fundamentally differ from HCP Terraform workspaces. Stacks can live exist alongside workspaces in the same project, learn more about the differences and use cases of [Stacks and workspaces](/terraform/cloud-docs/use-cases).
+Stacks are an alternative way to organize your infrastructure and fundamentally differ from HCP Terraform workspaces. Stacks can exist alongside workspaces in the same project, learn more about the differences and use cases of [Stacks and workspaces](/terraform/cloud-docs/use-cases).
 
 Terraform Stacks enable you to split your Terraform configuration into components and then deploy and manage those components across multiple environments. You can manage the lifecycle of each deployment separately, roll out configuration changes across your deployments, and manage your Stack as a unit in HCP Terraform. When writing a Stack, you codify the entire behavior of your infrastructure lifecycle within version-controlled configuration files.