Use www. for project sites

website/source/docs/builders/amazon.html.markdown

@@ -49,7 +49,7 @@ Credentials are resolved in the following order:
 1.  Values hard-coded in the packer template are always authoritative.
 2.  *Variables* in the packer template may be resolved from command-line flags
     or from environment variables. Please read about [User
-    Variables](https://packer.io/docs/templates/user-variables.html)
+    Variables](https://www.packer.io/docs/templates/user-variables.html)
     for details.
 3.  If no credentials are found, packer falls back to automatic lookup.
 

website/source/docs/builders/docker.html.markdown

@@ -75,7 +75,7 @@ You must specify (only) one of `commit`, `discard`, or `export_path`.
 
 -   `discard` (boolean) - Throw away the container when the build is complete.
     This is useful for the [artifice
-    post-processor](https://packer.io/docs/post-processors/artifice.html).
+    post-processor](https://www.packer.io/docs/post-processors/artifice.html).
 
 -   `export_path` (string) - The path where the final container will be exported
     as a tar file.

website/source/docs/command-line/push.html.markdown

@@ -26,7 +26,7 @@ both the post-processor and push commands can be used independently.
 scripts, to Atlas. Take care not to upload files that you don't intend to, like
 secrets or large binaries. **If you have secrets in your Packer template, you
 should [move them into environment
-variables](https://packer.io/docs/templates/user-variables.html).**
+variables](https://www.packer.io/docs/templates/user-variables.html).**
 
 Most push behavior is [configured in your packer
 template](/docs/templates/push.html). You can override or supplement your

website/source/docs/post-processors/artifice.html.markdown

@@ -25,9 +25,9 @@ extracting the docker container and throwing away the EC2 instance.
 
 After overriding the artifact with artifice, you can use it with other
 post-processors like
-[compress](https://packer.io/docs/post-processors/compress.html),
-[docker-push](https://packer.io/docs/post-processors/docker-push.html),
-[Atlas](https://packer.io/docs/post-processors/atlas.html), or a third-party
+[compress](https://www.packer.io/docs/post-processors/compress.html),
+[docker-push](https://www.packer.io/docs/post-processors/docker-push.html),
+[Atlas](https://www.packer.io/docs/post-processors/atlas.html), or a third-party
 post-processor.
 
 Artifice allows you to use the familiar packer workflow to create a fresh,
@@ -67,7 +67,7 @@ The configuration allows you to specify which files comprise your artifact.
 This minimal example:
 
 1.  Spins up a cloned VMware virtual machine
-2.  Installs a [consul](https://consul.io/) release
+2.  Installs a [consul](https://www.consul.io/) release
 3.  Downloads the consul binary
 4.  Packages it into a `.tar.gz` file
 5.  Uploads it to Atlas.

website/source/docs/post-processors/atlas.html.markdown

@@ -38,7 +38,7 @@ Here is an example workflow:
     example `hashicorp/foobar`, to create the artifact in Atlas or update the
     version if the artifact already exists
 3.  The new version is ready and available to be used in deployments with a tool
-    like [Terraform](https://terraform.io)
+    like [Terraform](https://www.terraform.io)
 
 ## Configuration
 

website/source/docs/post-processors/vagrant-cloud.html.markdown

@@ -18,7 +18,7 @@ Type: `vagrant-cloud`
 
 The Packer Vagrant Cloud post-processor receives a Vagrant box from the
 `vagrant` post-processor and pushes it to Vagrant Cloud. [Vagrant
-Cloud](https://vagrantcloud.com) hosts and serves boxes to Vagrant, allowing you
+Cloud](https://atlas.hashicorp.com) hosts and serves boxes to Vagrant, allowing you
 to version and distribute boxes to an organization in a simple way.
 
 You'll need to be familiar with Vagrant Cloud, have an upgraded account to

website/source/intro/getting-started/remote-builds.html.markdown

@@ -87,7 +87,7 @@ when you click on the active build, you can view the logs in real-time.
 
 Now we have Atlas building an AMI with Redis pre-configured. This is great, but
 it's even better to store and version the AMI output so it can be easily
-deployed by a tool like [Terraform](https://terraform.io). The `atlas`
+deployed by a tool like [Terraform](https://www.terraform.io). The `atlas`
 [post-processor](/docs/post-processors/atlas.html) makes this process simple:
 
 ``` {.javascript}

website/source/intro/hashicorp-ecosystem.html.markdown

@@ -33,16 +33,16 @@ is HashiCorp's only commercial product. It unites Packer, Terraform, and Consul
 to make application delivery a versioned, auditable, repeatable, and
 collaborative process.
 
-[Packer](https://packer.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
+[Packer](https://www.packer.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
 is a HashiCorp tool for creating machine images and deployable artifacts such as
 AMIs, OpenStack images, Docker containers, etc.
 
-[Terraform](https://terraform.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
+[Terraform](https://www.terraform.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
 is a HashiCorp tool for creating, combining, and modifying infrastructure. In
 the Atlas workflow Terraform reads from the artifact registry and provisions
 infrastructure.
 
-[Consul](https://consul.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
+[Consul](https://www.consul.io/?utm_source=packer&utm_campaign=HashicorpEcosystem)
 is a HashiCorp tool for service discovery, service registry, and health checks.
 In the Atlas workflow Consul is configured at the Packer build stage and
 identifies the service(s) contained in each artifact. Since Consul is configured
@@ -51,7 +51,7 @@ is fully configured with dependencies and service discovery pre-baked. This
 greatly reduces the risk of an unhealthy node in production due to configuration
 failure at runtime.
 
-[Serf](https://serfdom.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) is
+[Serf](https://www.serfdom.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) is
 a HashiCorp tool for cluster membership and failure detection. Consul uses
 Serf's gossip protocol as the foundation for service discovery.