Fix settings and typos in docs

docs/cli/automation/github-actions/deployment-workflow.md

@@ -1,7 +1,6 @@
 ---
 title: How to use Terramate to automate and orchestrate Terraform Deployments in GitHub Actions
-description: Learn how to use Terramate to configure custom GitOps workflows to automate and orchestrate Terraform and OpenTofu Deploymnets in GitHub Actions.
-outline: [2, 3]
+description: Learn how to use Terramate to configure custom GitOps workflows to automate and orchestrate Terraform and OpenTofu Deployments in GitHub Actions.
 ---
 
 # Run a Deployment in GitHub Actions
@@ -17,6 +16,8 @@ This drift check will be used to judge the health of the deployment even if the
 
 ## Deployment Blueprints
 
+Create the following GitHub Actions configuration at `.github/workflows/deploy.yml`
+
 ::: code-group
 
 ```yml [ AWS + Terramate Cloud ]

docs/cli/automation/github-actions/drift-check-workflow.md

@@ -1,7 +1,6 @@
 ---
 title: How to use Terramate to automate and orchestrate Terraform Drift Checks in GitHub Actions
 description: Learn how to use Terramate to configure custom GitOps workflows to automate and orchestrate Terraform and OpenTofu Drift Checks in GitHub Actions.
-outline: [2, 3]
 ---
 
 # Run a Drfit Check in GitHub Actions
@@ -12,20 +11,22 @@ Search for `CHANGEME` to adjust needed credentials details for AWS and Google Cl
 
 Drift Checks require action and protocolling the results, so Terramate Cloud support is required for those workflows at the moment.
 
-The following workflows run every day at 2am.
+The following workflows run every day at 2 am.
 
 ## Terramate Cloud support
 
-When synchronizing drift checks to Terramate Cloud, the following fetures will support the team with handling drifts:
+When synchronizing drift checks to Terramate Cloud, the following features will support the team with handling drifts:
 
-- Get notified on new drifts via Slacks notifications.
+- Get notified on new drifts via Slack notifications.
 - Highlight and identify drifted stacks in the Stacks List and Dashboard
 - See drift details without requiring your team to have elevated access to read the Terraform state or have access to read the cloud resources.
 - Identify the time when a drift happened and how long a stack stayed in a drifted state.
 - Create automation to reconcile a drift without human interaction using `--cloud-status` filter in Terramate CLI.
 
 ## Deployment Blueprints
 
+Create the following GitHub Actions configuration at `.github/workflows/drift.yml`
+
 ::: code-group
 
 ```yml [ AWS + Terramate Cloud ]
