diff --git a/docs/proposals/202105256-cluster-class-and-managed-topologies.md b/docs/proposals/202105256-cluster-class-and-managed-topologies.md
index b0242f7c6294..3916b3d8f1aa 100644
--- a/docs/proposals/202105256-cluster-class-and-managed-topologies.md
+++ b/docs/proposals/202105256-cluster-class-and-managed-topologies.md
@@ -346,9 +346,9 @@ There are cases where we must consider whether two ClusterClasses are compatible
 2. Where a user updates a ClusterClass currently in use by a Cluster.
 
 To establish compatibility between two ClusterClasses:
-    - All the references must be in the same namespace of `metadata.Namespace` - the same namespace as the existing clusterClass.
-    - `spec.workers.machineDeployments` must not remove any deployment classes (adding new or modifying existing classes is supported).
-    - `spec.controlPlane.localobjecttemplate`, `spec.controlplane.machineinfrastructure`, `spec.infrastructure`,  `spec.workers.machineDeployments[].template.infrastructure.ref` must not change apiGroup or Kind.
+  - All the references must be in the same namespace of `metadata.Namespace` - the same namespace as the existing clusterClass.
+  - `spec.workers.machineDeployments` must not remove any deployment classes (adding new or modifying existing classes is supported).
+  - `spec.controlPlane.localobjecttemplate`, `spec.controlplane.machineinfrastructure`, `spec.infrastructure`,  `spec.workers.machineDeployments[].template.infrastructure.ref` must not change apiGroup or Kind.
 
 #### Behaviors
 This section lists out the behavior for Cluster objects using `ClusterClass` in case of creates and updates.