Update serverlessworkflow/modules/ROOT/pages/use-cases/advanced-devel…

…oper-use-cases/getting-started/create-your-first-workflow-project.adoc

Co-authored-by: Dominik Hanák <[email protected]>

serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc

@@ -51,8 +51,8 @@ Quarkus unifies reactive and imperative programming you can find it more explain
 
 In this phase we need to decide how the Event-Driven Architecture needs to be added to our project. We have different options here:
 
-* *Kafka Connector* for Reactive Messaging. xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-producing-events-with-kafka.adoc[]
-* *Knative* eventing. xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[]
+* *Kafka Connector* for Reactive Messaging. See xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-producing-events-with-kafka.adoc[] for more details.
+* *Knative* eventing.  See xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[] for more details.
 
 When we choose how the different project components will communicate. More details about link:https://quarkus.io/guides/quarkus-reactive-architecture#quarkus-extensions-enabling-reactive[Quarkus Extensions enabling Reactive]