@@ -148,5 +149,4 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ github.token }}
 ```
-
 :::

docs/cli/automation/github-actions/preview-workflow.md

@@ -1,7 +1,6 @@
 ---
 title: How to use Terramate to automate and orchestrate Terraform Previews in GitHub Actions
 description: Learn how to use Terramate to configure custom GitOps workflows to automate and orchestrate Terraform and OpenTofu Previews in GitHub Actions.
-outline: [2, 3]
 ---
 
 # Run a Preview in GitHub Actions
@@ -14,7 +13,7 @@ Search for `CHANGEME` to adjust needed credentials details for AWS and Google Cl
 
 When synchronizing previews to Terramate Cloud previews will be synchronized with a detailed status and can be reviewed on a stack level.
 
-The following actions also post back previews as GitHub comments. This will soon be taken care of by Terramate Cloud to fix some short-commings:
+The following actions also post back previews as GitHub comments. This will soon be taken care of by Terramate Cloud to fix some short-comings:
 
 - GitHub limits the size of a comment, so when creating large plans of many stacks, previews are truncated.
 - Rate limits in GitHub sometimes prevent comments from being created.
@@ -29,6 +28,8 @@ Terramate Cloud will provide:
 
 ## Deployment Blueprints
 
+Create the following GitHub Actions configuration at `.github/workflows/preview.yml`
+
 ::: code-group
 
 ````yml [ AWS + Terramate Cloud ]

docs/cli/automation/index.md

@@ -1,7 +1,7 @@
 ---
 # title: Running Terramate in Automation
-title: GitOps for infrastructure with Terramate and Terraform / OpenTofu
-description: Learn how to automate and orchestrate Terraform and OpenTofu with Terramate and GitOps workflows in GitHub Actions, GitLab CI/CD, BitBucket Pipelines and others.
+title: GitOps for infrastructure with Terraform
+description: Learn how to automate and orchestrate Terraform and OpenTofu with Terramate and GitOps workflows in GitHub Actions, GitLab CI/CD, BitBucket Pipelines and any other CI/CD.
 ---
 
 # Running Terramate in Automation
@@ -12,38 +12,14 @@ BitBucket Pipelines, Azure DevOps, and others for cost-effective Terraform and O
 This enables you to automate the orchestration of your IaC stacks using GitOps workflows and comes with the following
 benefits:
 
-✨ **GitOps for infrastructure**
-
-Move fast using a declarative, single source of truth with an auditable history and change management controls.
-Be more productive and reliable. Provide a better Developer Experience by building on top of tools your team already knows.
-
-✨ **Run in any existing CI/CD**
-
-Terramate helps you to achieve the best automation and collaboration experience when working with Terraform and OpenTofu
-in any CI/CD. This means you can reuse existing infrastructure, collaboration features, audit logs and security.
-
-✨ **Design your workflows without limitations**
-
-Configure limitless workflows. Whether you prefer merge-and-apply or apply-and-merge; we got you covered.
-
-✨ **Integrate any existing tooling**
-
-Integrate third-party toolings such as *Infracost*, *Trivy*, *terrascan*, *checkov*, *OPA*, *Kyverno*, *Sentinel* and
-others into your workflows. Terramate allows you to integrate and run any tool.
-
-✨ **Reduce execution time of existing pipelines**
-
-Parallel runs and change detection allows orchestrating stacks containing changes only and running those in parallel.
-
-✨ **No extra budget needed**
-
-Enable cost-effective automation for IaC by integrating with your existing CI/CD instead of paying
+- **GitOps for infrastructure**: Move fast using a declarative, single source of truth with an auditable history and change management controls. Be more productive and reliable. Provide a better Developer Experience by building on top of tools your team already knows.
+- **Run in any existing CI/CD**: Terramate helps you to achieve the best automation and collaboration experience when working with Terraform and OpenTofu in any CI/CD. This means you can reuse existing infrastructure, collaboration features, audit logs and security.
+- **Design your workflows without limitations**: Configure limitless workflows. Whether you prefer merge-and-apply or apply-and-merge; we got you covered.
+- **Integrate any existing tooling**: Integrate third-party toolings such as *Infracost*, *Trivy*, *terrascan*, *checkov*, *OPA*, *Kyverno*, *Sentinel* and others into your workflows. Terramate allows you to integrate and run any tool.
+- **Reduce execution time of existing pipelines**: Parallel runs and change detection allows orchestrating stacks containing changes only and running those in parallel.
+- **No extra budget needed**: Enable cost-effective automation for IaC by integrating with your existing CI/CD instead of paying
 for an additional and expensive platform.
-
-✨ **Maximum Security**
-
-Using your existing CI/CD limits the number of privileged platforms in your organization. There's no need to provide an
-additional platform with access to your cloud accounts.
+- **Maximum Security**: Using your existing CI/CD limits the number of privileged platforms in your organization. There's no need to provide an additional platform with access to your cloud accounts.
 
 ## Guides
 

docs/cloud/dashboard/index.md

@@ -1,3 +1,8 @@
+---
+title: Dashboard in Terramate Cloud
+description: Learn how the dashboard in Terramate Cloud helps to keep an overview of the health of all stacks. In addition, it shows historical data about deployments.
+---
+
 # Dashboard
 
 The dashboard helps to keep an overview of the health of all stacks. In addition, it shows historical data about deployments.
@@ -6,7 +11,7 @@ The dashboard helps to keep an overview of the health of all stacks. In addition
 
 ## Health Donut
 
-The Health Donut either shows the amount of healthy stacks in case no stacks are unhealthy or the details about how many
+The Health Donut either shows the number of healthy stacks in case no stacks are unhealthy or the details about how many
 stacks are in a `failed` state and how many stacks are in a `drifted` state.
 
 ## Deployment Graph
@@ -16,7 +21,7 @@ stacks `failed` to deploy or succeeded.
 
 ## Last Deployments
 
-To have a real time activity overview of deployments that were running or are currently running, the list of the last
+To have a real-time activity overview of deployments that were running or are currently running, the list of the last
 deployments shows details about deployment runs.
 
 ::: tip

docs/cloud/deployments/synchronization-from-cli.md

@@ -28,7 +28,7 @@ information to Terramate Cloud.
 - `--cloud-sync-deployment` Synchronizes the deployment status and logs to Terramate Cloud
 - `--cloud-sync-terraform-plan=FILE` A Terraform integration that allows synchronization of details about the changed, added or deleted Terraform Resources that were planned to be applied in the deployment
 
-The full command line to run an auto approved apply based on an existing plan file in changed stacks only looks like the following:
+The full command line to run an auto-approved apply based on an existing plan file in changed stacks only looks like the following:
 
 ```bash
 terramate run \

docs/cloud/drifts/notifications.md

@@ -1,6 +1,6 @@
 ---
 title: Drift Notifications
-description: Learn how to get notified about new drifts that Terramate Cloud detects in stacks.
+description: Learn how to configure Slack notifications for drift detection in Terramate Cloud.
 ---
 
 # Drift Notifications
@@ -18,6 +18,6 @@ The notification will contain detailed information about the drifted stack and l
 
 ## Initial Drift Run
 
-When on-boarding to Terramate Cloud it is recommended to run a drift run before setting up the notifications when the initial run is expected to detect a lot of drifted stacks.
+When onboarding to Terramate Cloud it is recommended to run a drift run before setting up the notifications when the initial run is expected to detect a lot of drifted stacks.
 
 After the initial drift check run, the Slack Webhook can be set up and only new drifts will notify the channel.

docs/cloud/drifts/synchronization-in-automation.md

@@ -26,5 +26,5 @@ To gather metadata from GitHub about the pull request associated with the previe
 - Use OpenID Connect (OIDC) to authenticate to your Cloud Provider to use short-lived credentials - Terramate CLI uses OIDC by default.
 - Ensure that all drift checks run on all stacks even if some errors are detected using the `--continue-on-error` command line option
 - Run a Drift Check right after the deployment and synchronize the result to Terramate Cloud to get an immediate health check and ensure the deployment is stable.
-- Run a Drift Check at least every 24h to get a detailed history about when drifts were introduced.
+- Run a Drift Check at least every 24 hours to get a detailed history of newly detected drift.
 - Set up notification to get informed about newly detected drifts in stacks

docs/cloud/drifts/synchronization-with-scripts.md

@@ -20,7 +20,7 @@ To gather metadata from GitHub about the commit associated with the drift check,
 
 The following options are available in Terramate Scripts and mirror the CLI options with the name:
 
-- Set `cloud_sync_drift_status = true` to let Terramate CLI know about the command that is doing the actual drift check and returns a detailed exit status to define a successful run that has changes or has no changed detected.
+- Set `cloud_sync_drift_status = true` to let Terramate CLI know about the command that is doing the actual drift check and returns a detailed exit status to define a successful run that has changes or has no changes detected.
 - Set `cloud_sync_terraform_plan_file` to the name of the terraform plan to synchronize the deployment details.
 
 ## Terramate Script Config

docs/cloud/organization/user-management.md

@@ -1,3 +1,8 @@
+---
+title: User Management in Terramate Cloud
+description: Learn how to manage users of an organization in Terramate Cloud.
+---
+
 # User Management
 
 To manage teammates, an `admin` can choose from the following actions, while a normal `member` can only see the list of teammates or leave an organization.
@@ -44,7 +49,7 @@ Every teammate can decide to deactivate themselves to leave the organization.
 
 As an `admin` you can promote other teammates by granting them the `admin` role or demote other teammates by granting them the `member` role.
 
-Only other teammates can be managed this way. You can not demote yourself. To drop the `admin` role, promote another teammate to `admin` and ask the teammate to demote you. This guarantees that your organization always have at least one administrator.
+Only other teammates can be managed this way. You can not demote yourself. To drop the `admin` role, promote another teammate to `admin` and ask the teammate to demote you. This guarantees that your organization always has at least one administrator.
 
 In case the only teammate having an `admin` role is not active anymore, and you need to promote a new admin, please get in touch with our support.
 

docs/cloud/previews/index.md

@@ -1,6 +1,6 @@
 ---
 title: Pull Requests and Previews
-description: Learn how to synchronize pull reuest previews from CLI, automation or via Terramate Scripts, how to visualize Previews in Terramate Cloud.
+description: Learn how to synchronize pull request previews from CLI, automation or via Terramate Scripts, how to visualize Previews in Terramate Cloud.
 ---
 
 # Pull Requests and Previews

docs/cloud/previews/synchronization-in-automation.md

@@ -29,5 +29,5 @@ To gather metadata from GitHub about the pull request associated with the previe
 - Use OpenID Connect (OIDC) to authenticate to your Cloud Provider to use short-lived credentials - Terramate CLI uses OIDC by default.
 - Ensure that all drift checks run on all stacks even if some errors are detected using the `--continue-on-error` command line option
 - Run a Drift Check right after the deployment and synchronize the result to Terramate Cloud to get an immediate health check and ensure the deployment is stable.
-- Run a Drift Check at least every 24h to get a detailed history about when drifts were introduced.
+- Run a Drift Check at least every 24 hours to get a detailed history of when drifts were introduced.
 - Set up notifications to get informed about newly detected drifts in stacks