docs: fix typos and grammer (#667)

tenthirtyam · web-flow · commit 94d217c3f341 · 2026-02-23T22:02:37.000-05:00
Addressed spelling, grammar, and phrasing.

Signed-off-by: Ryan Johnson &lt;ryan.johnson@broadcom.com&gt;
diff --git a/.web-docs/components/builder/vsphere-clone/README.md b/.web-docs/components/builder/vsphere-clone/README.md
@@ -291,7 +291,7 @@ JSON Example:
 
 <!-- Code generated from the comments of the ConfigParamsConfig struct in builder/vsphere/common/step_config_params.go; DO NOT EDIT MANUALLY -->
 
-- `configuration_parameters` (map[string]string) - A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+- `configuration_parameters` (map[string]string) - A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
   in the vSphere API's `VirtualMachineConfigSpec`.
   
   HCL Example:
@@ -315,7 +315,7 @@ JSON Example:
   ```
   
   ~> **Note:** Configuration keys that would conflict with parameters that
-  are explicitly configurable through other fields in the `ConfigSpec`` object
+  are explicitly configurable through other fields in the `ConfigSpec` object
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
@@ -909,10 +909,10 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 - `floppy_dirs` ([]string) - A list of directories to copy files from.
 
 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
-  the values contents. It can be used alongside `floppy_files` or
+  the value contents. It can be used alongside `floppy_files` or
   `floppy_dirs`, which is useful to add large files without loading them
-  into memory. If any paths are specified by both, the contents in
-  `floppy_content` will take precedence.
+  into memory. If both specify a path, the contents in `floppy_content` will take
+  precedence.
   
   HCL Example:
   
@@ -924,8 +924,8 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
   ```
 
 - `floppy_label` (string) - The label to use for the floppy disk that is attached when the virtual
-  machine is booted. This is most useful for cloud-init, Kickstart or other
-  early initialization tools, which can benefit from labelled floppy disks.
+  machine is booted. This is most useful for cloud-init, Kickstart, or other
+  early initialization tools, which can benefit from labeled floppy disks.
   By default, the floppy label will be 'packer'.
 
 <!-- End of code generated from the comments of the FloppyConfig struct in builder/vsphere/common/step_add_floppy.go; -->
@@ -937,8 +937,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 
diff --git a/.web-docs/components/builder/vsphere-iso/README.md b/.web-docs/components/builder/vsphere-iso/README.md
@@ -107,8 +107,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 
@@ -182,7 +181,7 @@ wget http://{{ .HTTPIP }}:{{ .HTTPPort }}/foo/bar/preseed.cfg
 
 - `convert_to_template` (bool) - Convert the virtual machine to a template after the build is complete.
   Defaults to `false`.
-  If set to `true`, the virtual machine can not be imported into a content library.
+  If set to `true`, the virtual machine cannot be imported into a content library.
 
 - `export` (\*common.ExportConfig) - The configuration for exporting the virtual machine to an OVF.
   The virtual machine is not exported if [export configuration](#export-configuration) is not specified.
@@ -652,10 +651,10 @@ boot time.
 - `floppy_dirs` ([]string) - A list of directories to copy files from.
 
 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
-  the values contents. It can be used alongside `floppy_files` or
+  the value contents. It can be used alongside `floppy_files` or
   `floppy_dirs`, which is useful to add large files without loading them
-  into memory. If any paths are specified by both, the contents in
-  `floppy_content` will take precedence.
+  into memory. If both specify a path, the contents in `floppy_content` will take
+  precedence.
   
   HCL Example:
   
@@ -667,8 +666,8 @@ boot time.
   ```
 
 - `floppy_label` (string) - The label to use for the floppy disk that is attached when the virtual
-  machine is booted. This is most useful for cloud-init, Kickstart or other
-  early initialization tools, which can benefit from labelled floppy disks.
+  machine is booted. This is most useful for cloud-init, Kickstart, or other
+  early initialization tools, which can benefit from labeled floppy disks.
   By default, the floppy label will be 'packer'.
 
 <!-- End of code generated from the comments of the FloppyConfig struct in builder/vsphere/common/step_add_floppy.go; -->
@@ -1617,7 +1616,7 @@ JSON Example:
 
 <!-- Code generated from the comments of the ConfigParamsConfig struct in builder/vsphere/common/step_config_params.go; DO NOT EDIT MANUALLY -->
 
-- `configuration_parameters` (map[string]string) - A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+- `configuration_parameters` (map[string]string) - A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
   in the vSphere API's `VirtualMachineConfigSpec`.
   
   HCL Example:
@@ -1641,7 +1640,7 @@ JSON Example:
   ```
   
   ~> **Note:** Configuration keys that would conflict with parameters that
-  are explicitly configurable through other fields in the `ConfigSpec`` object
+  are explicitly configurable through other fields in the `ConfigSpec` object
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
diff --git a/.web-docs/components/data-source/virtualmachine/README.md b/.web-docs/components/data-source/virtualmachine/README.md
@@ -76,8 +76,7 @@ virtual machine can be used in the vSphere Clone builder to select a template.
 
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 
diff --git a/.web-docs/components/post-processor/vsphere/README.md b/.web-docs/components/post-processor/vsphere/README.md
@@ -85,7 +85,7 @@ The following configuration options are available for the post-processor.
   same as the source virtual machine's.
   
   This option is useful when deploying to vCenter instance or an ESX host whose
-  version is different than the one used to create the artifact.
+  version is different from the one used to create the artifact.
   
   Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)
   for more information on supported virtual hardware versions.
