link stacks references to m-a refs

Author: trujillo-adam

content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/component.mdx

@@ -128,6 +128,8 @@ component "storage" {
 
 The keys in the `providers` map must match the provider names that the source module expects, and the values must reference providers declared in your component configuration. Learn more about [Declaring providers in Stacks](/terraform/language/stacks/component/declare-providers).
 
+`providers` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`providers` reference](/terraform/language/meta-arguments/providers) for details about how the argument works.
+
 #### Summary
 
 - Data type: Map
@@ -178,10 +180,7 @@ component "app_server" {
 
 You do not need to include the dependant component’s outputs in the `depends_on` list because Terraform automatically recognizes those dependencies.
 
-#### Summary
-
-- Data type: List of references
-- Default: None
+`depends_on` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`depends_on` reference](/terraform/language/meta-arguments/depends_on) for details about how the argument works.
 
 ### `for_each`
 
@@ -217,10 +216,7 @@ component "<LABEL>" {
 
 When you use `for_each`, Terraform creates one component instance for each item in the collection. You can reference individual instances using `component.<LABEL>[<KEY>]` syntax.
 
-#### Summary
-
-- Data type: Map or Set
-- Default: None
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
 
 ## Examples
 

content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/provider.mdx

@@ -111,10 +111,7 @@ provider "<NAME>" "<ALIAS>" {
 
 When you use `for_each`, you can reference individual provider instances using `provider.<PROVIDER_NAME>.<ALIAS>[<KEY>]` syntax in your `component` blocks.
 
-#### Summary
-
-- Data type: Map or Set
-- Default: None
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
 
 ## Examples
 

content/terraform/v1.13.x/docs/language/block/stack/tfcomponent/removed.mdx

@@ -104,7 +104,7 @@ removed {
 
 ### `providers`
 
-The `providers` argument maps provider names to the providers that the component you want to remove uses. HCP Terraform needs these provider configurations to properly remove the component's resources.
+The `providers` argument is required. It maps provider names to the providers that the component you want to remove uses. HCP Terraform needs these provider configurations to properly remove the component's resources.
 
 ```hcl
 removed {
@@ -119,11 +119,7 @@ removed {
 
 The provider mapping must include every provider that the component's module requires for resource destruction.
 
-#### Summary
-
-- Data type: Map
-- Default: None
-- Required: Yes
+`providers` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`providers` reference](/terraform/language/meta-arguments/providers) for details about how the argument works.
 
 ### `for_each`
 
@@ -161,6 +157,8 @@ removed {
 
 The `for_each` meta-argument is useful when you want to remove components from specific regions or environments.
 
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
+
 #### Summary
 
 - Data type: Map or Set

content/terraform/v1.14.x (beta)/docs/language/block/stack/tfcomponent/component.mdx

@@ -128,11 +128,7 @@ component "storage" {
 
 The keys in the `providers` map must match the provider names that the source module expects, and the values must reference providers declared in your component configuration. Learn more about [Declaring providers in Stacks](/terraform/language/stacks/component/declare-providers).
 
-#### Summary
-
-- Data type: Map
-- Default: None
-- Required: Yes
+`providers` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`providers` reference](/terraform/language/meta-arguments/providers) for details about how the argument works.
 
 
 ### `inputs`
@@ -175,13 +171,9 @@ component "app_server" {
   # ...
 }
 ```
-
 You do not need to include the dependant component’s outputs in the `depends_on` list because Terraform automatically recognizes those dependencies.
 
-#### Summary
-
-- Data type: List of references
-- Default: None
+`depends_on` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`depends_on` reference](/terraform/language/meta-arguments/depends_on) for details about how the argument works.
 
 ### `for_each`
 
@@ -217,10 +209,8 @@ component "<LABEL>" {
 
 When you use `for_each`, Terraform creates one component instance for each item in the collection. You can reference individual instances using `component.<LABEL>[<KEY>]` syntax.
 
-#### Summary
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
 
-- Data type: Map or Set
-- Default: None
 
 ## Examples
 

content/terraform/v1.14.x (beta)/docs/language/block/stack/tfcomponent/provider.mdx

@@ -111,6 +111,8 @@ provider "<NAME>" "<ALIAS>" {
 
 When you use `for_each`, you can reference individual provider instances using `provider.<PROVIDER_NAME>.<ALIAS>[<KEY>]` syntax in your `component` blocks.
 
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
+
 #### Summary
 
 - Data type: Map or Set

content/terraform/v1.14.x (beta)/docs/language/block/stack/tfcomponent/removed.mdx

@@ -104,7 +104,7 @@ removed {
 
 ### `providers`
 
-The `providers` argument maps provider names to the providers that the component you want to remove uses. HCP Terraform needs these provider configurations to properly remove the component's resources.
+The `providers` argument is required. It maps provider names to the providers that the component you want to remove uses. HCP Terraform needs these provider configurations to properly remove the component's resources.
 
 ```hcl
 removed {
@@ -119,11 +119,7 @@ removed {
 
 The provider mapping must include every provider that the component's module requires for resource destruction.
 
-#### Summary
-
-- Data type: Map
-- Default: None
-- Required: Yes
+`providers` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`providers` reference](/terraform/language/meta-arguments/providers) for details about how the argument works.
 
 ### `for_each`
 
@@ -158,8 +154,9 @@ removed {
 
 </Tabs>
 
+You can use `for_each` to remove components from specific regions or environments.
 
-The `for_each` meta-argument is useful when you want to remove components from specific regions or environments.
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates and manages resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
 
 #### Summary