Almost done

Author: rkoron007

content/terraform/v1.13.x/docs/language/stacks/component/declare-providers.mdx

@@ -77,7 +77,7 @@ component "s3" {
 
 After configuring your provider, you can use the Terraform CLI to generate a provider lock file:
 
-```shell
+```shell-session
 $ terraform stacks init
 ```
 
@@ -155,7 +155,7 @@ A Stack cannot run without a lock file for its providers. After defining your pr
 $ terraform stacks init
 ```
 
-The `terraform stacks init` command uses the `required_providers` block from your configuration to download the listed providers and compute the provider lock hashes. If you update your Stack’s providers, run `terraform stacks init -upgrade` command to update your Stack’s lock file locally. For more details, refer to the [`terraform stacks` commands](/terraform/cli/commands/stacks).
+The `terraform stacks init` command uses the `required_providers` block from your configuration to download the listed providers and compute the provider lock hashes. If you update your Stack’s providers, run the `terraform stacks init -upgrade` command to update your Stack’s lock file locally. For more details, refer to the [`terraform stacks` commands](/terraform/cli/commands/stacks).
 
 ## Next steps
 

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

@@ -19,6 +19,8 @@ Terraform Stacks enable you to split your Terraform configuration into component
 
 Each deployment in a Stack represents a group of components that work together, such as a development and production environment. The configuration for each Stack is identical across deployments, and you can customize each deployment with input variables. You can then use HCP Terraform to roll out changes to each of your deployments and keep track of the changes across your environments.
 
+If you participated in the Stacks beta, you need to update your configurations to be compatible with the GA release. For details, refer to [Update for general availability](/terraform/language/stacks/update-GA).
+
 ## Workflow
 
 Begin creating Stack by making a component configuration file, ending in `tfcomponent.hcl`, and filling it with `component` blocks. Each `component` block includes a Terraform module as its source, and you can configure each `component` using the `inputs` argument. All of your Stack components share a lifecycle, which you repeatedly deploy together using HCP Terraform.

content/terraform/v1.13.x/docs/language/stacks/update-GA.mdx

@@ -1,10 +1,10 @@
 ---
-page_title: Stack configuration files for Terraform
+page_title: Update from beta to general availability for Terraform Stacks
 description: |-
   Learn about the new general release of Stacks and how to migrate from the beta to the general release.
 ---
 
-# Move from Stacks beta to general availability
+# Update from beta to general availability
 
 The GA release of Stacks introduces several new features and improvements.