Skip to content

Commit ac09dd1

Browse files
author
Tihomir Surdilovic
authored
fix table of contents and double heading (#298) (#299)
Signed-off-by: Tihomir Surdilovic <[email protected]>
1 parent 4cff0c3 commit ac09dd1

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

specification.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ You can find the specification roadmap [here](roadmap/README.md).
2020
- [Project Components](#Project-Components)
2121
- [Specification Details](#Specification-Details)
2222
- [Core Concepts](#Core-Concepts)
23+
- [Workflow Definition](#Workflow-Definition)
2324
- [Workflow Model](#Workflow-Model)
2425
- [Workflow Data](#Workflow-Data)
2526
- [Workflow Functions](#Workflow-Functions)
2627
- [Workflow Expressions](#Workflow-Expressions)
27-
- [Workflow Definition](#Workflow-Definition)
2828
- [Workflow Error Handling](#Workflow-Error-Handling)
2929
- [Defining Errors](#Defining-Errors)
3030
- [Defining Retries](#Defining-Retries)
@@ -107,8 +107,8 @@ This section describes some of the core Serverless Workflow concepts:
107107
### Workflow Definition
108108

109109
A workflow definition is a single artefact written in the Serverless Workflow
110-
language. It consists of a set of [workflow model](#Workflow-Model) constructs,
111-
and defines a blueprint used by runtimes for its execution.
110+
language. It consists of the core [Workflow Definition Structure](#Workflow-Definition-Structure)
111+
and the [Workflow Model](#Workflow-Model) It defines a blueprint used by runtimes for its execution.
112112

113113
A business solution can be composed of any number of related workflow definitions.
114114
Their relationships are explicitly modeled with the Serverless Workflow language (for example
@@ -1349,7 +1349,7 @@ We can now get back to our previously defined "IsAdultApplicant" expression func
13491349
As previously mentioned, expressions are evaluated against certain subsets of data. For example
13501350
the `parameters` param of the [functionRef definition](#FunctionRef-Definition) can evaluate expressions
13511351
only against the data that is available to the [action](#Action-Definition) it belongs to.
1352-
One thing to note here are the top-level [workflow definition](#Workflow-Definition) parameters. Expressions defined
1352+
One thing to note here are the top-level [workflow definition](#Workflow-Definition-Structure) parameters. Expressions defined
13531353
in them can only be evaluated against the initial [workflow data input](#Workflow-Data-Input).
13541354

13551355
For example let's say that we have a workflow data input of:
@@ -1374,7 +1374,7 @@ which would set the workflow version to "1.0.0".
13741374
Note that the workflow "id" property value is not allowed to use an expression. The workflow
13751375
definition "id" must be a constant value.
13761376

1377-
### Workflow Definition
1377+
### Workflow Definition Structure
13781378

13791379
| Parameter | Description | Type | Required |
13801380
| --- | --- | --- | --- |
@@ -4843,7 +4843,7 @@ Metadata includes key/value pairs (string types). Both keys and values are compl
48434843

48444844
Metadata can be added to:
48454845

4846-
- [Core Workflow definition](#Workflow-Definition)
4846+
- [Workflow Definition](#Workflow-Definition-Structure)
48474847
- [Function definitions](#Function-Definition)
48484848
- [Event definitions](#Event-Definition)
48494849
- [State definitions](#State-Definition)

0 commit comments

Comments
 (0)