remove trailing spaces

website/source/docs/builders/amazon-ebs.html.md

@@ -237,7 +237,7 @@ builder.
 
 -   `temporary_security_group_source_cidr` (string) - An IPv4 CIDR block to be authorized
     access to the instance, when packer is creating a temporary security group.
-    The default is `0.0.0.0/0` (ie, allow any IPv4 source). This is only used 
+    The default is `0.0.0.0/0` (ie, allow any IPv4 source). This is only used
     when `security_group_id` or `security_group_ids` is not specified.
 
 -   `shutdown_behavior` (string) - Automatically terminate instances on shutdown

website/source/docs/builders/azure.html.md

@@ -134,7 +134,7 @@ When creating a managed image the following two options are required.
     assigned.  Knowing the resource group and VM name allows one to execute commands to update the VM during a Packer
     build, e.g. attach a resource disk to the VM.
 
--   `temp_resource_group_name` (string) name assigned to the temporary resource group created during the build.  If this 
+-   `temp_resource_group_name` (string) name assigned to the temporary resource group created during the build.  If this
     value is not set, a random value will be assigned. This resource group is deleted at the end of the build. Cannot be
     used together with `build_resource_group_name`.
 

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

@@ -212,7 +212,7 @@ You must specify (only) one of `commit`, `discard`, or `export_path`.
 -   `container_dir` (string) - The directory inside container to mount
      temp directory from host server for work [file provisioner](/docs/provisioners/file.html).
      By default this is set to `/packer-files`.
-     
+
 -   `fix_upload_owner` (boolean) - If true, files uploaded to the container will
     be owned by the user the container is running as. If false, the owner will depend
     on the version of docker installed in the system. Defaults to true.

website/source/docs/builders/hyperv-iso.html.md

@@ -54,20 +54,20 @@ can be configured for this builder.
 ### Required:
 
 -   `iso_checksum` (string) - The checksum for the OS ISO file or virtual
-    harddrive file. Because these files are so large, this is required and 
-    Packer will verify it prior to booting a virtual machine with the ISO or 
-    virtual harddrive attached. The type of the checksum is specified with 
+    harddrive file. Because these files are so large, this is required and
+    Packer will verify it prior to booting a virtual machine with the ISO or
+    virtual harddrive attached. The type of the checksum is specified with
     `iso_checksum_type`, documented below.
 
 -   `iso_checksum_type` (string) - The type of the checksum specified in
     `iso_checksum`. Valid values are "none", "md5", "sha1", "sha256", or
     "sha512" currently. While "none" will skip checksumming, this is not
-    recommended since ISO files and virtual harddrive files are	generally large 
+    recommended since ISO files and virtual harddrive files are generally large
     and corruption does happen from time to time.
 
 -   `iso_url` (string) - A URL to the ISO containing the installation image or
     virtual harddrive vhd or vhdx file to clone. This URL can be either an HTTP
-    URL or a file URL (or path to a file). If this is an HTTP URL, Packer will 
+    URL or a file URL (or path to a file). If this is an HTTP URL, Packer will
     download the file and cache it between runs.
 
 ### Optional:

website/source/docs/builders/hyperv-vmcx.html.md

@@ -10,13 +10,13 @@ page_title: "Hyper-V Builder (from an vmcx)"
 
 Type: `hyperv-vmcx`
 
