website: Fix Vagrant Enterprise docs links

website/source/docs/vagrant-cloud/boxes/create.html.md

@@ -8,7 +8,7 @@ sidebar_current: "vagrant-cloud-boxes-create-x"
 
 This page will cover creating a new box in Vagrant Enterprise and how to distribute
 it to users. Boxes can be distributed without Vagrant Enterprise, but
-miss out on several [important features](/help/vagrant/boxes).
+miss out on several [important features](/docs/vagrant-cloud/boxes).
 
 There are __three ways to create and upload Vagrant Boxes to Vagrant Enterprise__. All
 three options are outlined below.
@@ -17,7 +17,7 @@ We recommend using Packer, as is it is fully repeatable and keeps a strong
 history of changes within Vagrant Enterprise. However, for some situations, including
 legacy workflows, the Web UI or API will work well.
 
-All three options require you [sign up for Vagrant Enterprise](/account/new).
+All three options require you [sign up for Vagrant Enterprise](https://vagrantcloud.com/account/new).
 
 ## Creating Boxes with Packer
 
@@ -34,7 +34,7 @@ or with Packer locally.
 
 After you've created the `.box` file, this guide can be followed.
 
-1. Go to the [Create Box](/boxes/new) page.
+1. Go to the [Create Box](https://vagrantcloud.com/boxes/new) page.
 
 1. Name the box and give it a simple description
 
@@ -47,21 +47,21 @@ locally in Vagrant. `virtualbox` is the most common provider.
 1. Upload the `.box` file for each provider, or use a url to the `.box`
 file that is publicly accessible
 
-You can find all of your boxes in the [Vagrant section](/vagrant) of Vagrant Enterprise.
+You can find all of your boxes in the [Vagrant section](https://vagrantcloud.com/vagrant) of Vagrant Enterprise.
 
 Once you've created and released a box, you can release new versions of
 the box by clicking "Create New Version" under the versions sidebar on
 a box page. For more information on the release lifecycle of boxes, see
-the [help page dedicated to box lifecycle](/help/boxes/lifecycle).
+the [help page dedicated to box lifecycle](/docs/vagrant-cloud/boxes/lifecycle.html).
 
 ## Creating Boxes with the API
 
-This example uses the [Boxes API](/docs) to upload boxes with `curl`. To
-get started, you'll need to get an [access token](/settings/tokens).
+This example uses the API to upload boxes with `curl`. To get started, you'll
+need to get an [access token](https://vagrantcloud.com/settings/tokens).
 
 Then, prepare the upload:
 
-    $ curl 'https://atlas.hashicorp.com/api/v1/box/USERNAME/BOX_NAME/version/VERSION/provider/PROVIDER_NAME/upload?access_token=ACCESS_TOKEN'
+    $ curl 'https://vagrantcloud.com/api/v1/box/USERNAME/BOX_NAME/version/VERSION/provider/PROVIDER_NAME/upload?access_token=ACCESS_TOKEN'
 
 This should return something like this:
 
@@ -75,6 +75,6 @@ Then, upload your box with the following command, with the filename in this case
 
 When the upload finishes, you can verify it worked by making this request and matching the `hosted_token` it returns to the previously retrieved upload token.
 
-    $ curl 'https://atlas.hashicorp.com/api/v1/box/USERNAME/BOX_NAME/version/VERSION_NUMBER/provider/PROVIDER_NAME?access_token=ACCESS_TOKEN'
+    $ curl 'https://vagrantcloud.com/api/v1/box/USERNAME/BOX_NAME/version/VERSION_NUMBER/provider/PROVIDER_NAME?access_token=ACCESS_TOKEN'
 
 Your box should then be available for download.

website/source/docs/vagrant-cloud/boxes/distributing.html.md

@@ -10,14 +10,14 @@ To distribute the box to your team, update your Vagrantfile to reference the
 box on Vagrant Enterprise.
 
     Vagrant.configure(2) do |config|
-      config.vm.box = "ATLAS_USERNAME_HERE/example-box"
+      config.vm.box = "username/example-box"
     end
 
 Now when a team member runs `vagrant up`, the box will be downloaded from Vagrant Enterprise.
 If the box is private, the team member will be prompted to authorize access. Users
 are granted access to private resources by logging in with a Vagrant Enterprise username and
 password or by using a shared Vagrant Enterprise token.
-[Learn more about authorization options here](/help/user-accounts/authentication).
+[Learn more about authorization options here](/docs/vagrant-cloud/users/authentication.html).
 
 ## Private Boxes
 
@@ -45,7 +45,7 @@ and if necessary a collaborator can be removed
 In order to access these private boxes from Vagrant, you'll need to first
 authenticate with your Vagrant Enterprise account.
 
-1. Run `vagrant login` (with [the latest version of Vagrant](/help/intro/updating-tools))
+1. Run `vagrant login`
 2. Enter your credentials
 
 You should now be logged in. We use these credentials to request

website/source/docs/vagrant-cloud/boxes/release-workflow.html.md

@@ -6,7 +6,7 @@ sidebar_current: "vagrant-cloud-boxes-release-workflow"
 
 # API Release Workflow
 
-Creating new boxes through their [release lifecycle](/help/boxes/lifecycle)
+Creating new boxes through their [release lifecycle](/docs/vagrant-cloud/boxes/lifecycle.html)
 is possible through the Vagrant Enterprise website, but you can also automate
 the task via the Vagrant Enterprise API.
 

website/source/docs/vagrant-cloud/boxes/using.html.md

@@ -10,14 +10,12 @@ A primary use case of Vagrant Enterprise by HashiCorp is to be able to easily fi
 boxes you can use with Vagrant that contain the technologies you need
 for a Vagrant environment. We've made it extremely easy to do that:
 
-1. Go to the [Discover page](/discover)
+1. Go to the [Discover page](https://vagrantcloud.com/discover), and search for
+   any box you want.
 
-2. Search for any box you want, or use the navigation on the left
-   to see [featured](/discover/featured) boxes.
+1. Once you find a box, click its name to learn more about it.
 
-3. Once you find a box, click its name to learn more about it.
-
-4. When you're ready to use it, copy the name, such as "hashicorp/precise64"
+1. When you're ready to use it, copy the name, such as "hashicorp/precise64"
    and initialize your Vagrant project with `vagrant init hashicorp/precise64`.
    Or, if you already have a Vagrant project created, modify the Vagrantfile
    to use the box: `config.vm.box = "hashicorp/precise64"`

website/source/docs/vagrant-cloud/organizations/authentication-policy.html.md

@@ -14,7 +14,7 @@ Enterprise.
 ## Requiring Two-Factor Authentication
 
 Organization owners can require that all organization team members use
-[two-factor authentication](/docs/enterprise/user-accounts/authentication.html).
+[two-factor authentication](/docs/vagrant-cloud/users/authentication.html).
 Those that lack two-factor authentication will be locked out of the web
 interface until they enable it or leave the organization.
 

website/source/docs/vagrant-cloud/users/index.html.md

@@ -7,5 +7,5 @@ sidebar_current: "vagrant-cloud-users"
 # User Accounts
 
 Users are the main identity system in Vagrant Enterprise. A user can be a
-member of multiple [organizations](/docs/enterprise/organizations/index.html),
+member of multiple [organizations](/docs/vagrant-cloud/organizations/index.html),
 as well as individually collaborate on various resources.