From 9eccbb4cfe28a1031c68f8ea8368f049f4225890 Mon Sep 17 00:00:00 2001 From: Wilken Rivera Date: Tue, 14 Apr 2020 06:46:29 -0400 Subject: [PATCH] docs/getting-started: Update PATH install instructions --- website/pages/intro/getting-started/index.mdx | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/website/pages/intro/getting-started/index.mdx b/website/pages/intro/getting-started/index.mdx index c04227f1c..e9390f661 100644 --- a/website/pages/intro/getting-started/index.mdx +++ b/website/pages/intro/getting-started/index.mdx @@ -32,11 +32,10 @@ have any near term plans to provide system packages. Next, unzip the downloaded package into a directory where Packer will be installed. On Unix systems, `~/packer` or `/usr/local/packer` is generally good, depending on whether you want to restrict the install to just your user or -install it system-wide. If you intend to access it from the command-line, make -sure to place it somewhere on your `PATH` before `/usr/sbin`. On Windows -systems, you can put it wherever you'd like. The `packer` (or `packer.exe` for -Windows) binary inside is all that is necessary to run Packer. Any additional -files aren't required to run Packer. +install it system-wide. If you intend to access Packer from the command-line, make +sure to place it somewhere on your `PATH`. On Windows systems, you can install +the binary wherever you'd like. The single `packer` (or `packer.exe` for +Windows) binary contains all that is necessary to run Packer. After unzipping the package, the directory should contain a single binary program called `packer`. The final step to