You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by he...@apache.org on 2022/10/24 11:03:00 UTC

[brooklyn-docs] 02/02: tidy language for workflow

This is an automated email from the ASF dual-hosted git repository.

heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git

commit e7e1ded054b69e7bd580bdb9747e09a36d5c5002
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Mon Oct 24 11:58:54 2022 +0100

    tidy language for workflow
---
 guide/blueprints/workflow/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/guide/blueprints/workflow/index.md b/guide/blueprints/workflow/index.md
index cbbda277..0d5b2304 100644
--- a/guide/blueprints/workflow/index.md
+++ b/guide/blueprints/workflow/index.md
@@ -10,7 +10,7 @@ children:
 - nested-workflow.md
 ---
 
-Apache Brooklyn has a powerful workflow engine and syntax for defining effectors, sensors, and policies.
+Apache Brooklyn has a powerful workflow engine and syntax for defining entities, effectors, sensors, and policies.
 
 For example, to define an effector `one-and-two` which invokes effector `one` then effector `two`, you can write:
 
@@ -23,7 +23,7 @@ brooklyn.initializers:
       - invoke-effector two
 ```
 
-This can be used to define [effectors, sensors, and policies](defining.md).
+This can be used within [most Apache Brooklyn resources](defining.md).
 
 The syntax supports [longhand, conditions, loops, error-handling](common.md), [variables](variables.md),
 a large set of [built-in step types](steps.md), and the ability to [define custom step types](nested-workflow.md).