website: Replace Atlas with Vagrant Enterprise

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

@@ -6,11 +6,11 @@ sidebar_current: "vagrant-cloud-boxes-catalog"
 
 # Discovering Vagrant Boxes
 
-Atlas serves a public, searchable index of Vagrant boxes. It's easy to find
+Vagrant Enterprise serves a public, searchable index of Vagrant boxes. It's easy to find
 boxes you can use with Vagrant that contain the technologies you need
 for a Vagrant environment.
 
-You don't need an Atlas account to use public boxes.
+You don't need a Vagrant Enterprise account to use public boxes.
 
 1. Go to the [Box search page](https://vagrantcloud.com/boxes/search)
 
@@ -37,10 +37,10 @@ are some things to note when you're choosing a box:
 trust the box more than an anonymous user
 - __The number of downloads of the box__. Heavily downloaded boxes
 are likely vetted more often by other members of the community. Hashicorp
-responds to reports of malicious software distributed via Atlas
+responds to reports of malicious software distributed via Vagrant Enterprise
 and takes down boxes
 - __The latest release date__. More up-to-date boxes contain up-to-date
 software
-- __Availability of the box download__. Atlas periodically checks if box
+- __Availability of the box download__. Vagrant Enterprise periodically checks if box
 has is publicly accessible. You can see this information on the box
 page next to the provider

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

@@ -6,27 +6,27 @@ sidebar_current: "vagrant-cloud-boxes-create-x"
 
 # Creating a New Vagrant Box
 
-This page will cover creating a new box in Atlas and how to distribute
-it to users. Boxes can be distributed without Atlas, but
+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).
 
-There are __three ways to create and upload Vagrant Boxes to Atlas__. All
+There are __three ways to create and upload Vagrant Boxes to Vagrant Enterprise__. All
 three options are outlined below.
 
 We recommend using Packer, as is it is fully repeatable and keeps a strong
-history of changes within Atlas. However, for some situations, including
+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 Atlas](/account/new).
+All three options require you [sign up for Vagrant Enterprise](/account/new).
 
 ## Creating Boxes with Packer
 
 Using Packer requires more up front effort, but the repeatable and
 automated builds will end any manual management of boxes. Additionally,
-all boxes will be stored and served from Atlas, keeping a history along
+all boxes will be stored and served from Vagrant Enterprise, keeping a history along
  the way.
 
-## Creating Boxes via the Atlas Web Interface
+## Creating Boxes via the Vagrant Enterprise Web Interface
 
 You'll first need to create a box file. This can be done via
 the [vagrant `package` command](http://docs.vagrantup.com/v2/boxes/base.html)
@@ -47,7 +47,7 @@ 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 Atlas.
+You can find all of your boxes in the [Vagrant section](/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

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

@@ -7,16 +7,16 @@ sidebar_current: "vagrant-cloud-boxes-distributing"
 ## Distributing Boxes
 
 To distribute the box to your team, update your Vagrantfile to reference the
-box on Atlas.
+box on Vagrant Enterprise.
 
     Vagrant.configure(2) do |config|
       config.vm.box = "ATLAS_USERNAME_HERE/example-box"
     end
 
-Now when a team member runs `vagrant up`, the box will be downloaded from Atlas.
+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 an Atlas username and
-password or by using a shared Atlas token.
+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).
 
 ## Private Boxes
@@ -43,7 +43,7 @@ and if necessary a collaborator can be removed
 ### Vagrant Login
 
 In order to access these private boxes from Vagrant, you'll need to first
-authenticate with your Atlas account.
+authenticate with your Vagrant Enterprise account.
 
 1. Run `vagrant login` (with [the latest version of Vagrant](/help/intro/updating-tools))
 2. Enter your credentials

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

@@ -16,14 +16,14 @@ Boxes support versioning so that members of your team using Vagrant can update
 the underlying box easily, and the people who create boxes can push fixes and
 communicate these fixes efficiently.
 
-Atlas makes it easy to manage the versioning of boxes.  Versioning boxes in
-Atlas allows for easy updates, transparent fixes, and clear communication in
+Vagrant Enterprise makes it easy to manage the versioning of boxes.  Versioning boxes in
+Vagrant Enterprise allows for easy updates, transparent fixes, and clear communication in
 changes made. Learn more about the [box release lifecycle
 here](/docs/vagrant-cloud/boxes/lifecycle.html).
 
 ## Vagrant Box Catalog and Discovery
 
-Atlas hosts a catalog of publically available Vagrant Boxes. These are boxes
+Vagrant Enterprise hosts a catalog of publically available Vagrant Boxes. These are boxes
 created by both HashiCorp and community contributions. You can find an owner of
 a box by selecting their username in the URL or on the box page.
 

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

@@ -30,7 +30,7 @@ user will see the following message in Vagrant:
 
 ## Box Version Release States
 
-Atlas lets you create new versions of boxes without
+Vagrant Enterprise lets you create new versions of boxes without
 releasing them or without Vagrant seeing the update. This lets you prepare
 a box for release slowly. Box versions have three states:
 

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

@@ -28,7 +28,7 @@ things they cannot do are:
 ## Vagrant Login
 
 In order to access these boxes from Vagrant, you'll need to first
-authenticate with your Atlas account.
+authenticate with your Vagrant Enterprise account.
 
 1. Run `vagrant login`
 2. Enter your credentials

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

@@ -7,8 +7,8 @@ sidebar_current: "vagrant-cloud-boxes-release-workflow"
 # API Release Workflow
 
 Creating new boxes through their [release lifecycle](/help/boxes/lifecycle)
-is possible through the Atlas website, but you can also automate
-the task via the Atlas API.
+is possible through the Vagrant Enterprise website, but you can also automate
+the task via the Vagrant Enterprise API.
 
 1. Create box, or locate a boxes `tag`, like `hashicorp/precise64`
 2. After some event, like the end of a CI build, you may want to

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

@@ -6,7 +6,7 @@ sidebar_current: "vagrant-cloud-boxes-using"
 
 # Finding and Using Boxes
 
-A primary use case of Atlas by HashiCorp is to be able to easily find
+A primary use case of Vagrant Enterprise by HashiCorp is to be able to easily find
 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: