Apply suggestions from code review

Co-authored-by: Anthony <russo555@gmail.com>
This commit is contained in:
kaitlincart 2022-11-16 09:23:12 -08:00 committed by GitHub
parent ef0bd8b583
commit c88c142b15
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions

View File

@ -8,7 +8,7 @@ description: |-
# Install Vagrant from source
Vagrant installations from source is an advanced operation. It is only recommended
Vagrant installations from source is an advanced operation. We only recommended
if you cannot use the official installer. This page details the prerequisites and three
steps to install Vagrant from source.
@ -70,7 +70,7 @@ the full path to the `exec/vagrant` anywhere on your operating system.
$ /path/to/vagrant/exec/vagrant init -m hashicorp/bionic64
```
-> **Tip:** Warning messages are expected when you use a local Vagrant from source installation, since it is not supported or recommend.
-> **Tip:** Warning messages are expected when you use a local Vagrant from source installation, since it is not supported or recommended.
If you do not want to specify the full path to Vagrant (i.e. you just want to
run `vagrant`), you can create a symbolic link to your exec.

View File

@ -47,7 +47,7 @@ The removal of user data will remove all [boxes](/docs/boxes),
by Vagrant. Removing the user data effectively makes Vagrant think it
is a fresh install.
On all platforms, the user data directory location is in the root of your home directory under `vagrant.d`. Remove the `~/.vagrant.d` directory to delete all the user data. On
On Linux and Mac OS platforms, the user data directory location is in the root of your home directory under `vagrant.d`. Remove the `~/.vagrant.d` directory to delete all the user data. On
Windows, this directory is, `C:\Users\YourUsername\.vagrant.d`, where
`YourUsername` is the username of your local user.

View File

@ -19,7 +19,7 @@ install it with standard procedures for your operating system.
As the [backwards compatibility](/docs/installation/backwards-compatibility)
page says, **Vagrant 1.0.x plugins will not work with Vagrant 1.1+**. Many
of these plugins have been updated to work with newer versions of Vagrant,
you will need to verify if they've been updated. If not however, you will have
so you will need to verify if they've been updated. If not however, you will have
to remove them before the upgrade.
We recommend that you remove _all_ plugins before the upgrade and then slowly