From 78f859004fe3cb1ce29c56b091a49ab6efb4a8e4 Mon Sep 17 00:00:00 2001 From: Christian J Date: Wed, 12 Aug 2026 13:35:42 -0500 Subject: [PATCH] Minor fixes to various typos and improved grammar for better readability --- .../blueprints/blueprints-yaml-structure.md | 2 +- docs/workflows/workflows-overview.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/blueprint-designer-guide/blueprints/blueprints-yaml-structure.md b/docs/blueprint-designer-guide/blueprints/blueprints-yaml-structure.md index ed2d78e55..eb1ec0029 100644 --- a/docs/blueprint-designer-guide/blueprints/blueprints-yaml-structure.md +++ b/docs/blueprint-designer-guide/blueprints/blueprints-yaml-structure.md @@ -15,7 +15,7 @@ spec_version: 2 ``` ### `description` -The blueprint’s description is an optional but recommended field. Blueprint description will be presented in the Torque's UI and API so users consuming environment will have more information about the blueprints to batter match their business need to the available set of blueprints published in the account catalog. +The blueprint’s description is an optional but recommended field. Blueprint description will be presented in the Torque's UI and API so users consuming environment will have more information about the blueprints to better match their business need to the available set of blueprints published in the account catalog. ```yaml diff --git a/docs/workflows/workflows-overview.md b/docs/workflows/workflows-overview.md index 561b7e0ca..d49d8bd4e 100644 --- a/docs/workflows/workflows-overview.md +++ b/docs/workflows/workflows-overview.md @@ -7,7 +7,7 @@ Torque Workflows are a powerful way to automate and orchestrate complex processe ## Workflow Discovery -Workflow discovery is done in the same way as Blueprints. The YAML files need to be under the `blueprints/` directory in the repository. Torque automatically scans for workflow files and makes them available based on their scope and configuration. +Workflow discovery is done in the same way as Blueprints. The YAML files need to be under the `blueprints/` directory in the repository. Torque will automatically scan for workflow files and make them available based on their scope and configuration. The Workflow YAML standard is similar to the Blueprint standard. The only addition to the Workflow specification is the `workflow` block, which defines the workflow-specific configuration. @@ -54,7 +54,7 @@ grains: ### `scope` -The `scope` field in a Torque workflow determines where the workflow is available. There are two possible values for the `scope` field: +The `scope` field in a Torque workflow determines where the workflow is available. There are three possible values for the `scope` field: 1. `space`: Workflows with this scope are available at the space level, and can be triggered and executed without any dependencies. 2. `env`: Workflows with this scope are available at the environment level. This means that they can be triggered and executed for the entire environment. These workflows can be used to automate and orchestrate processes that involve multiple resources within the environment. @@ -62,7 +62,7 @@ The `scope` field in a Torque workflow determines where the workflow is availabl ### `resource-types` -When scoping a the workflow to an `env_resource`, the `resource-types` field allow to attach that workflow to the specified resource types. +When scoping a workflow to an `env_resource`, the `resource-types` field allow to attach that workflow to the specified resource types. In this example, we scope this workflow only AWS EC2 instances resources: