diff --git a/packages/@aws-cdk/cx-api/FEATURE_FLAGS.md b/packages/@aws-cdk/cx-api/FEATURE_FLAGS.md
index 5ca5af6fb8756..b6d5956dc3359 100644
--- a/packages/@aws-cdk/cx-api/FEATURE_FLAGS.md
+++ b/packages/@aws-cdk/cx-api/FEATURE_FLAGS.md
@@ -36,7 +36,7 @@ Flags come in three types:
 | [@aws-cdk/aws-ecs:arnFormatIncludesClusterName](#aws-cdkaws-ecsarnformatincludesclustername) | ARN format used by ECS. In the new ARN format, the cluster name is part of the resource ID. | 2.35.0 | (fix) |
 | [@aws-cdk/aws-apigateway:disableCloudWatchRole](#aws-cdkaws-apigatewaydisablecloudwatchrole) | Make default CloudWatch Role behavior safe for multiple API Gateways in one environment | 2.38.0 | (fix) |
 | [@aws-cdk/core:enablePartitionLiterals](#aws-cdkcoreenablepartitionliterals) | Make ARNs concrete if AWS partition is known | 2.38.0 | (fix) |
-| @aws-cdk/aws-ecs:disableExplicitDeploymentControllerForCircuitBreaker | Avoid setting the "ECS" deployment controller when adding a circuit breaker | 2.51.0 | (fix) |
+| [@aws-cdk/aws-ecs:disableExplicitDeploymentControllerForCircuitBreaker](#aws-cdkaws-ecsdisableexplicitdeploymentcontrollerforcircuitbreaker) | Avoid setting the "ECS" deployment controller when adding a circuit breaker | 2.51.0 | (fix) |
 | [@aws-cdk/aws-events:eventsTargetQueueSameAccount](#aws-cdkaws-eventseventstargetqueuesameaccount) | Event Rules may only push to encrypted SQS queues in the same account | 2.51.0 | (fix) |
 
 <!-- END table -->
@@ -65,7 +65,8 @@ The following json shows the current recommended set of flags, as `cdk init` wou
     "@aws-cdk/aws-sns-subscriptions:restrictSqsDescryption": true,
     "@aws-cdk/aws-apigateway:disableCloudWatchRole": true,
     "@aws-cdk/core:enablePartitionLiterals": true,
-    "@aws-cdk/aws-events:eventsTargetQueueSameAccount": true
+    "@aws-cdk/aws-events:eventsTargetQueueSameAccount": true,
+    "@aws-cdk/aws-ecs:disableExplicitDeploymentControllerForCircuitBreaker": true
   }
 }
 ```
@@ -646,7 +647,7 @@ is unknown.
 
 ### @aws-cdk/aws-ecs:disableExplicitDeploymentControllerForCircuitBreaker
 
-Avoid setting the "ECS" deployment controller when adding a circuit breaker (fix)
+*Avoid setting the "ECS" deployment controller when adding a circuit breaker* (fix)
 
 Enable this feature flag to avoid setting the "ECS" deployment controller when adding a circuit breaker to an
 ECS Service, as this will trigger a full replacement which fails to deploy when using set service names.
@@ -654,7 +655,12 @@ This does not change any behaviour as the default deployment controller when it
 
 This is a feature flag as the new behavior provides a better default experience for the users.
 
-Introduced in **2.51.0**, recommended value `true`.
+
+| Since | Default | Recommended |
+| ----- | ----- | ----- |
+| (not in v1) |  |  |
+| 2.51.0 | `false` | `true` |
+
 
 ### @aws-cdk/aws-events:eventsTargetQueueSameAccount
 
diff --git a/packages/@aws-cdk/cx-api/lib/features.ts b/packages/@aws-cdk/cx-api/lib/features.ts
index a9cc1dea335f3..b7d541d31ca9c 100644
--- a/packages/@aws-cdk/cx-api/lib/features.ts
+++ b/packages/@aws-cdk/cx-api/lib/features.ts
@@ -520,7 +520,7 @@ export const FLAGS: Record<string, FlagInfo> = {
   [ECS_DISABLE_EXPLICIT_DEPLOYMENT_CONTROLLER_FOR_CIRCUIT_BREAKER]: {
     type: FlagType.BugFix,
     summary: 'Avoid setting the "ECS" deployment controller when adding a circuit breaker',
-    details: `
+    detailsMd: `
       Enable this feature flag to avoid setting the "ECS" deployment controller when adding a circuit breaker to an
       ECS Service, as this will trigger a full replacement which fails to deploy when using set service names.
       This does not change any behaviour as the default deployment controller when it is not defined is ECS.