Ross Smith maintains our VMware builder on Windows, and provides other valuable assistance. -Ross is an open source enthusist, published author, and freelance consultant.
+Ross is an open source enthusiast, published author, and freelance consultant. diff --git a/website/source/docs/builders/amazon-ebs.html.markdown b/website/source/docs/builders/amazon-ebs.html.markdown index 9383592fc..c6415432b 100644 --- a/website/source/docs/builders/amazon-ebs.html.markdown +++ b/website/source/docs/builders/amazon-ebs.html.markdown @@ -2,7 +2,7 @@ layout: "docs" page_title: "Amazon AMI Builder (EBS backed)" description: |- - The `amazon-ebs` Packer builder is able to create Amazon AMIs backed by EBS volumes for use in EC2. For more information on the difference betwen EBS-backed instances and instance-store backed instances, see the storage for the root device section in the EC2 documentation. + The `amazon-ebs` Packer builder is able to create Amazon AMIs backed by EBS volumes for use in EC2. For more information on the difference between EBS-backed instances and instance-store backed instances, see the storage for the root device section in the EC2 documentation. --- # AMI Builder (EBS backed) @@ -11,7 +11,7 @@ Type: `amazon-ebs` The `amazon-ebs` Packer builder is able to create Amazon AMIs backed by EBS volumes for use in [EC2](http://aws.amazon.com/ec2/). For more information -on the difference betwen EBS-backed instances and instance-store backed +on the difference between EBS-backed instances and instance-store backed instances, see the ["storage for the root device" section in the EC2 documentation](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ComponentsAMIs.html#storage-for-the-root-device). diff --git a/website/source/docs/builders/googlecompute.markdown b/website/source/docs/builders/googlecompute.markdown index fd3ed2558..097e69268 100644 --- a/website/source/docs/builders/googlecompute.markdown +++ b/website/source/docs/builders/googlecompute.markdown @@ -26,7 +26,7 @@ instance to use a [Compute Engine Service Account](https://cloud.google.com/comp to Google Cloud without having to bake in a separate credential/authentication file. To create a GCE instance that uses a service account, provide the required scopes when -launching the intance. +launching the instance. For `gcloud`, do this via the `--scopes` parameter: diff --git a/website/source/docs/builders/parallels-iso.html.markdown b/website/source/docs/builders/parallels-iso.html.markdown index 3d8bbaddc..3d13acae3 100644 --- a/website/source/docs/builders/parallels-iso.html.markdown +++ b/website/source/docs/builders/parallels-iso.html.markdown @@ -73,7 +73,7 @@ each category, the available options are alphabetized and described. * `parallels_tools_flavor` (string) - The flavor of the Parallels Tools ISO to install into the VM. Valid values are "win", "lin", "mac", "os2" and "other". - This can be ommited only if `parallels_tools_mode` is "disable". + This can be omitted only if `parallels_tools_mode` is "disable". ### Optional: diff --git a/website/source/docs/builders/parallels-pvm.html.markdown b/website/source/docs/builders/parallels-pvm.html.markdown index 5bd1c92cf..9243d1f10 100644 --- a/website/source/docs/builders/parallels-pvm.html.markdown +++ b/website/source/docs/builders/parallels-pvm.html.markdown @@ -56,7 +56,7 @@ each category, the available options are alphabetized and described. * `parallels_tools_flavor` (string) - The flavor of the Parallels Tools ISO to install into the VM. Valid values are "win", "lin", "mac", "os2" and "other". - This can be ommited only if `parallels_tools_mode` is "disable". + This can be omitted only if `parallels_tools_mode` is "disable". ### Optional: diff --git a/website/source/docs/builders/qemu.html.markdown b/website/source/docs/builders/qemu.html.markdown index 34e86f20d..5aa0cf152 100644 --- a/website/source/docs/builders/qemu.html.markdown +++ b/website/source/docs/builders/qemu.html.markdown @@ -185,7 +185,7 @@ each category, the available options are alphabetized and described. the qemu command line (though not, at this time, qemu-img). Each array of strings makes up a command line switch that overrides matching default switch/value pairs. Any value specified as an empty string is ignored. - All values after the switch are concatenated with no separater. + All values after the switch are concatenated with no separator. ~> **Warning:** The qemu command line allows extreme flexibility, so beware of conflicting arguments causing failures of your run. For instance, using diff --git a/website/source/docs/builders/vmware-iso.html.markdown b/website/source/docs/builders/vmware-iso.html.markdown index 7da76aa1d..aba8dd902 100644 --- a/website/source/docs/builders/vmware-iso.html.markdown +++ b/website/source/docs/builders/vmware-iso.html.markdown @@ -73,7 +73,7 @@ each category, the available options are alphabetized and described. ### Optional: * `boot_command` (array of strings) - This is an array of commands to type - when the virtual machine is firsted booted. The goal of these commands should + when the virtual machine is first booted. The goal of these commands should be to type just enough to initialize the operating system installer. Special keys can be typed as well, and are covered in the section below on the boot command. If this is not specified, it is assumed the installer will start diff --git a/website/source/docs/builders/vmware-vmx.html.markdown b/website/source/docs/builders/vmware-vmx.html.markdown index 5cf752459..399bab8a9 100644 --- a/website/source/docs/builders/vmware-vmx.html.markdown +++ b/website/source/docs/builders/vmware-vmx.html.markdown @@ -54,7 +54,7 @@ each category, the available options are alphabetized and described. ### Optional: * `boot_command` (array of strings) - This is an array of commands to type - when the virtual machine is firsted booted. The goal of these commands should + when the virtual machine is first booted. The goal of these commands should be to type just enough to initialize the operating system installer. Special keys can be typed as well, and are covered in the section below on the boot command. If this is not specified, it is assumed the installer will start diff --git a/website/source/docs/extend/command.html.markdown b/website/source/docs/extend/command.html.markdown index d36a9087d..1a4625c9b 100644 --- a/website/source/docs/extend/command.html.markdown +++ b/website/source/docs/extend/command.html.markdown @@ -73,7 +73,7 @@ passed directly into something like the standard Go `flag` package for command-line flag parsing. The return value of `Run` is the exit status for the command. If everything -ran successfully, this should be 0. If any errors occured, it should be any +ran successfully, this should be 0. If any errors occurred, it should be any positive integer. ### The "Synopsis" Method diff --git a/website/source/docs/extend/developing-plugins.html.markdown b/website/source/docs/extend/developing-plugins.html.markdown index d67470930..4e38c27a3 100644 --- a/website/source/docs/extend/developing-plugins.html.markdown +++ b/website/source/docs/extend/developing-plugins.html.markdown @@ -34,7 +34,7 @@ uses, because they're completely isolated into the process space of the plugin itself. And, thanks to Go's [interfaces](http://golang.org/doc/effective_go.html#interfaces_and_types), -it doesn't even look like inter-process communication is occuring. You just +it doesn't even look like inter-process communication is occurring. You just use the interfaces like normal, but in fact they're being executed in a remote process. Pretty cool. @@ -93,7 +93,7 @@ in the relevant subsections available in the navigation to the left. ~> **Lock your dependencies!** Unfortunately, Go's dependency management story is fairly sad. There are various unofficial methods out -there for locking dependencies, and using one of them is highly recomended +there for locking dependencies, and using one of them is highly recommended since the Packer codebase will continue to improve, potentially breaking APIs along the way until there is a stable release. By locking your dependencies, your plugins will continue to work with the version of Packer you lock to. diff --git a/website/source/docs/machine-readable/command-build.html.markdown b/website/source/docs/machine-readable/command-build.html.markdown index 836a61ef2..3320f43f1 100644 --- a/website/source/docs/machine-readable/command-build.html.markdown +++ b/website/source/docs/machine-readable/command-build.html.markdown @@ -14,7 +14,7 @@ of `packer build`.- Information about an artifact of the targetted item. This is a + Information about an artifact of the targeted item. This is a fairly complex (but uniform!) machine-readable type that contains subtypes. The subtypes are documented within this page in the syntax of "artifact subtype: SUBTYPE". The number of arguments within @@ -119,7 +119,7 @@ of `packer build`.
- If present, this means that the artifact was nil, or that the targetted + If present, this means that the artifact was nil, or that the targeted build completed successfully but no artifact was created.