From 81cf23052ff2833e1d47f51cf44d096a3eaba9a6 Mon Sep 17 00:00:00 2001 From: Dave Holland Date: Thu, 10 Mar 2016 17:24:40 +0000 Subject: [PATCH] Update setup.html.markdown zip file now contains a single binary --- website/source/intro/getting-started/setup.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/intro/getting-started/setup.html.markdown b/website/source/intro/getting-started/setup.html.markdown index eed91c97a..623a0e0b0 100644 --- a/website/source/intro/getting-started/setup.html.markdown +++ b/website/source/intro/getting-started/setup.html.markdown @@ -31,8 +31,8 @@ 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. On Windows systems, you can put it wherever you'd like. -After unzipping the package, the directory should contain a set of binary -programs, such as `packer`, `packer-build-amazon-ebs`, etc. The final step to +After unzipping the package, the directory should contain a single binary +program called `packer`. The final step to installation is to make sure the directory you installed Packer to is on the PATH. See [this page](https://stackoverflow.com/questions/14637979/how-to-permanently-set-path-on-linux)