Fixed newlines from tutorial .md files rendering ugly.

Moved explenation of certificates to tutorial because it was too specific

docs/src/.vuepress/theme.ts

@@ -797,7 +797,7 @@ export default hopeTheme({
             icon: "info",
             prefix: "dsf/",
             link: "dsf/",
-            children: ["about-version-placeholders-and-urls.md", "bpmn-process-execution.md", "bpmn-process-variables.md", "certificates.md", "draft-task-resources.md", "environment-variables.md", "examples-for-requester-and-recipient-elements.md", "message-correlation.md", "message-delegates.md", "organization-identifiers.md", "process-api.md", "read-access-tag.md", "service-delegates.md", "spring-integration.md", "the-process-plugin-definition.md"], 
+            children: ["about-version-placeholders-and-urls.md", "bpmn-process-execution.md", "bpmn-process-variables.md", "draft-task-resources.md", "environment-variables.md", "examples-for-requester-and-recipient-elements.md", "message-correlation.md", "message-delegates.md", "organization-identifiers.md", "process-api.md", "read-access-tag.md", "service-delegates.md", "spring-integration.md", "the-process-plugin-definition.md"], 
           }]
         },
         {

docs/src/developer-documentation/concepts/bpmn/conditions.md

@@ -5,13 +5,4 @@ icon: creative
 
 ### Conditions
 
-[Conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions)
-allow you to change the behaviour of BPMN processes during execution. There are two ways you
-are able to add decision logic to Conditions. The [Camunda Modeler](https://camunda.com/download/modeler/) refers to them as `Type`. You can find them in the ``Condition`` tab of
-certain BPMN elements. The first one is `Script`. This allows you to add arbitrary complexity
-to your decisions logic and is rarely used for process plugins. The more common Type is `Expression`.
-Expressions have the following syntax: `${expression}`. For this tutorial, _expression_ will
-use a boolean condition like `var == true`. You can learn more advanced features of Expressions [here](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/).
-For this to work during BPMN process execution, the variable you want to use for the boolean
-condition must be available in the BPMN process variables before [Sequence Flow](../../concepts/bpmn/sequence-flow.md)
-reaches the evaluation of the expression.
+[Conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions) allow you to change the behaviour of BPMN processes during execution. There are two ways you are able to add decision logic to Conditions. The [Camunda Modeler](https://camunda.com/download/modeler/) refers to them as `Type`. You can find them in the ``Condition`` tab of certain BPMN elements. The first one is `Script`. This allows you to add arbitrary complexity to your decisions logic and is rarely used for process plugins. The more common Type is `Expression`. Expressions have the following syntax: `${expression}`. An example of a simple expression would be a boolean condition like `var == true`. For this to work during BPMN process execution, the variable you want to use for the boolean condition must be available in the BPMN process variables before [Sequence Flow](../../concepts/bpmn/sequence-flow.md) reaches the evaluation of the expression. You can learn more advanced features of Expressions [here](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/).

docs/src/developer-documentation/concepts/bpmn/gateways.md

@@ -5,21 +5,12 @@ icon: creative
 
 ### Gateways
 
-[Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/) allow you to control the [Sequence Flow](../../concepts/bpmn/sequence-flow.md). Different
-types of gateways will be useful for different scenarios.
+[Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/) allow you to control the [Sequence Flow](../../concepts/bpmn/sequence-flow.md). Different types of gateways will be useful for different scenarios.
 
 #### Exclusive Gateways
 
-[Exclusive Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/)
-allow you to decide which [Sequence Flow](../../concepts/bpmn/sequence-flow.md) should be followed based on [conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions).
-[Conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions) are not part of the
-[Exclusive Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/) themselves. You set them
-through the sequence Flow Exiting the [Exclusive Gateway](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/).  
-In the [Camunda Modeler](https://camunda.com/download/modeler/), you can add conditions to [Sequence Flow](../../concepts/bpmn/sequence-flow.md) by selecting
-a [Sequence Flow](../../concepts/bpmn/sequence-flow.md) and opening the `Condition` tab. You can find more information on how to
-use Conditions [here](../../concepts/bpmn/conditions.md).
+[Exclusive Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/) allow you to decide which [Sequence Flow](../../concepts/bpmn/sequence-flow.md) should be followed based on [conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions). [Conditions](https://docs.camunda.org/manual/7.20/user-guide/process-engine/expression-language/#conditions) are not part of the [Exclusive Gateways](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/) themselves. You set them through the sequence Flow Exiting the [Exclusive Gateway](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/exclusive-gateway/).   In the [Camunda Modeler](https://camunda.com/download/modeler/), you can add conditions to [Sequence Flow](../../concepts/bpmn/sequence-flow.md) by selecting a [Sequence Flow](../../concepts/bpmn/sequence-flow.md) and opening the `Condition` tab. You can find more information on how to use Conditions [here](../../concepts/bpmn/conditions.md).
 
 #### Event-based Gateway
 
-The [Event-based Gateway](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/event-based-gateway/)
-allows you model scenarios where you are expecting one out of a number of events to occur. 
+The [Event-based Gateway](https://docs.camunda.org/manual/7.20/reference/bpmn20/gateways/event-based-gateway/) allows you model scenarios where you are expecting one out of a number of events to occur. 

docs/src/developer-documentation/concepts/bpmn/intro.md

@@ -3,13 +3,4 @@ title: Introduction
 icon: creative
 ---
 
-The DSF uses BPMN 2.0 to model processes. Specifically, the [Camunda 7](https://docs.camunda.org/manual/7.20/) dialect from the [Camunda Modeler](https://camunda.com/de/download/modeler/).
-Modeling processes for the DSF requires this modeler or any other modeler which is able to produce the correct Camunda dialect.
-
-### Common BPMN Components
-- Sequence Flow
-- Service Tasks
-- User Tasks
-- Message Events
-- Timer Events
-- 
+The DSF uses BPMN 2.0 to model processes. Specifically, the [Camunda 7](https://docs.camunda.org/manual/7.20/) dialect from the [Camunda Modeler](https://camunda.com/de/download/modeler/). Modeling processes for the DSF requires this modeler or any other modeler which is able to produce the correct Camunda dialect.

docs/src/developer-documentation/concepts/bpmn/messaging.md

@@ -6,34 +6,19 @@ icon: creative
 
 ### Messaging
 
-In order to enable communication with other lanes, pools or even entirely separate processes you need to be able
-to exchange information. In BPMN, you can use [Message Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/)
-to model this information exchange. Modeling communication with [Message Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/) in the same diagram
-uses Message Flow. Message Flow is typically represented by a dashed line arrow between BPMN elements with a black (send) or white (receive) envelope icon.
-The following BPMN collaboration diagram shows message exchange between two processes.
-
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="/photos/developer-documentation/exercise3_message_flow_inverted.svg">
-  <source media="(prefers-color-scheme: light)" srcset="/photos/developer-documentation/exercise3_message_flow.svg">
-  <img alt="BPMN collaboration diagram with two processes using message flow to exchange information between two organizations" src="/photos/developer-documentation/exercise3_message_flow.svg">
-</picture>
+In order to enable communication with other lanes, pools or even entirely separate processes you need to be able to exchange information. In BPMN, you can use [Message Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/) to model this information exchange. Modeling communication with [Message Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/) in the same diagram uses Message Flow. Message Flow is typically represented by a dashed line arrow between BPMN elements with a black (send) or white (receive) envelope icon. The following BPMN collaboration diagram shows message exchange between two processes.
+
+![BPMN collaboration diagram with two processes using message flow to exchange information between two organizations](/photos/developer-documentation/exercise3_message_flow.svg)
 
 #### Message Start Event
 
-[Message Start Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-start-event)
-allow a BPMN process to be started by an incoming message. In the DSF, all BPMN processes are started via messages. Therefore,
-you will have to include a [Message Start Event](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-start-event) at
-the beginning of all of your BPMN models.
+[Message Start Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-start-event) allow a BPMN process to be started by an incoming message. In the DSF, all BPMN processes are started via messages. Therefore, you will have to include a [Message Start Event](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-start-event) at the beginning of all of your BPMN models.
 
 #### Message Intermediate Throwing Event
-[Message Intermediate Throwing Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-intermediate-throwing-event)
-are used to send messages during process execution.
+[Message Intermediate Throwing Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-intermediate-throwing-event) are used to send messages during process execution.
 
 #### Message Intermediate Catching Event
-[Message Intermediate Catching Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-intermediate-catching-event) serve as
-the counterpart to [Message Intermediate Throwing Events](messaging.md#message-intermediate-throwing-event).
-Use them whenever you expect to receive a message from another process or organization during execution.
+[Message Intermediate Catching Events](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-intermediate-catching-event) serve as the counterpart to [Message Intermediate Throwing Events](messaging.md#message-intermediate-throwing-event). Use them whenever you expect to receive a message from another process or organization during execution.
 
 #### Message End Event
-The [Message End Event](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-end-event) will
-stop the execution of a BPMN process and finish by sending a message.
+The [Message End Event](https://docs.camunda.org/manual/7.20/reference/bpmn20/events/message-events/#message-end-event) will stop the execution of a BPMN process and finish by sending a message.

docs/src/developer-documentation/concepts/bpmn/sequence-flow.md

@@ -4,5 +4,4 @@ icon: creative
 ---
 
 ### Sequence Flow
-BPMN 2.0 calls the continuous arrows connecting the BPMN elements in BPMN models, Sequence Flow.
-Sequence Flow exits one BPMN element and points at the next BPMN element to be processed.
+BPMN 2.0 calls the continuous arrows connecting the BPMN elements in BPMN models, Sequence Flow. Sequence Flow exits one BPMN element and points at the next BPMN element to be processed.

docs/src/developer-documentation/concepts/bpmn/service-tasks.md

@@ -5,8 +5,4 @@ icon: creative
 
 ### Service Tasks
 
-You will primarily use [Service Tasks](https://docs.camunda.org/manual/7.20/reference/bpmn20/tasks/service-task/)
-when creating BPMN models. They are different from regular BPMN Tasks in that they offer the ability to
-link an implementation to the [Service Task](https://docs.camunda.org/manual/7.20/reference/bpmn20/tasks/service-task/)
-which can be called and executed by a BPMN engine. The BPE (Business Process Engine) server of the DSF leverages
-this engine to execute your BPMN processes.
+One of the most common types of BPMN Tasks used for modeling DSF processes is the [Service Task](https://docs.camunda.org/manual/7.20/reference/bpmn20/tasks/service-task/). They are different from regular BPMN Tasks in that they offer the ability to link an implementation to the [Service Task](https://docs.camunda.org/manual/7.20/reference/bpmn20/tasks/service-task/) which can be called and executed by a BPMN engine. The BPE (Business Process Engine) server of the DSF leverages this engine to execute your BPMN processes.

docs/src/developer-documentation/concepts/bpmn/timer-intermediate-catching-events.md

@@ -5,8 +5,4 @@ icon: creative
 
 ### Timer Intermediate Catching Events
 
-A [Timer Intermediate Catching Event](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#timer-intermediate-catching-event)
-allows you model stopwatch behavior. A timer is started once the BPMN execution arrives at the event.
-The duration until the timer runs out is specified using the [ISO 8601 Durations](http://en.wikipedia.org/wiki/ISO_8601#Durations) format.
-Examples can be found [here](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#time-duration). After running out, the BPMN process executes the [Sequence Flow](../../concepts/bpmn/sequence-flow.md) following
-the [Timer Intermediate Catching Event](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#timer-intermediate-catching-event).
+A [Timer Intermediate Catching Event](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#timer-intermediate-catching-event) allows you to model stopwatch behavior. A timer is started once the BPMN execution arrives at the event. The duration until the timer runs out is specified using the [ISO 8601 Durations](http://en.wikipedia.org/wiki/ISO_8601#Durations) format. Examples can be found [here](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#time-duration). After running out, the BPMN process executes the [Sequence Flow](../../concepts/bpmn/sequence-flow.md) following the [Timer Intermediate Catching Event](https://docs.camunda.org/manual/7.17/reference/bpmn20/events/timer-events/#timer-intermediate-catching-event).