diff --git a/modules/migrate/pages/console-v3.adoc b/modules/migrate/pages/console-v3.adoc
index 66559a55bb..1568dd4d45 100644
--- a/modules/migrate/pages/console-v3.adoc
+++ b/modules/migrate/pages/console-v3.adoc
@@ -130,8 +130,6 @@ NOTE: OIDC-based group authorization is no longer available in Redpanda Console.
 
 Here is an example of how to migrate from Google OIDC in v2 to v3:
 
-Here is an example of how to migrate from Google OIDC in v2 to v3:
-
 [.side-by-side]
 --
 .V2 Google OIDC
@@ -212,11 +210,11 @@ authorization:
 ----
 --
 
-However, if you are using *impersonation* in v3, `roleBindings` are ignored. Instead, access is controlled by Redpanda using ACLs and RBAC.
-
 ==== Migrate Redpanda Console roles to Redpanda ACLs
 
-If you previously assigned roles in Redpanda Console, you must provision those users in Redpanda and grant them the appropriate permissions.
+If you are using *impersonation* in v3, `roleBindings` are ignored. Instead, access is controlled by Redpanda using ACLs and RBAC.
+
+You must provision your users in Redpanda and grant them the appropriate permissions.
 
 The following examples show how to map Redpanda Console roles (`viewer`, `editor`, `admin`) to Redpanda ACLs.