diff --git a/builder/vsphere/common/step_add_floppy.go b/builder/vsphere/common/step_add_floppy.go
@@ -28,10 +28,10 @@ type FloppyConfig struct {
 	// A list of directories to copy files from.
 	FloppyDirectories []string `mapstructure:"floppy_dirs"`
 	// Key/Values to add to the floppy disk. The keys represent the paths, and
-	// the values contents. It can be used alongside `floppy_files` or
+	// the value contents. It can be used alongside `floppy_files` or
 	// `floppy_dirs`, which is useful to add large files without loading them
-	// into memory. If any paths are specified by both, the contents in
-	// `floppy_content` will take precedence.
+	// into memory. If both specify a path, the contents in `floppy_content` will take
+	// precedence.
 	//
 	// HCL Example:
 	//
@@ -43,8 +43,8 @@ type FloppyConfig struct {
 	// ```
 	FloppyContent map[string]string `mapstructure:"floppy_content"`
 	// The label to use for the floppy disk that is attached when the virtual
-	// machine is booted. This is most useful for cloud-init, Kickstart or other
-	// early initialization tools, which can benefit from labelled floppy disks.
+	// machine is booted. This is most useful for cloud-init, Kickstart, or other
+	// early initialization tools, which can benefit from labeled floppy disks.
 	// By default, the floppy label will be 'packer'.
 	FloppyLabel string `mapstructure:"floppy_label"`
 }
diff --git a/builder/vsphere/common/step_boot_command.go b/builder/vsphere/common/step_boot_command.go
@@ -56,7 +56,7 @@ func (s *StepBootCommand) Run(ctx context.Context, state multistep.StateBag) mul
 		return multistep.ActionContinue
 	}
 
-	// Wait the for the vm to boot.
+	// Wait for the vm to boot.
 	if int64(s.Config.BootWait) > 0 {
 		ui.Sayf("Waiting %s for boot...", s.Config.BootWait.String())
 		select {
@@ -115,7 +115,7 @@ func (s *StepBootCommand) Run(ctx context.Context, state multistep.StateBag) mul
 			}
 		}
 
