diff --git a/internal/command/meta_backend.go b/internal/command/meta_backend.go
index 005237845..5c7f04df3 100644
--- a/internal/command/meta_backend.go
+++ b/internal/command/meta_backend.go
@@ -1426,7 +1426,7 @@ in your Terraform Cloud organization. To finish initializing, Terraform needs at
 least one workspace available.
 
 Terraform can create a properly tagged workspace for you now. Please enter a
-name to create a new Terraform Cloud workspace:
+name to create a new Terraform Cloud workspace.
 `
 
 const successBackendUnset = `
diff --git a/internal/command/meta_backend_migrate.go b/internal/command/meta_backend_migrate.go
index 508199ade..97162eb8b 100644
--- a/internal/command/meta_backend_migrate.go
+++ b/internal/command/meta_backend_migrate.go
@@ -897,9 +897,6 @@ For example, if a workspace is currently named 'prod', the pattern 'app-*' would
 `
 
 const tfcInputBackendMigrateMultiToMulti = `
-When migrating existing workspaces from the backend %[1]q to Terraform Cloud, would you like to
-rename your workspaces?
-
 Unlike typical Terraform workspaces representing an environment associated with a particular
 configuration (e.g. production, staging, development), Terraform Cloud workspaces are named uniquely
 across all configurations used within an organization. A typical strategy to start with is
@@ -907,6 +904,9 @@ across all configurations used within an organization. A typical strategy to sta
 
 For more information on workspace naming, see https://www.terraform.io/docs/cloud/workspaces/naming.html
 
+When migrating existing workspaces from the backend %[1]q to Terraform Cloud, would you like to
+rename your workspaces? Enter 1 or 2.
+
 1. Yes, I'd like to rename all workspaces according to a pattern I will provide.
 2. No, I would not like to rename my workspaces. Migrate them as currently named.
 `