Skip to content

Commit 2250bb9

Browse files
committed
Eliminate trailing slash
1 parent 1bc20ea commit 2250bb9

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Microflows run in the runtime server and can therefore not be used in offline ap
1414

1515
This page is a summary of the elements which make up a microflow, together with their visual representation within the microflow. It also covers [keyboard support](#keyboard) when editing microflows.
1616

17-
For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For microflow best practices, see the[Microflows](/refguide/naming-convention-best-practices/#microflow-naming-conventions/) section of *Naming Convention Best Practices*, [Microflow General Best Practices](/refguide/general-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
17+
For the properties of the microflow itself, see [Microflow Properties](/refguide/microflow/). For microflow best practices, see the[Microflows](/refguide/naming-convention-best-practices/#microflow-naming-conventions) section of *Naming Convention Best Practices*, [Microflow General Best Practices](/refguide/general-best-practices/#microflow-dev-best-practices), and [Microflow Best Practices from the Community](/refguide/community-best-practices-for-app-performance/#microflow-community-best-practices).
1818

1919
For information on using microflows as data sources, see [Microflow Source](/refguide/microflow-source/).
2020

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/microflows/extract-and-use-sub-microflows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ To extract the validation steps into a sub-microflow, follow these steps:
4545

4646
3. In the **Add microflow** dialog box, enter a name for the sub-microflow.
4747

48-
{{% alert color="info" %}}As a best practice, use a consistent naming scheme that clearly identifies the sub-microflow, for example, *SUB_{Microflow description}*. For more naming best practices, see the [Microflow](/refguide/naming-convention-best-practices/#microflow-naming-conventions/) section of *Naming Convention Best Practices*.{{% /alert %}}
48+
{{% alert color="info" %}}As a best practice, use a consistent naming scheme that clearly identifies the sub-microflow, for example, *SUB_{Microflow description}*. For more naming best practices, see the [Microflow](/refguide/naming-convention-best-practices/#microflow-naming-conventions) section of *Naming Convention Best Practices*.{{% /alert %}}
4949

5050
4. Click **OK**.
5151
5. Open the sub-microflow by right-clicking the sub-microflow call and selecting **Go to microflow**.

0 commit comments

Comments
 (0)