Fixup copy and add link within nav

website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx

@@ -10,7 +10,7 @@ This document describes the behavior of Vagrant Cloud after an organization is m
 
 # Vagrant Cloud Redirects
 
-After an ogranization has been migrated to HCP Vagrant Registry any requests Vagrant Cloud receives for that organization, or any boxes within that organization, will be automatically redirected to the proper location on HCP Vagrant Registry.
+After an organization has been migrated to HCP Vagrant Registry any requests Vagrant Cloud receives for that organization, or any boxes within that organization, will be automatically redirected to the proper location on HCP Vagrant Registry.
 
 # API 
 
@@ -26,7 +26,7 @@ The format of the composite access token is:
 <VAGRANT_CLOUD_TOKEN>;<HCP_TOKEN>
 ```
 
-If all organizations have been migrated to HCP Vagrant Registry the Vagrant Cloud access token will not be needed and the format of the access token is:
+If all organizations have been migrated to HCP Vagrant Registry the Vagrant Cloud access token will not be needed. The format of the access token is:
 
 ```
 ;<HCP_TOKEN>
@@ -36,8 +36,8 @@ If all organizations have been migrated to HCP Vagrant Registry the Vagrant Clou
 
 The following prerequisites are required for generating an HCP access token:
 
-* [HCP Service Principal](https://developer.hashicorp.com/hcp/docs/hcp/admin/iam/service-principals)
-* [HCP CLI](https://developer.hashicorp.com/hcp/docs/cli)
+* [HCP Service Principal](/hcp/docs/hcp/admin/iam/service-principals)
+* [HCP CLI](/hcp/docs/cli)
 
 Using the `CLIENT_ID` and `CLIENT_SECRET` from the HCP service principal login to HCP using the `hcp` command:
 

website/data/vagrant-cloud-nav-data.json

@@ -9,6 +9,10 @@
       {
         "title": "Migration Troubleshooting",
         "path": "hcp-vagrant/troubleshooting"
+      },
+      {
+          "title": "Post Migration",
+          "path": "hcp-vagrant/post-migration-guide"
       }
     ]
   },