-The Hyper-V Packer builder is able to use exported virtual machines or clone existing 
+The Hyper-V Packer builder is able to use exported virtual machines or clone existing
 [Hyper-V](https://www.microsoft.com/en-us/server-cloud/solutions/virtualization.aspx)
 virtual machines.
 
-The builder imports a virtual machine or clones an existing virtual machine boots it, 
-and provisioning software within the OS, then shutting it down. The result of the 
-Hyper-V builder is a directory containing all the files necessary to run the virtual 
+The builder imports a virtual machine or clones an existing virtual machine boots it,
+and provisioning software within the OS, then shutting it down. The result of the
+Hyper-V builder is a directory containing all the files necessary to run the virtual
 machine portably.
 
 ## Basic Example
@@ -193,7 +193,7 @@ can be configured for this builder.
 *   `secondary_iso_images` (array of strings) - A list of iso paths to attached
     to a VM when it is booted. This is most useful for unattended Windows
     installs, which look for an `Autounattend.xml` file on removable media. By
-    default, no secondary iso will be attached. 
+    default, no secondary iso will be attached.
 
 -   `shutdown_command` (string) - The command to use to gracefully shut down
     the machine once all the provisioning is done. By default this is an empty
@@ -275,7 +275,7 @@ will be replaced by the proper key:
 
 -   `<leftAltOn>` `<rightAltOn>`  - Simulates pressing and holding the alt key.
 
--   `<leftCtrlOn>` `<rightCtrlOn>` - Simulates pressing and holding the ctrl key. 
+-   `<leftCtrlOn>` `<rightCtrlOn>` - Simulates pressing and holding the ctrl key.
 
 -   `<leftShiftOn>` `<rightShiftOn>` - Simulates pressing and holding the shift key.
 
@@ -289,7 +289,7 @@ will be replaced by the proper key:
     sending any additional keys. This is useful if you have to generally wait
     for the UI to update before typing more.
 
-When using modifier keys `ctrl`, `alt`, `shift` ensure that you release them, otherwise they will be held down until the machine reboots. Use lowercase characters as well inside modifiers. For example: to simulate ctrl+c use `<leftCtrlOn>c<leftCtrlOff>`.    
+When using modifier keys `ctrl`, `alt`, `shift` ensure that you release them, otherwise they will be held down until the machine reboots. Use lowercase characters as well inside modifiers. For example: to simulate ctrl+c use `<leftCtrlOn>c<leftCtrlOff>`.
 
 In addition to the special keys, each command to type is treated as a
 [configuration template](/docs/templates/configuration-templates.html).
@@ -324,15 +324,15 @@ for the version of Hyper-V that is running.
 
 ## Generation 1 vs Generation 2
 
-Floppy drives are no longer supported by generation 2 machines. This requires you to 
+Floppy drives are no longer supported by generation 2 machines. This requires you to
 take another approach when dealing with preseed or answer files. Two possible options
 are using virtual dvd drives or using the built in web server.
 
-When dealing with Windows you need to enable UEFI drives for generation 2 virtual machines. 
+When dealing with Windows you need to enable UEFI drives for generation 2 virtual machines.
 
 ## Creating iso from directory
 
-Programs like mkisofs can be used to create an iso from a directory. 
+Programs like mkisofs can be used to create an iso from a directory.
 There is a [windows version of mkisofs](http://opensourcepack.blogspot.co.uk/p/cdrtools.html).
 
 Example powershell script. This is an actually working powershell script used to create a Windows answer iso:
@@ -357,7 +357,7 @@ copy windows\common\win-updates.ps1 $isoFolder\
 copy windows\common\run-sysprep.ps1 $isoFolder\
 copy windows\common\run-sysprep.cmd $isoFolder\
 
-$textFile = "$isoFolder\Autounattend.xml" 
+$textFile = "$isoFolder\Autounattend.xml"
 
 $c = Get-Content -Encoding UTF8 $textFile
 
@@ -399,7 +399,7 @@ Packer config:
     "winrm_username": "vagrant",
     "winrm_password": "vagrant",
     "winrm_timeout" : "4h",
-    "shutdown_command": "f:\\run-sysprep.cmd",  
+    "shutdown_command": "f:\\run-sysprep.cmd",
     "ram_size": 4096,
     "cpu": 4,
     "generation": 2,
@@ -514,10 +514,10 @@ autounattend.xml:
                             <Order>3</Order>
                             <Size>128</Size>
                             <Type>MSR</Type>
-                        </CreatePartition>         
+                        </CreatePartition>
                         <CreatePartition wcm:action="add">
                             <Order>4</Order>
-                            <Extend>true</Extend> 
+                            <Extend>true</Extend>
                             <Type>Primary</Type>
                         </CreatePartition>
                     </CreatePartitions>
@@ -609,8 +609,8 @@ autounattend.xml:
             <POLICYProxySettingsPerUser>0</POLICYProxySettingsPerUser>
             <HKLMProxyEnable>true</HKLMProxyEnable>
             <HKLMProxyServer>cache-proxy:3142</HKLMProxyServer>
-        </component>  
-Finish Setup cache proxy during installation --> 
+        </component>
+Finish Setup cache proxy during installation -->
         <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <AutoLogon>
                 <Password>
@@ -842,13 +842,13 @@ sysprep-unattend.xml:
         </component>
     </settings>
     <settings pass="oobeSystem">
-<!-- Setup proxy after sysprep 
+<!-- Setup proxy after sysprep
        <component name="Microsoft-Windows-IE-ClientNetworkProtocolImplementation" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <POLICYProxySettingsPerUser>1</POLICYProxySettingsPerUser>
             <HKLMProxyEnable>false</HKLMProxyEnable>
             <HKLMProxyServer>cache-proxy:3142</HKLMProxyServer>
         </component>
-Finish proxy after sysprep -->  
+Finish proxy after sysprep -->
         <component language="neutral" name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
             <InputLocale>0809:00000809</InputLocale>
             <SystemLocale>en-GB</SystemLocale>

website/source/docs/builders/hyperv.html.md

@@ -18,6 +18,6 @@ virtual machines and export them.
     an image. This is best for people who want to start from scratch.
 
 -   [hyperv-vmcx](/docs/builders/hyperv-vmcx.html) - Clones an
-    an existing virtual machine, provisions software within the OS, 
-    then exports that machine to create an image. This is best for 
+    an existing virtual machine, provisions software within the OS,
+    then exports that machine to create an image. This is best for
     people who have existing base images and want to customize them.

website/source/docs/post-processors/vsphere-template.html.md

@@ -1,7 +1,7 @@
 ---
 description: |
     The Packer vSphere Template post-processor takes an artifact from the VMware-iso builder built on ESXi (i.e. remote)
-    and allows to mark a VM as a template and leaving it in a path of choice. 
+    and allows to mark a VM as a template and leaving it in a path of choice.
 layout: docs
 page_title: 'vSphere Template - Post-Processors'
 sidebar_current: 'docs-post-processors-vSphere-template'
@@ -19,14 +19,14 @@ allows to mark a VM as a template and leaving it in a path of choice.
 An example is shown below, showing only the post-processor configuration:
 
 ``` json
-{  
+{
    "type": "vsphere-template",
    "host": "vcenter.local",
    "insecure": true,
    "username": "root",
-   "password": "secret",      
+   "password": "secret",
    "datacenter": "mydatacenter",
-   "folder": "/packer-templates/os/distro-7"   
+   "folder": "/packer-templates/os/distro-7"
 }
 ```
 
@@ -38,7 +38,7 @@ each category, the available configuration keys are alphabetized.
 
 Required:
 
--   `host` (string) - The vSphere host that contains the VM built by the vmware-iso. 
+-   `host` (string) - The vSphere host that contains the VM built by the vmware-iso.
 
 -   `password` (string) - Password to use to authenticate to the vSphere endpoint.
 
@@ -48,6 +48,6 @@ Optional:
 
 -   `datacenter` (string) - If you have more than one, you will need to specify which one the ESXi used.
 
--   `folder` (string) - Target path where the template will be created. 
+-   `folder` (string) - Target path where the template will be created.
 
--   `insecure` (boolean) - If it's true skip verification of server certificate. Default is false  
+-   `insecure` (boolean) - If it's true skip verification of server certificate. Default is false

website/source/docs/provisioners/ansible-local.html.md

@@ -1,10 +1,10 @@
 ---
 description: |
-    The ansible-local Packer provisioner will run ansible in ansible's "local" 
-    mode on the remote/guest VM using Playbook and Role files that exist on the 
-    guest VM. This means ansible must be installed on the remote/guest VM. 
-    Playbooks and Roles can be uploaded from your build machine 
-    (the one running Packer) to the vm. 
+    The ansible-local Packer provisioner will run ansible in ansible's "local"
+    mode on the remote/guest VM using Playbook and Role files that exist on the
+    guest VM. This means ansible must be installed on the remote/guest VM.
+    Playbooks and Roles can be uploaded from your build machine
+    (the one running Packer) to the vm.
 layout: docs
 page_title: 'Ansible Local - Provisioners'
 sidebar_current: 'docs-provisioners-ansible-local'
@@ -14,11 +14,11 @@ sidebar_current: 'docs-provisioners-ansible-local'
 
 Type: `ansible-local`
 
-The `ansible-local` Packer provisioner will run ansible in ansible's "local" 
-    mode on the remote/guest VM using Playbook and Role files that exist on the 
-    guest VM. This means ansible must be installed on the remote/guest VM. 
-    Playbooks and Roles can be uploaded from your build machine 
-    (the one running Packer) to the vm. Ansible is then run on the guest machine 
+The `ansible-local` Packer provisioner will run ansible in ansible's "local"
+    mode on the remote/guest VM using Playbook and Role files that exist on the
+    guest VM. This means ansible must be installed on the remote/guest VM.
+    Playbooks and Roles can be uploaded from your build machine
+    (the one running Packer) to the vm. Ansible is then run on the guest machine
     in [local mode](https://docs.ansible.com/ansible/playbooks_delegation.html#local-playbooks) via the
 `ansible-playbook` command.
 
@@ -118,7 +118,7 @@ chi-appservers
     cli](http://docs.ansible.com/ansible/galaxy.html#the-ansible-galaxy-command-line-tool)
     on the remote machine. By default, this is empty.
 
--   `galaxycommand` (string) - The command to invoke ansible-galaxy. 
+-   `galaxycommand` (string) - The command to invoke ansible-galaxy.
     By default, this is ansible-galaxy.
 
 -   `group_vars` (string) - a path to the directory containing ansible group

website/source/docs/provisioners/ansible.html.md

@@ -250,7 +250,7 @@ SSH servers only allow you to attempt to authenticate a certain number of times.
     googlecompute: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '[127.0.0.1]:62684' (RSA) to the list of known hosts.\r\nReceived disconnect from 127.0.0.1 port 62684:2: too many authentication failures\r\nAuthentication failed.\r\n", "unreachable": true}
 ```
 
-To unload all keys from your `ssh-agent`, run: 
+To unload all keys from your `ssh-agent`, run:
 
 ```console
 $ ssh-add -D

website/source/docs/provisioners/shell-local.html.md

@@ -1,8 +1,8 @@
 ---
 description: |
-    shell-local will run a shell script of your choosing on the machine where Packer 
-    is being run - in other words, it shell-local will run the shell script on your 
-    build server, or your desktop, etc., rather than the remote/guest machine being 
+    shell-local will run a shell script of your choosing on the machine where Packer
+    is being run - in other words, it shell-local will run the shell script on your
+    build server, or your desktop, etc., rather than the remote/guest machine being
     provisioned by Packer.
 layout: docs
 page_title: 'Shell (Local) - Provisioners'
@@ -13,9 +13,9 @@ sidebar_current: 'docs-provisioners-shell-local'
 
 Type: `shell-local`
 
-shell-local will run a shell script of your choosing on the machine where Packer 
-is being run - in other words, it shell-local will run the shell script on your 
-build server, or your desktop, etc., rather than the remote/guest machine being 
+shell-local will run a shell script of your choosing on the machine where Packer
+is being run - in other words, it shell-local will run the shell script on your
+build server, or your desktop, etc., rather than the remote/guest machine being
 provisioned by Packer.
 
 The [remote shell](/docs/provisioners/shell.html) provisioner executes