diff --git a/docs/docs/self-hosting/manage/updating_scaling.md b/docs/docs/self-hosting/manage/updating_scaling.md
index a716c63a03..7b8c72bd32 100644
--- a/docs/docs/self-hosting/manage/updating_scaling.md
+++ b/docs/docs/self-hosting/manage/updating_scaling.md
@@ -65,7 +65,7 @@ The init phase is idempotent if executed with the same binary version.
 
 ### The Setup Phase
 
-During `zitadel setup`, ZITADEL creates projection tables and migrates existing data, if `--init-projections` is set.
+During `zitadel setup`, ZITADEL creates projection tables and migrates existing data, if `--init-projections=true` is set.
 Depending on the ZITADEL version and the runtime resources,
 this step can take several minutes.
 When deploying a new ZITADEL version,
@@ -85,4 +85,4 @@ Beware, in the background, out-of-date projections
 [recompute their state by replaying all missed events](/docs/concepts/eventstore/implementation#projections).
 If a new ZITADEL version is deployed, this can take quite a long time,
 depending on the amount of events to catch up.
-You probably should consider providing `--init-projections`-flag to the [Setup Phase](#the-setup-phase) to shift the synchronization time to previous steps and delay the startup phase until events are caught up.
\ No newline at end of file
+You probably should consider providing `--init-projections=true`-flag to the [Setup Phase](#the-setup-phase) to shift the synchronization time to previous steps and delay the startup phase until events are caught up.
\ No newline at end of file
diff --git a/docs/docs/support/advisory/a10008.md b/docs/docs/support/advisory/a10008.md
index 8848fd05a2..811c64d773 100644
--- a/docs/docs/support/advisory/a10008.md
+++ b/docs/docs/support/advisory/a10008.md
@@ -27,13 +27,13 @@ If you use different configurations on `setup` and `start` and have overwritten
 
 ## Statement
 
-Filling of projections can get time consuming as your system grows and this can cause downtime of self hosted installations of ZITADEL because queries first need to ensure data consistency.
+Filling of projections can get time-consuming as your system grows and this can cause downtime of self-hosted installations of ZITADEL because queries first need to ensure data consistency.
 
 Before this release, this step was executed after the start of ZITADEL and therefore lead to inconsistent retrieval of data until the projections were up-to-date. 
 
 ## Mitigation
 
-Enable the `--init-projections`-flag in setup phase and make sure the previous deployment of ZITADEL remains active until the new revision started properly.
+Enable the flag (`--init-projections=true`) in setup phase and make sure the previous deployment of ZITADEL remains active until the new revision started properly.
 
 ## Impact