replacing We reference by You

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

@@ -4,7 +4,7 @@ As a developer, you can use {product_name} to create an application and in this
 
 We will also use Quarkus dev mode for iterative development and testing.
 
-As a common application development, we have different phases: Analysis, Development and Deployment. Let's explore in detail each phase and what {product_name} provides in each case:
+As a common application development, you have different phases: Analysis, Development and Deployment. Let's explore in detail each phase and what {product_name} provides in each case:
 
 * <<proc-analysis-phase,Analysis and taking decisions phase>>
 ** <<proc-adding-persistence,Adding persistence?>>
@@ -61,7 +61,7 @@ If we choose to add eventing, {product_name} supports different options like:
 * *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.
 
-We need to choose how the different project components will communicate and what kind of communication is needed. More details about link:https://quarkus.io/guides/quarkus-reactive-architecture#quarkus-extensions-enabling-reactive[Quarkus Extensions enabling Reactive]
+You need to choose how the different project components will communicate and what kind of communication is needed. More details about link:https://quarkus.io/guides/quarkus-reactive-architecture#quarkus-extensions-enabling-reactive[Quarkus Extensions enabling Reactive]
 
 [[proc-adding-data-index-service]]
 === Adding Data Index service?
@@ -161,6 +161,7 @@ This is a build time property, it cannot be changed at runtime after your applic
 At this stage you have a {product_name} Quarkus application well tested and ready to be deployed.
 
 There are two basic modes that a Quarkus application can be deployed:
+
 * As an standard Java application (executable jar with libraries on the classpath)
 * As a native executable which can be built using GraalVM link:{quarkus_guides_building_native}#producing-a-native-executable[Quarkus Building a native executable guide]
 
@@ -169,7 +170,7 @@ If you put either the Java application or the native executable app inside a con
 Quarkus provides extensions for building (and pushing) container images.
 You can find more details about that container images generation in link:{quarkus_guides_container_image_url}[Quarkus Container Image extensions]
 
-Once this container image is built it can be used as part of the decided topology. We have different options like:
+Once this container image is built it can be used as part of the decided topology. You have different options like:
 
 * xref:use-cases/advanced-developer-use-cases/deployments/deploying-on-minikube.adoc[]
 * xref:use-cases/advanced-developer-use-cases/deployments/deploying-on-kubernetes.adoc[]