diff --git a/docs/proposal/20210311-single-controller-multitenancy.md b/docs/proposal/20210311-single-controller-multitenancy.md
index d9fbf8ee86..afc3e5ea4e 100644
--- a/docs/proposal/20210311-single-controller-multitenancy.md
+++ b/docs/proposal/20210311-single-controller-multitenancy.md
@@ -210,7 +210,7 @@ type VSphereClusterSpec struct {
 
 #### Clusterctl Changes
 
-Today, clusterctl move operates by tracking objectreferences within the same namespace, since we are now proposing to use cluster-scoped resources, we will need to add requisite support to clusterctl's object graph to track cluster-scoped resources that are used by the source cluster, and ensure they are moved. We will naively not delete cluster-scoped resources during a move, as they maybe referenced across namespaces. If a cluster uses a `Secret` for account credentials, the OwnerReference will get set by the controller and the `Secret` will be moved to the target cluster. Any `VSphereClusterIdentity` that's required by the resources being moved, will need to be manually created on the target cluster prior to the move operation.
+Today, clusterctl move operates by tracking objectreferences within the same namespace, since we are now proposing to use cluster-scoped resources, we will need to add requisite support to clusterctl's object graph to track cluster-scoped resources that are used by the source cluster, and ensure they are moved. We will naively not delete cluster-scoped resources during a move, as they maybe referenced across namespaces. If a cluster uses a `Secret` for account credentials, the OwnerReference will get set by the controller and the `Secret` will be moved to the target cluster.
 
 ### Security Model