removing all downloaded devdocs files

1 files changed, 0 insertions, 6 deletions

diff --git a/devdocs/vagrant/vmware%2Fknown-issues.html b/devdocs/vagrant/vmware%2Fknown-issues.html
deleted file mode 100644
index ee179d50..00000000
--- a/devdocs/vagrant/vmware%2Fknown-issues.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<h1 id="known-issues">  Known Issues </h1> <p>This page tracks some known issues or limitations of the VMware provider. Note that none of these are generally blockers to using the provider, but are good to know.</p> <h2 id="network-disconnect">  Network disconnect </h2> <p>When Vagrant applies port forwarding rules while bring up a guest instance, other running VMware VMs may experience a loss of network connectivity. The cause of this connectivity issue is the restarting of the VMware NAT service to apply new port forwarding rules. Since new rules cannot be applied to the NAT service while it is running, it is required to restart the service, which results in the loss of connectivity.</p> <h2 id="forwarded-ports-failing-in-workstation-on-windows">  Forwarded Ports Failing in Workstation on Windows </h2> <p>VMware Workstation has a bug on Windows where forwarded ports do not work properly. Vagrant actually works around this bug and makes them work. However, if you run the virtual network editor on Windows, the forwarded ports will suddenly stop working.</p> <p>In this case, run <code>vagrant reload</code> and things will begin working again.</p> <p>This issue has been reported to VMware, but a fix has not been released yet.</p><div class="_attribution">
-  <p class="_attribution-p">
-    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
-    <a href="https://www.vagrantup.com/docs/vmware/known-issues.html" class="_attribution-link">https://www.vagrantup.com/docs/vmware/known-issues.html</a>
-  </p>
-</div>