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 9fde234b397accea79297fb110b29ed404aa4412
Author: Alex Heneveld <a...@cloudsoft.io>
AuthorDate: Thu Dec 7 12:53:37 2023 +0000
tidy some links in workflow
---
guide/blueprints/workflow/common.md | 2 +-
guide/blueprints/workflow/steps/index.md | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/guide/blueprints/workflow/common.md
b/guide/blueprints/workflow/common.md
index f18d7f32..910a5324 100644
--- a/guide/blueprints/workflow/common.md
+++ b/guide/blueprints/workflow/common.md
@@ -81,7 +81,7 @@ steps:
### Conditions
The previous example shows the use of conditions, as mentioned as one of the
properties common to all steps.
-This makes use of the recent "[Predicate
DSL](https://github.com/apache/brooklyn-docs/blob/master/guide/blueprints/yaml-reference.md#predicate-dsl)"
conditions framework .
+This makes use of the recent "[Predicate
DSL](../yaml-reference.md#predicate-dsl)" conditions framework .
It is normally necessary to supply a `target`, unless one of the
entity-specific target keys (e.g. `sensor` or `config`)
is used. The target and arguments here can use the [workflow expression
syntax](variables.md).
diff --git a/guide/blueprints/workflow/steps/index.md
b/guide/blueprints/workflow/steps/index.md
index 073c265e..ec9c71fd 100644
--- a/guide/blueprints/workflow/steps/index.md
+++ b/guide/blueprints/workflow/steps/index.md
@@ -13,13 +13,13 @@ Apache Brooklyn workflow supports a range of step types
covering the most common
commonly done as part of application management.
These are divided into the following groups:
-* [Workflow Control](#workflow_control): use local variables and control flow,
+* [Workflow Control](#workflow-control): use local variables and control flow,
with step types such as `let`, `return`, and `retry`
-* [External Actions](#external_actions): interact with external systems
+* [External Actions](#external-actions): interact with external systems
using step types such as `container`, `ssh`, `winrm`, and `http`
-* [Application Models](#application_models): work with the models stored in
Brooklyn,
+* [Application Models](#application-models): work with the models stored in
Brooklyn,
doing things such as `invoke-effector`, `set-sensor`, `deploy-application`,
and `add-entity`
-* [General Purpose](#general_purpose): miscellaneous step types such as `log`
and `sleep`
+* [General Purpose](#general-purpose): miscellaneous step types such as `log`
and `sleep`
Custom step types can be written and added to the catalog, either written as
workflow using these primitives
(including doing virtually anything in a container) or by implementing a Java
type, both [as described here](../nested-workflow.md).
