beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Anthony <russo555@gmail.com>
This commit is contained in:
kaitlincart 2022-10-12 08:57:58 -07:00 committed by GitHub
parent 35bd397982
commit 306e0de171
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/installation/source.mdx
View File

@ -22,7 +22,7 @@ You must install Ruby 2.2 or newer to develop and build Vagrant. The
specific Ruby version that you will need is documented in `vagrant.gemspec`, located in the repository on GitHub. It contains the most
up-to-date requirements.
~> Note that it is not recommended that you use the system Ruby. You need a Ruby version manager like RVM or chruby.
~> **Note:** It is not recommended that you use the system Ruby. You need a Ruby version manager like RVM or chruby.
You will also need to be aware of plugin compatibility between Vagrant source installations and package based installations. Since Vagrant plugins are configured based on the current environment, plugins installed with Vagrant from source will not work with the package based Vagrant installation.
@ -34,7 +34,7 @@ Clone Vagrant's repository from GitHub into the directory where you keep code on
$ git clone https://github.com/hashicorp/vagrant.git
```
Next, `cd` into that path. All commands need to be initiated from this directory.
Next, `cd` into that path. You must initiate all commands from this directory.
```shell-session
$ cd /path/to/your/vagrant/clone
@ -69,7 +69,7 @@ the full path to the `exec/vagrant` anywhere on your operating system.
$ /path/to/vagrant/exec/vagrant init -m hashicorp/bionic64
```
~> 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 recommend.
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.

4
website/content/docs/installation/uninstallation.mdx
View File

@ -20,7 +20,7 @@ dependencies from your machine. It will _not_ remove user data. The next section
### Windows machines
Uninstall using the "add/remove programs" section of the control panel.
Uninstall using the **Add/Remove Programs** section of the control panel.
### Mac OS X machines
@ -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, `vagrant.d`. Remove the `~/.vagrant.d` directory to delete all the user data. If on
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
Windows, this directory is, `C:\Users\YourUsername\.vagrant.d`, where
`YourUsername` is the username of your local user.

4
website/content/docs/installation/upgrading-from-1-0.mdx
View File

@ -4,7 +4,7 @@ page_title: Upgrade from Vagrant 1.0
description: |-
The upgrade process from 1.0.x to 1.x is straightforward, Vagrant is
backwards compatible with Vagrant 1.0.x. To reinstall Vagrant
over your previous installation download the latest package and
over your previous installation, download the latest package and
install it with standard procedures for your operating system.
---
@ -13,7 +13,7 @@ description: |-
The upgrade process from 1.0.x to 1.x is straightforward, Vagrant is
[backwards compatible](/docs/installation/backwards-compatibility)
with Vagrant 1.0.x. To reinstall Vagrant
over your previous installation download the latest package and
over your previous installation, download the latest package and
install it with standard procedures for your operating system.
As the [backwards compatibility](/docs/installation/backwards-compatibility)