en.yml in vagrant-unbundled-2.0.4.0

- old
+ new

@@ -400,10 +400,16 @@
         provider.
 
         Machine name: %{name}
         Active provider: %{active_provider}
         Requested provider: %{requested_provider}
+      alias_invalid_error: |-
+        The defined alias is not valid. Please review the information below
+        to help resolve the issue:
+
+        Alias: %{alias}
+        Message: %{message}
       batch_multi_error: |-
         An error occurred while executing multiple actions in parallel.
         Any errors that occurred are shown below.
 
         %{message}
@@ -773,11 +779,11 @@
       downloader_checksum_error: |-
         The calculated checksum of the requested file does not match the expected
         checksum!
 
         File source:         %{source}
-        Checsum type:        %{type}
+        Checksum type:       %{type}
         Expected checksum:   %{expected_checksum}
         Calculated checksum: %{actual_checksum}
       env_inval: |-
         Vagrant received an "EINVAL" error while attempting to set some
         environment variables. This is usually caused by the total size of your
@@ -926,11 +932,11 @@
           %{error_msg}
       network_manager_not_installed: |-
         Vagrant was instructed to configure the %{device} network device to
         be managed by NetworkManager. However, the configured guest VM does
         not have NetworkManager installed. To fix this error please remove
-        the `nm_controlled` setting from local Vagantfile. If NetworkManager
+        the `nm_controlled` setting from local Vagrantfile. If NetworkManager
         is required to manage the network devices, please use a box with
         NetworkManager installed.
       nfs_bad_exports: |-
         NFS is reporting that your exports file is invalid. Vagrant does
         this check before making any changes to the file. Please correct
@@ -1623,11 +1629,11 @@
           https://www.vagrantup.com/docs/other/wsl.html
       wsl_virtualbox_windows_access: |-
         Vagrant is unable to use the VirtualBox provider from the Windows Subsystem for
         Linux without access to the Windows environment. Enabling this access must be
         done with caution and an understanding of the implications. For more information
-        on enabing Windows access and using VirtualBox from the Windows Subsystem for
+        on enabling Windows access and using VirtualBox from the Windows Subsystem for
         Linux, please refer to the Vagrant documentation:
 
           https://www.vagrantup.com/docs/other/wsl.html
       wsl_rootfs_not_found_error: |-
         Vagrant is unable to determine the location of this instance of the Windows
@@ -1836,11 +1842,11 @@
           stopped without properly closing the session. Run `vagrant up`
           to resume this virtual machine. If any problems persist, you may
           have to destroy and restart the virtual machine.
         gurumeditation: |-
           The VM is in the "guru meditation" state. This is a rare case which means
-          that an internal error in VitualBox caused the VM to fail. This is always
+          that an internal error in VirtualBox caused the VM to fail. This is always
           the sign of a bug in VirtualBox. You can try to bring your VM back online
           with a `vagrant up`.
         inaccessible: |-
           The VM is inaccessible! This is a rare case which means that VirtualBox
           can't find your VM configuration. This usually happens when upgrading
@@ -2068,9 +2074,12 @@
           collides: |-
             The specified host network collides with a non-hostonly network!
             This will cause your specified IP to be inaccessible. Please change
             the IP or name of your host only network so that it no longer matches that of
             a bridged or non-hostonly network.
+
+            Bridged Network Address: '%{netaddr}'
+            Host-only Network '%{interface_name}': '%{that_netaddr}'
           creating: "Creating new host only network for environment..."
           enabling: "Enabling host only network..."
           not_found: |-
             The specified host network could not be found: '%{name}.'
             If the name specification is removed, Vagrant will create a new