review comments

hashicorp · May 2, 2024 · 27a6959 · 27a6959
1 parent 3fb76bf
commit 27a6959
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 7 deletions.
diff --git a/website/content/vagrant-cloud/hcp-vagrant/migration-guide.mdx b/website/content/vagrant-cloud/hcp-vagrant/migration-guide.mdx
@@ -56,14 +56,10 @@ Your HCP account must use the email address associated with your Vagrant Cloud a
 
 Once you have signed into both your HCP and Vagrant Cloud accounts, you can access the [migration tool](https://app.vagrantup.com/migration).
 
-To auto-populate the migration tool with a specific Vagrant Cloud `Organization` click on the `Migrate to HCP` button in the top right corner of your [settings](https://app.vagrantup.com/settings) page.
-
 #### 2. Select a Vagrant Cloud organization to migrate
 
 Select a single organization from the dropdown to migrate or select the checkbox `Migrate all organizations` to migrate them all at once to a single HCP Project.
 
-You can select any of the organizations listed in the Vagrant Cloud organization dropdown, even if a specific organization was pre-populated.
-
 ##### 3. Select a destination project in HCP
 
 If you have multiple projects in HCP, select the project you want from the HCP Project dropdown. If you have not created a second project the `default-project` will be auto-selected.
@@ -88,4 +84,6 @@ It is important to note that while a migrated organization will no longer be ava
 
 ## Conclusion
 
-If for some reason you are unable to access your new HCP Registry or your migration does not complete successfully, review the [Migration Troubleshooting] (/vagrant/vagrant-cloud/hcp-vagrant/troubleshooting) guide or contact us at [support@hashicorp.com](mailto:support@hashicorp.com) with the subject `HCP Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.
+If for some reason you are unable to access your new HCP Registry or your migration does not complete successfully, review the [Migration Troubleshooting] (/vagrant/vagrant-cloud/hcp-vagrant/troubleshooting) guide or contact us at [support+vagrantcloud@hashicorp.com](mailto:support@hashicorp.com) with the subject `HCP Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.
+
+
diff --git a/website/content/vagrant-cloud/hcp-vagrant/troubleshooting.mdx b/website/content/vagrant-cloud/hcp-vagrant/troubleshooting.mdx
@@ -16,5 +16,5 @@ In the rare case that an inoperable box was successfully uploaded (e.g legacy bo
 
 ### Retrying Migrations
 
-If a migration fails, a `retry` icon will appear beside the name of that organization on the [migration status](https://app.beta.vagrantup.com/migration/status) page. Failed migrations can be retried once.
-In the event of a second failure, contact us at [support@hashicorp.com](mailto:support@hashicorp.com) with the subject `Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.
+If a migration fails, a `retry` icon will appear beside the name of that organization on the [migration status](https://app.vagrantup.com/migration/status) page. Failed migrations can be retried once.
+In the event of a second failure, contact us at [support+vagrantcloud@hashicorp.com](mailto:support@hashicorp.com) with the subject `Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.