From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Thu, 14 Aug 2025 22:58:58 -0500
Subject: removing all downloaded devdocs files

---
 devdocs/vagrant/plugins%2Findex.html | 6 ------
 1 file changed, 6 deletions(-)
 delete mode 100644 devdocs/vagrant/plugins%2Findex.html

(limited to 'devdocs/vagrant/plugins%2Findex.html')

diff --git a/devdocs/vagrant/plugins%2Findex.html b/devdocs/vagrant/plugins%2Findex.html
deleted file mode 100644
index eb8b1e6d..00000000
--- a/devdocs/vagrant/plugins%2Findex.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<h1 id="plugins">  Plugins </h1> <p>Vagrant comes with many great features out of the box to get your environments up and running. Sometimes, however, you want to change the way Vagrant does something or add additional functionality to Vagrant. This can be done via Vagrant <em>plugins</em>.</p> <p>Plugins are powerful, first-class citizens that extend Vagrant using a well-documented, stable API that can withstand major version upgrades.</p> <p>In fact, most of the core of Vagrant is <a href="https://github.com/hashicorp/vagrant/tree/master/plugins">implemented using plugins</a>. Since Vagrant <a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">dogfoods</a> its own plugin API, you can be confident that the interface is stable and well supported.</p> <p>Use the navigation on the left below the "Plugins" section to learn more about how to use and build your own plugins.</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/plugins/" class="_attribution-link">https://www.vagrantup.com/docs/plugins/</a>
-  </p>
-</div>
-- 
cgit v1.2.3