From 16b907eed9f6386e68e06e7cf3abfb1c03f6fe9c Mon Sep 17 00:00:00 2001 From: sophia Date: Tue, 27 Jul 2021 11:51:52 -0500 Subject: [PATCH] Grammatical fixes --- website/content/intro/index.mdx | 2 +- website/content/intro/vs/cli-tools.mdx | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/website/content/intro/index.mdx b/website/content/intro/index.mdx index f1e8e6311..f4a66d02d 100644 --- a/website/content/intro/index.mdx +++ b/website/content/intro/index.mdx @@ -30,7 +30,7 @@ To achieve its magic, Vagrant stands on the shoulders of giants. Machines are provisioned on top of VirtualBox, VMware, AWS, or [any other provider](/docs/providers/). Then, industry-standard [provisioning tools](/docs/provisioning/) -such as shell scripts, Chef, or Puppet, can automatically install +such as shell scripts, Chef, or Puppet can automatically install and configure software on the virtual machine. ### For Developers diff --git a/website/content/intro/vs/cli-tools.mdx b/website/content/intro/vs/cli-tools.mdx index 50f762b8d..f38b0b3fb 100644 --- a/website/content/intro/vs/cli-tools.mdx +++ b/website/content/intro/vs/cli-tools.mdx @@ -2,7 +2,7 @@ layout: intro page_title: Vagrant vs. CLI Tools description: |- - Virtualization software like VirtualBox and VMware come with command line + Virtualization software like VirtualBox and VMware comes with command line utilities for managing the lifecycle of machines on their platform. Vagrant actually uses many of these utilities internally. The difference between these CLI tools and Vagrant is that Vagrant provides a declarative, reproducible, @@ -19,19 +19,19 @@ actually uses many of these utilities internally. The difference between these CLI tools and Vagrant is that Vagrant builds on top of these utilities in a number of ways while still providing a consistent workflow. Vagrant supports multiple synced folder types, multiple -provisioners to setup the machine, automatic SSH setup, creating HTTP tunnels -into your development environment, and more. All of these can be configured +provisioners to set up the machine, automatic SSH setup, creating HTTP tunnels +into your development environment and more. All of these can be configured using a single simple configuration file. Vagrant still has a number of improvements over manual scripting even if you -ignore all the higher-level features Vagrant provides. The command-line +ignore all the higher-level features Vagrant provides. The command line utilities provided by virtualization software often change each version or have subtle bugs with workarounds. Vagrant automatically detects the version, uses the correct flags, and can work around known issues. So if you're using one version of VirtualBox and a co-worker is using a different version, Vagrant will still work consistently. -For highly-specific workflows that don't change often, it can still be +For highly specific workflows that don't change often, it can still be beneficial to maintain custom scripts. Vagrant is targeted at building development environments but some advanced users still use the CLI tools underneath to do other manual things.