-		// Check if IP address was determined.
+		// Check if the IP address was determined.
 		if ip == "" {
 			err := fmt.Errorf("error determining IP address")
 			state.Put("error", err)
diff --git a/builder/vsphere/common/step_config_params.go b/builder/vsphere/common/step_config_params.go
@@ -20,7 +20,7 @@ import (
 )
 
 type ConfigParamsConfig struct {
-	// A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+	// A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
 	// in the vSphere API's `VirtualMachineConfigSpec`.
 	//
 	// HCL Example:
@@ -44,7 +44,7 @@ type ConfigParamsConfig struct {
 	// ```
 	//
 	// ~> **Note:** Configuration keys that would conflict with parameters that
-	// are explicitly configurable through other fields in the `ConfigSpec`` object
+	// are explicitly configurable through other fields in the `ConfigSpec` object
 	// are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
 	// in the vSphere API documentation.
 	ConfigParams map[string]string `mapstructure:"configuration_parameters"`
diff --git a/builder/vsphere/common/step_connect.go b/builder/vsphere/common/step_connect.go
@@ -19,8 +19,7 @@ import (
 )
 
 type ConnectConfig struct {
-	// The fully qualified domain name or IP address of the vCenter instance
-	// instance.
+	// The fully qualified domain name or IP address of the vCenter instance.
 	VCenterServer string `mapstructure:"vcenter_server"`
 	// The username to authenticate with the vCenter instance.
 	Username string `mapstructure:"username"`
diff --git a/builder/vsphere/common/step_hardware.go b/builder/vsphere/common/step_hardware.go
@@ -16,7 +16,7 @@ import (
 	"github.com/vmware/packer-plugin-vsphere/builder/vsphere/driver"
 )
 
-// Dynamic DirectPath I/O is component of the Assignable Hardware framework in VMware vSphere.
+// Dynamic DirectPath I/O is the component of the Assignable Hardware framework in VMware vSphere.
 // Dynamic DirectPath I/O enables the Assignable Hardware intelligence for passthrough devices and
 // the hardware address of the PCIe device is no longer directly mapped to the virtual machine
 // configuration. Instead, the attributes, or capabilities, are exposed to the virtual machine.
diff --git a/builder/vsphere/driver/vm.go b/builder/vsphere/driver/vm.go
@@ -825,7 +825,7 @@ func (vm *VirtualMachineDriver) PowerOn() error {
 	return err
 }
 
-// WaitForIP waits for the virtual machine to obtain an IP address.
+// WaitForIP waits for the virtual machine to get an IP address.
 func (vm *VirtualMachineDriver) WaitForIP(ctx context.Context, ipNet *net.IPNet) (string, error) {
 	netIP, err := vm.vm.WaitForNetIP(ctx, false)
 	if err != nil {
@@ -975,7 +975,7 @@ func (vm *VirtualMachineDriver) ImportOvfToContentLibrary(ovf vcenter.OVF) error
 
 	item, err := vm.driver.FindContentLibraryItem(l.library.ID, ovf.Spec.Name)
 	if err == nil {
-		// Update the content library item, if it exists.
+		// Update the content library item if it exists.
 		ovf.Target.LibraryItemID = item.ID
 		if item.Description != nil && ovf.Spec.Description != *item.Description {
 			err = vm.driver.UpdateContentLibraryItem(item, ovf.Spec.Name, ovf.Spec.Description)
@@ -1095,7 +1095,7 @@ func (vm *VirtualMachineDriver) GetDir() (string, error) {
 }
 
 // addNetwork adds a network to the virtual machine. Returns a list of devices
-// with the network added or an error if the  operation fails.
+// with the network added or an error if the operation fails.
 func addNetwork(d *VCenterDriver, devices object.VirtualDeviceList, config *CreateConfig) (object.VirtualDeviceList, error) {
 	for _, nic := range config.NICs {
 		network, err := findNetwork(nic.Network, config.Host, d)
@@ -1137,7 +1137,7 @@ func findNetwork(network string, host string, d *VCenterDriver) (object.NetworkR
 			return networks[0].network, nil
 		}
 
-		// If there are multiple networks then try to match the host.
+		// If there are multiple networks, then try to match the host.
 		if host != "" {
 			h, err := d.FindHost(host)
 			if err != nil {
diff --git a/builder/vsphere/iso/config.go b/builder/vsphere/iso/config.go
@@ -49,7 +49,7 @@ type Config struct {
 	SnapshotName string `mapstructure:"snapshot_name"`
 	// Convert the virtual machine to a template after the build is complete.
 	// Defaults to `false`.
-	// If set to `true`, the virtual machine can not be imported into a content library.
+	// If set to `true`, the virtual machine cannot be imported into a content library.
 	ConvertToTemplate bool `mapstructure:"convert_to_template"`
 	// The configuration for exporting the virtual machine to an OVF.
 	// The virtual machine is not exported if [export configuration](#export-configuration) is not specified.
diff --git a/builder/vsphere/iso/step_create_test.go b/builder/vsphere/iso/step_create_test.go
@@ -281,7 +281,7 @@ func TestStepCreateVM_Cleanup(t *testing.T) {
 	vm := new(driver.VirtualMachineMock)
 	state.Put("vm", vm)
 
-	// Clean up when state is cancelled
+	// Clean up when state is canceled
 	state.Put(multistep.StateCancelled, true)
 	step.Cleanup(state)
 	if !vm.DestroyCalled {
@@ -290,7 +290,7 @@ func TestStepCreateVM_Cleanup(t *testing.T) {
 	vm.DestroyCalled = false
 	state.Remove(multistep.StateCancelled)
 
-	// Clean up when state is halted
+	// Clean up when the state is halted
 	state.Put(multistep.StateHalted, true)
 	step.Cleanup(state)
 	if !vm.DestroyCalled {
@@ -308,7 +308,7 @@ func TestStepCreateVM_Cleanup(t *testing.T) {
 	vm.DestroyCalled = false
 	state.Remove("destroy_vm")
 
-	// Don't clean up if state is not set with previous values
+	// Don't clean up if the state is not set with previous values
 	step.Cleanup(state)
 	if vm.DestroyCalled {
 		t.Fatalf("unexpected result: expected '%s' not to be called", "Destroy")
@@ -353,7 +353,7 @@ func basicStepCreateVM() *StepCreateVM {
 	return step
 }
 
-// basicLocationConfig initializes and returns a default LocationConfig with predefined test values for virtual machine.
+// basicLocationConfig initializes and returns a default LocationConfig with predefined test values for the virtual machine.
 func basicLocationConfig() *common.LocationConfig {
 	return &common.LocationConfig{
 		VMName:       "test-vm",
diff --git a/docs-partials/builder/vsphere/common/ConfigParamsConfig-not-required.mdx b/docs-partials/builder/vsphere/common/ConfigParamsConfig-not-required.mdx
@@ -1,6 +1,6 @@
 <!-- Code generated from the comments of the ConfigParamsConfig struct in builder/vsphere/common/step_config_params.go; DO NOT EDIT MANUALLY -->
 
-- `configuration_parameters` (map[string]string) - A map of key-value pairs to sent to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
+- `configuration_parameters` (map[string]string) - A map of key-value pairs to send to the [`extraConfig`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html#extraConfig).
   in the vSphere API's `VirtualMachineConfigSpec`.
   
   HCL Example:
@@ -24,7 +24,7 @@
   ```
   
   ~> **Note:** Configuration keys that would conflict with parameters that
-  are explicitly configurable through other fields in the `ConfigSpec`` object
+  are explicitly configurable through other fields in the `ConfigSpec` object
   are silently ignored. Refer to the [`VirtualMachineConfigSpec`](https://dp-downloads.broadcom.com/api-content/apis/API_VWSA_001/8.0U3/html/ReferenceGuides/vim.vm.ConfigSpec.html)
   in the vSphere API documentation.
 
diff --git a/docs-partials/builder/vsphere/common/ConnectConfig-not-required.mdx b/docs-partials/builder/vsphere/common/ConnectConfig-not-required.mdx
@@ -1,7 +1,6 @@
 <!-- Code generated from the comments of the ConnectConfig struct in builder/vsphere/common/step_connect.go; DO NOT EDIT MANUALLY -->
 
-- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance
-  instance.
+- `vcenter_server` (string) - The fully qualified domain name or IP address of the vCenter instance.
 
 - `username` (string) - The username to authenticate with the vCenter instance.
 
diff --git a/docs-partials/builder/vsphere/common/FloppyConfig-not-required.mdx b/docs-partials/builder/vsphere/common/FloppyConfig-not-required.mdx
@@ -9,10 +9,10 @@
 - `floppy_dirs` ([]string) - A list of directories to copy files from.
 
 - `floppy_content` (map[string]string) - Key/Values to add to the floppy disk. The keys represent the paths, and
-  the values contents. It can be used alongside `floppy_files` or
+  the value contents. It can be used alongside `floppy_files` or
   `floppy_dirs`, which is useful to add large files without loading them
-  into memory. If any paths are specified by both, the contents in
-  `floppy_content` will take precedence.
+  into memory. If both specify a path, the contents in `floppy_content` will take
+  precedence.
   
   HCL Example:
   
@@ -24,8 +24,8 @@
   ```
 
 - `floppy_label` (string) - The label to use for the floppy disk that is attached when the virtual
-  machine is booted. This is most useful for cloud-init, Kickstart or other
-  early initialization tools, which can benefit from labelled floppy disks.
+  machine is booted. This is most useful for cloud-init, Kickstart, or other
+  early initialization tools, which can benefit from labeled floppy disks.
   By default, the floppy label will be 'packer'.
 
 <!-- End of code generated from the comments of the FloppyConfig struct in builder/vsphere/common/step_add_floppy.go; -->
diff --git a/docs-partials/builder/vsphere/common/PCIPassthroughAllowedDevice.mdx b/docs-partials/builder/vsphere/common/PCIPassthroughAllowedDevice.mdx
@@ -1,6 +1,6 @@
 <!-- Code generated from the comments of the PCIPassthroughAllowedDevice struct in builder/vsphere/common/step_hardware.go; DO NOT EDIT MANUALLY -->
 
-Dynamic DirectPath I/O is component of the Assignable Hardware framework in VMware vSphere.
+Dynamic DirectPath I/O is the component of the Assignable Hardware framework in VMware vSphere.
 Dynamic DirectPath I/O enables the Assignable Hardware intelligence for passthrough devices and
 the hardware address of the PCIe device is no longer directly mapped to the virtual machine
 configuration. Instead, the attributes, or capabilities, are exposed to the virtual machine.
diff --git a/docs-partials/builder/vsphere/iso/Config-not-required.mdx b/docs-partials/builder/vsphere/iso/Config-not-required.mdx
@@ -8,7 +8,7 @@
 
 - `convert_to_template` (bool) - Convert the virtual machine to a template after the build is complete.
   Defaults to `false`.
-  If set to `true`, the virtual machine can not be imported into a content library.
+  If set to `true`, the virtual machine cannot be imported into a content library.
 
 - `export` (\*common.ExportConfig) - The configuration for exporting the virtual machine to an OVF.
   The virtual machine is not exported if [export configuration](#export-configuration) is not specified.
diff --git a/docs-partials/post-processor/vsphere/Config-not-required.mdx b/docs-partials/post-processor/vsphere/Config-not-required.mdx
@@ -42,7 +42,7 @@
   same as the source virtual machine's.
   
   This option is useful when deploying to vCenter instance or an ESX host whose
-  version is different than the one used to create the artifact.
+  version is different from the one used to create the artifact.
   
   Refer to [KB 315655](https://knowledge.broadcom.com/external/article?articleNumber=315655)
   for more information on supported virtual hardware versions.
diff --git a/post-processor/vsphere/post-processor.go b/post-processor/vsphere/post-processor.go
diff --git a/post-processor/vsphere/post-processor_test.go b/post-processor/vsphere/post-processor_test.go

Original file line number	Diff line number	Diff line change
`@@ -56,7 +56,7 @@ func (s *StepBootCommand) Run(ctx context.Context, state multistep.StateBag) mul`
`56`	`56`	`return multistep.ActionContinue`
`57`	`57`	`}`
`58`	`58`
`59`		`- // Wait the for the vm to boot.`
	`59`	`+ // Wait for the vm to boot.`
`60`	`60`	`if int64(s.Config.BootWait) > 0 {`
`61`	`61`	`ui.Sayf("Waiting %s for boot...", s.Config.BootWait.String())`
`62`	`62`	`select {`
`@@ -115,7 +115,7 @@ func (s *StepBootCommand) Run(ctx context.Context, state multistep.StateBag) mul`
`115`	`115`	`}`
`116`	`116`	`}`
`117`	`117`
`118`		`- // Check if IP address was determined.`
	`118`	`+ // Check if the IP address was determined.`
`119`	`119`	`if ip == "" {`
`120`	`120`	`err := fmt.Errorf("error determining IP address")`
`121`	`121`	`state.Put("error", err)`
Original file line number	Diff line number	Diff line change
`@@ -19,8 +19,7 @@ import (`
`19`	`19`	`)`
`20`	`20`
`21`	`21`	`type ConnectConfig struct {`
`22`		`- // The fully qualified domain name or IP address of the vCenter instance`
`23`		`- // instance.`
	`22`	`+ // The fully qualified domain name or IP address of the vCenter instance.`
`24`	`23`	VCenterServer string `mapstructure:"vcenter_server"`
`25`	`24`	`// The username to authenticate with the vCenter instance.`
`26`	`25`	Username string `mapstructure:"username"`
Original file line number	Diff line number	Diff line change
`@@ -16,7 +16,7 @@ import (`
`16`	`16`	`"github.com/vmware/packer-plugin-vsphere/builder/vsphere/driver"`
`17`	`17`	`)`
`18`	`18`
`19`		`-// Dynamic DirectPath I/O is component of the Assignable Hardware framework in VMware vSphere.`
	`19`	`+// Dynamic DirectPath I/O is the component of the Assignable Hardware framework in VMware vSphere.`
`20`	`20`	`// Dynamic DirectPath I/O enables the Assignable Hardware intelligence for passthrough devices and`
`21`	`21`	`// the hardware address of the PCIe device is no longer directly mapped to the virtual machine`
`22`	`22`	`// configuration. Instead, the attributes, or capabilities, are exposed to the virtual machine.`