diff --git a/_vendor/github.com/linode/linode-docs-theme/assets/js/main/index.js b/_vendor/github.com/linode/linode-docs-theme/assets/js/main/index.js
index 77e8ec3e075..4a88e2f5438 100644
--- a/_vendor/github.com/linode/linode-docs-theme/assets/js/main/index.js
+++ b/_vendor/github.com/linode/linode-docs-theme/assets/js/main/index.js
@@ -130,7 +130,7 @@ const searchConfig = getSearchConfig(params);
 		this.dataLayer.push(event);
 	};
 
-	let pushGTag = function (eventName) {
+	let pushDataLayer = function (eventName) {
 		let event = {
 			event: eventName,
 		};
@@ -173,7 +173,7 @@ const searchConfig = getSearchConfig(params);
 
 		window.turbolinksLoaded = true;
 		setTimeout(function () {
-			pushGTag('docs_load');
+			pushDataLayer('docs_load');
 		}, 2000);
 	});
 
@@ -191,7 +191,7 @@ const searchConfig = getSearchConfig(params);
 			return;
 		}
 
-		pushGTag('docs_navigate');
+		pushDataLayer('docs_navigate');
 	});
 
 	// Preserve scroll position when navigating with Turbo on all elements with the data-preserve-scroll attribute.
@@ -202,6 +202,13 @@ const searchConfig = getSearchConfig(params);
 		window.scrollHandledByClick = {};
 	}
 
+	function turboClick(e) {
+		if (e.detail.url.includes('/docs/api')) {
+			// Disable Turbo for the API docs to allow for edge redirects.
+			e.preventDefault();
+		}
+	}
+
 	function preserveScroll(e) {
 		document.querySelectorAll('[data-preserve-scroll]').forEach((el) => {
 			// Check if the event's target is a child of the element.
@@ -250,6 +257,7 @@ const searchConfig = getSearchConfig(params);
 	}
 
 	window.addEventListener('turbo:click', preserveScroll);
+	window.addEventListener('turbo:click', turboClick);
 	window.addEventListener('turbo:before-render', restoreScroll);
 	window.addEventListener('turbo:render', restoreScroll);
 })();
diff --git a/_vendor/github.com/linode/linode-docs-theme/config.toml b/_vendor/github.com/linode/linode-docs-theme/config.toml
index 8c2c09f2272..8296119a23e 100644
--- a/_vendor/github.com/linode/linode-docs-theme/config.toml
+++ b/_vendor/github.com/linode/linode-docs-theme/config.toml
@@ -4,9 +4,6 @@ time_format_iso8601 = "2006-01-02T15:04:05-07:00"
 
 weglot_api_key = "wg_3b3ef29c81aa81292c64d1368ee318969"
 
-# Google Tag Manager ID used in production.
-# For development/staging, see the config dir.
-gtmID = "GTM-T5FXXG9"
 
 # # Adobe Analytics script used in production.
 # For development/staging, see the config dir.
diff --git a/_vendor/github.com/linode/linode-docs-theme/config/development/config.toml b/_vendor/github.com/linode/linode-docs-theme/config/development/config.toml
index 3ca8cbdca7e..850a06dfcaa 100644
--- a/_vendor/github.com/linode/linode-docs-theme/config/development/config.toml
+++ b/_vendor/github.com/linode/linode-docs-theme/config/development/config.toml
@@ -1,7 +1,4 @@
 [params]
-    # GTM container used in development and on Netlify.
-    gtmID = "GTM-TS67W4L"
-
     # Adobe Analytics script used in development and on Netlify.
     adobe_launch_script = "https://assets.adobedtm.com/fcfd3580c848/f9e7661907ee/launch-006d022c8726-development.min.js"
 
diff --git a/_vendor/github.com/linode/linode-docs-theme/config/staging/config.toml b/_vendor/github.com/linode/linode-docs-theme/config/staging/config.toml
index 57e201e67da..89e603d2676 100644
--- a/_vendor/github.com/linode/linode-docs-theme/config/staging/config.toml
+++ b/_vendor/github.com/linode/linode-docs-theme/config/staging/config.toml
@@ -1,7 +1,4 @@
 [params]
-    # GTM container used in Staging (docs.staging.linode.com/docs)
-    # gtmID = "GTM-T5FXXG9"
-
     # Adobe Analytics script used in Staging (docs.staging.linode.com/docs)
     adobe_launch_script = "https://assets.adobedtm.com/fcfd3580c848/f9e7661907ee/launch-96338797f65e-staging.min.js"
 
diff --git a/_vendor/github.com/linode/linode-docs-theme/config/testing/config.toml b/_vendor/github.com/linode/linode-docs-theme/config/testing/config.toml
index 3ca8cbdca7e..850a06dfcaa 100644
--- a/_vendor/github.com/linode/linode-docs-theme/config/testing/config.toml
+++ b/_vendor/github.com/linode/linode-docs-theme/config/testing/config.toml
@@ -1,7 +1,4 @@
 [params]
-    # GTM container used in development and on Netlify.
-    gtmID = "GTM-TS67W4L"
-
     # Adobe Analytics script used in development and on Netlify.
     adobe_launch_script = "https://assets.adobedtm.com/fcfd3580c848/f9e7661907ee/launch-006d022c8726-development.min.js"
 
diff --git a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/components/render-svg.html b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/components/render-svg.html
index 0fc3363ca2f..6328d8c533c 100644
--- a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/components/render-svg.html
+++ b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/components/render-svg.html
@@ -126,7 +126,9 @@
     x-transition.opacity
     :style="tooltip.style"
     x-show="tooltip.show">
-    <div class="tooltip bg-gray-200 p-4 rounded-md flex w-full">
+    <div
+      class="tooltip bg-gray-200 rounded-md flex w-full"
+      :class="{ 'p-12' : showModal, 'p-4' : !showModal}">
       <div class="tooltip-badge mr-4 mt-2">
         <span
           x-text="tooltip.number"
diff --git a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/head.html b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/head.html
index ddd58945d56..9cfae331f5d 100644
--- a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/head.html
+++ b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/head.html
@@ -34,18 +34,4 @@
 */}}<script
   src="{{ site.Params.adobe_launch_script }}"
   async></script>
-{{ if (ne hugo.Environment "development") }}
-  <!-- Google Tag Manager -->  <script>
-    (function (w, d, s, l, i) {
-    w[l] = w[l] || []; w[l].push({
-    'gtm.start':
-    new Date().getTime(), event: 'gtm.js'
-    });
-    var f = d.getElementsByTagName(s)[0],
-    j = d.createElement(s), dl = l != 'dataLayer' ? '&l=' + l : ''; j.async = true; j.src =
-    'https://www.googletagmanager.com/gtm.js?id=' + i + dl; f.parentNode.insertBefore(j, f);
-    })(window, document, 'script', 'dataLayer', '{{ site.Params.gtmID }}');
-  </script>
-  <!-- End Google Tag Manager -->
-{{ end }}
 {{ partialCached "sections/head-src.html" . "-" }}
diff --git a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-hydrated.html b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-hydrated.html
index fc90ffbee99..8a57cb30910 100644
--- a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-hydrated.html
+++ b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-hydrated.html
@@ -84,6 +84,7 @@
         <div class="flex items-center h-full">
           <span
             class="text-xs font-semibold pr-6 text-basicgray"
+            x-show="$store.search.query.isFiltered()"
             :class="{  'text-brand': ({{ $.n }}.count > 0) && $store.search.query.isFiltered(),
                 'text-gray-100': ({{ $.n }}.count === 0),
                 'text-basicgray': ({{ $.n }}.count > 0) && !$store.search.query.isFiltered() }"
@@ -101,7 +102,6 @@
               'border-l-2 pl-3 py-1': node.level > 1
             }"
         x-show="{{ $.n }}.open"
-        x-transition.200ms
         x-ref="node-tree"></ul>
     </div>
   </li>
diff --git a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-initial.html b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-initial.html
index d19a9238ae9..480dd8200e1 100644
--- a/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-initial.html
+++ b/_vendor/github.com/linode/linode-docs-theme/layouts/partials/sections/navigation/explorer-initial.html
@@ -146,13 +146,8 @@
             "text-basicgray" (not (eq .node.count 0))
             )
           }}
-          {{ with .node.count }}
-            <span
-              class="text-xs font-semibold pr-6 {{ $classes }}"
-              data-testid="node-count"
-              >{{ . }}</span
-            >
-          {{ end }}
+
+
           <div class="z-10">
             {{ $ariaLabel := cond .node.open "close" "open" }}
             {{ $classes := partial "inline/get-classes" (dict
diff --git a/_vendor/github.com/linode/linode-website-partials/header.html b/_vendor/github.com/linode/linode-website-partials/header.html
index 363537d0245..ad2faefe392 100644
--- a/_vendor/github.com/linode/linode-website-partials/header.html
+++ b/_vendor/github.com/linode/linode-website-partials/header.html
@@ -65,39 +65,6 @@
 
 
 
-  <div class="o-layout__row c-site-header__banner c-message" id="x-banner-2023-23-13">
-    <div class="c-message__body">
-      <div class="c-notification">
-        <a href="#" class="c-notification__link" target="_self">
-          <span class="c-notification__tag"></span>
-          <span class="c-notification__message"></span>
-        </a>
-      </div>
-    </div>
-    <button type="button" class="c-message__x" aria-label="Dismiss message">
-      <svg viewBox="0 0 320 512"><path fill="currentcolor" d="M207.6 256l107.72-107.72c6.23-6.23 6.23-16.34.0-22.58l-25.03-25.03c-6.23-6.23-16.34-6.23-22.58.0L160 208.4 52.28 100.68c-6.23-6.23-16.34-6.23-22.58.0L4.68 125.7c-6.23 6.23-6.23 16.34.0 22.58L112.4 256 4.68 363.72c-6.23 6.23-6.23 16.34.0 22.58l25.03 25.03c6.23 6.23 16.34 6.23 22.58.0L160 303.6l107.72 107.72c6.23 6.23 16.34 6.23 22.58.0l25.03-25.03c6.23-6.23 6.23-16.34.0-22.58L207.6 256z"/></svg>
-    </button>
-  </div>
-  <script>
-    (function(){
-      var lsk = 'x-banner-2023-23-13',
-          bc = 'has-banner',
-          $ht = document.querySelector( 'html' ),
-          $bn = document.getElementById( lsk ),
-          $x = $bn.querySelector( '.c-message__x' ),
-          lsv = localStorage.getItem( lsk ),
-          rm = function(){
-            $ht.classList.remove( bc );
-            $bn.remove();
-          };
-      if ( lsv ) { rm(); return; }
-      $ht.classList.add( bc );
-      $x.addEventListener('click',function(){
-        localStorage.setItem( lsk, true );
-        rm();
-      });
-    })();
-  </script>
   <div class="o-layout__row c-site-header__topbar">
     <div class="o-layout__colset">
       <div class="o-layout__col">
diff --git a/_vendor/modules.txt b/_vendor/modules.txt
index be70b28c249..683ce22e8bb 100644
--- a/_vendor/modules.txt
+++ b/_vendor/modules.txt
@@ -1,5 +1,5 @@
-# github.com/linode/linode-docs-theme v0.0.0-20240610162252-dd3795f29d6a
-# github.com/linode/linode-website-partials v0.0.0-20240426140442-12b76ccbfefd
+# github.com/linode/linode-docs-theme v0.0.0-20240618214412-23d0d6b33823
+# github.com/linode/linode-website-partials v0.0.0-20240516182804-8b13c1f13759
 # github.com/gohugoio/hugo-mod-jslibs-dist/alpinejs/v3 v3.21300.20800
 # github.com/gohugoio/hugo-mod-jslibs/turbo/v8 v8.20000.20400
 # github.com/hotwired/turbo v8.0.4+incompatible
diff --git a/docs/guides/applications/big-data/how-to-install-and-configure-a-redis-cluster-on-ubuntu-1604/index.md b/docs/guides/applications/big-data/how-to-install-and-configure-a-redis-cluster-on-ubuntu-1604/index.md
index 225ed966c8a..898d6da937d 100644
--- a/docs/guides/applications/big-data/how-to-install-and-configure-a-redis-cluster-on-ubuntu-1604/index.md
+++ b/docs/guides/applications/big-data/how-to-install-and-configure-a-redis-cluster-on-ubuntu-1604/index.md
@@ -13,6 +13,7 @@ aliases: ['/applications/big-data/redis-cluster/','/applications/big-data/how-to
 external_resources:
  - '[Redis Official Website](https://redis.io/)'
  - '[Install and Configure Redis on CentOS 7](/docs/guides/install-and-configure-redis-on-centos-7/)'
+deprecated: true
 ---
 
 ![How to Install and Configure a Redis Cluster on Ubuntu 16.04](Redis_Cluster.jpg)
diff --git a/docs/guides/applications/cloud-storage/access-google-drive-linode/index.md b/docs/guides/applications/cloud-storage/access-google-drive-linode/index.md
index 70205a0d6cf..35581d27236 100644
--- a/docs/guides/applications/cloud-storage/access-google-drive-linode/index.md
+++ b/docs/guides/applications/cloud-storage/access-google-drive-linode/index.md
@@ -10,6 +10,7 @@ keywords: ["google", "drive", "console", "fuse", "apt", "ubuntu"]
 tags: ["ubuntu"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/applications/cloud-storage/access-google-drive-linode/']
+deprecated: true
 ---
 
 If you've used Google Drive, you know that it can be an indispensable tool for remote file access. While one of the standard counter-arguments to remote storage is "just carry a flash drive," that only works until you need to add a file to your Linode. This guide will show you how to install and configure a great piece of free software to access your Google Drive from your Linode running Ubuntu version 14.04 or newer.
diff --git a/docs/guides/applications/cloud-storage/how-to-install-a-turtl-server-on-ubuntu/index.md b/docs/guides/applications/cloud-storage/how-to-install-a-turtl-server-on-ubuntu/index.md
index c6a1c3e3404..e81b47135d7 100644
--- a/docs/guides/applications/cloud-storage/how-to-install-a-turtl-server-on-ubuntu/index.md
+++ b/docs/guides/applications/cloud-storage/how-to-install-a-turtl-server-on-ubuntu/index.md
@@ -11,6 +11,7 @@ tags: ["ubuntu"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 
 aliases: ['/applications/cloud-storage/how-to-install-a-turtl-server-on-ubuntu/']
+deprecated: true
 ---
 
 ![Header image](Turtl.jpg)
diff --git a/docs/guides/applications/cloud-storage/how-to-use-zfs-on-ubuntu-16-04/index.md b/docs/guides/applications/cloud-storage/how-to-use-zfs-on-ubuntu-16-04/index.md
index a409c677f1c..a62730b4c9d 100644
--- a/docs/guides/applications/cloud-storage/how-to-use-zfs-on-ubuntu-16-04/index.md
+++ b/docs/guides/applications/cloud-storage/how-to-use-zfs-on-ubuntu-16-04/index.md
@@ -14,6 +14,7 @@ external_resources:
  - '[Ubuntu ZFS wiki](https://wiki.ubuntu.com/Kernel/Reference/ZFS)'
  - '[RAID levels Wikipedia](https://en.wikipedia.org/wiki/Standard_RAID_levels)'
 aliases: ['/applications/cloud-storage/how-to-use-zfs-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 ![How to Use ZFS on Ubuntu 16.04](zfs-on-ubuntu-title.jpg "How to Use ZFS on Ubuntu 16.04 title graphic")
diff --git a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-16-04/index.md b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-16-04/index.md
index 930eb438a14..5c7c53ec198 100644
--- a/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-16-04/index.md
+++ b/docs/guides/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-16-04/index.md
@@ -18,6 +18,7 @@ relations:
         keywords:
             - distribution: Ubuntu 16.04
 aliases: ['/applications/cloud-storage/install-and-configure-owncloud-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 OwnCloud is an open-source, cloud-based, file hosting service you can install on your Linode. OwnCloud offers a quick installation process, works out of the box, and has an extensive library of plugins available. Its cross-platform compatibility means you can access your files from most major operating systems, browsers, and mobile devices.
diff --git a/docs/guides/applications/cloud-storage/install-seafile-with-nginx-on-ubuntu-1604/index.md b/docs/guides/applications/cloud-storage/install-seafile-with-nginx-on-ubuntu-1604/index.md
index 3b8f996fa4f..b6896e57e9d 100644
--- a/docs/guides/applications/cloud-storage/install-seafile-with-nginx-on-ubuntu-1604/index.md
+++ b/docs/guides/applications/cloud-storage/install-seafile-with-nginx-on-ubuntu-1604/index.md
@@ -12,6 +12,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 external_resources:
  - '[Seafile Server Manual](https://manual.seafile.com/)'
 aliases: ['/applications/cloud-storage/install-seafile-with-nginx-on-ubuntu-1604/']
+deprecated: true
 ---
 
 Seafile is a cross-platform file hosting tool with server applications for Linux and Windows, and GUI clients for Android, iOS, Linux, OS X and Windows. It supports file versioning and snapshots, two-factor authentication, WebDAV, and can be paired with NGINX or Apache to enable connections over HTTPS.
diff --git a/docs/guides/applications/cloud-storage/tahoe-lafs-on-debian-9/index.md b/docs/guides/applications/cloud-storage/tahoe-lafs-on-debian-9/index.md
index 43f16a06d1d..7b69ba2b4ce 100644
--- a/docs/guides/applications/cloud-storage/tahoe-lafs-on-debian-9/index.md
+++ b/docs/guides/applications/cloud-storage/tahoe-lafs-on-debian-9/index.md
@@ -14,6 +14,7 @@ external_resources:
 - '[Tahoe-LAFS Project Page](https://tahoe-lafs.org/)'
 - '[Tahoe-LAFS Documentation](http://tahoe-lafs.readthedocs.io)'
 aliases: ['/applications/cloud-storage/tahoe-lafs-on-debian-9/']
+deprecated: true
 ---
 
 ## What is Tahoe-LAFS?
diff --git a/docs/guides/applications/configuration-management/salt/use-salt-states-to-configure-a-lamp-stack-on-a-minion/index.md b/docs/guides/applications/configuration-management/salt/use-salt-states-to-configure-a-lamp-stack-on-a-minion/index.md
index 021f1fb6160..8d3e3e121ac 100644
--- a/docs/guides/applications/configuration-management/salt/use-salt-states-to-configure-a-lamp-stack-on-a-minion/index.md
+++ b/docs/guides/applications/configuration-management/salt/use-salt-states-to-configure-a-lamp-stack-on-a-minion/index.md
@@ -11,6 +11,7 @@ tags: ["automation","salt","debian","lamp","apache"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/applications/salt/salt-states-configuration-apache-mysql-php/','/applications/configuration-management/salt/use-salt-states-to-configure-a-lamp-stack-on-a-minion/','/applications/configuration-management/use-salt-states-to-configure-a-lamp-stack-on-a-minion/']
 image: UseSaltStatestoConfigureaLAMPStackonaMinion.png
+deprecated: true
 ---
 
 This tutorial will configure a Minion's LAMP stack with further use of Salt States. This tutorial is written for Debian 8 but can easily be adjusted for other Linux Distributions. You will need a working Salt master and minion configuration before starting this guide. If you need to set up that prerequisite, see our [Salt installation guide](/docs/guides/getting-started-with-salt-basic-installation-and-setup/) to get started.
diff --git a/docs/guides/applications/containers/how-to-install-openvz-on-debian-9/index.md b/docs/guides/applications/containers/how-to-install-openvz-on-debian-9/index.md
index 9bd70f23c68..ff8a8fa70cc 100644
--- a/docs/guides/applications/containers/how-to-install-openvz-on-debian-9/index.md
+++ b/docs/guides/applications/containers/how-to-install-openvz-on-debian-9/index.md
@@ -14,6 +14,7 @@ external_resources:
   - '[Basic OpenVZ Operations](https://openvz.org/Basic_operations_in_OpenVZ_environment)'
   - '[OpenVZ User Contributed Templates](https://openvz.org/Download/template/precreated)'
 aliases: ['/applications/containers/how-to-install-openvz-on-debian-9/']
+deprecated: true
 ---
 
 ## What is OpenVZ?
diff --git a/docs/guides/applications/containers/node-js-web-server-deployed-within-docker/index.md b/docs/guides/applications/containers/node-js-web-server-deployed-within-docker/index.md
index d191d56e182..3119e262aa4 100644
--- a/docs/guides/applications/containers/node-js-web-server-deployed-within-docker/index.md
+++ b/docs/guides/applications/containers/node-js-web-server-deployed-within-docker/index.md
@@ -15,6 +15,7 @@ external_resources:
 - '[Docker Docs](http://docs.docker.com/)'
 - '[Docker Try it Tutorial](https://www.docker.com/tryit/)'
 - '[Docker Hub](https://hub.docker.com/)'
+deprecated: true
 ---
 
 Node.js is a server-side, JavaScript package, often used for various cloud applications. Docker is a container platform. With Docker, users can download applications without the hassle of the installation and configuration process.
diff --git a/docs/guides/applications/messaging/installing-rocketchat-ubuntu-16-04/index.md b/docs/guides/applications/messaging/installing-rocketchat-ubuntu-16-04/index.md
index e3096ce345f..d0006197f90 100644
--- a/docs/guides/applications/messaging/installing-rocketchat-ubuntu-16-04/index.md
+++ b/docs/guides/applications/messaging/installing-rocketchat-ubuntu-16-04/index.md
@@ -15,6 +15,7 @@ external_resources:
  - '[Configuring SSL Reversae Proxy](https://rocket.chat/docs/installation/manual-installation/configuring-ssl-reverse-proxy/)'
  - '[Configuring HTTPS Servers](http://nginx.org/en/docs/http/configuring_https_servers.html)'
 aliases: ['/applications/messaging/installing-rocketchat-ubuntu-16-04/']
+deprecated: true
 ---
 
 **Rocket.Chat** is an open source chat software alternative to Slack that ships with the feature rich components users have come to expect for team productivity. Chat with team members, make video and audio calls with screen sharing, create channels and private groups, upload files and more. With Rocket.Chat's source code hosted on GitHub, you can develop new features and contribute back to the project.
diff --git a/docs/guides/applications/project-management/how-to-install-and-configure-redmine-on-ubuntu-16-04/index.md b/docs/guides/applications/project-management/how-to-install-and-configure-redmine-on-ubuntu-16-04/index.md
index f002e332cc8..9e4c0f051ea 100644
--- a/docs/guides/applications/project-management/how-to-install-and-configure-redmine-on-ubuntu-16-04/index.md
+++ b/docs/guides/applications/project-management/how-to-install-and-configure-redmine-on-ubuntu-16-04/index.md
@@ -14,6 +14,7 @@ external_resources:
 - '[Redmine Users Guide](https://www.redmine.org/projects/redmine/wiki/Getting_Started)'
 - "[Andrew Hosch's Guide on Redmine](http://www.untrustedconnection.com/2016/04/redmine-passenger-and-nginx-on-ubuntu.html)"
 aliases: ['/applications/project-management/how-to-install-and-configure-redmine-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 ![How to Install and Configure Redmine on Ubuntu](how-to-install-and-configure-redmine-on-ubuntu-smg.jpg)
diff --git a/docs/guides/applications/voip/install-and-configure-mumble-on-debian/index.md b/docs/guides/applications/voip/install-and-configure-mumble-on-debian/index.md
index a51864e6518..df49743eda3 100644
--- a/docs/guides/applications/voip/install-and-configure-mumble-on-debian/index.md
+++ b/docs/guides/applications/voip/install-and-configure-mumble-on-debian/index.md
@@ -14,6 +14,7 @@ external_resources:
  - '[Mumble Wiki](http://wiki.mumble.info/wiki/Main_Page)'
 dedicated_cpu_link: true
 aliases: ['/applications/voip/install-and-configure-mumble-on-debian/']
+deprecated: true
 ---
 
 [Mumble](http://wiki.mumble.info/wiki/Main_Page) is an open-source VoIP client, designed for gamers, that requires a server for all clients to connect to. This guide instructs how to install and configure the Mumble server (also called Murmur) on Debian.
diff --git a/docs/guides/databases/cassandra/how-to-install-apache-cassandra-on-debian-9/index.md b/docs/guides/databases/cassandra/how-to-install-apache-cassandra-on-debian-9/index.md
index cc2029c8111..24f53caede5 100644
--- a/docs/guides/databases/cassandra/how-to-install-apache-cassandra-on-debian-9/index.md
+++ b/docs/guides/databases/cassandra/how-to-install-apache-cassandra-on-debian-9/index.md
@@ -22,6 +22,7 @@ relations:
             - distribution: Debian 9
 tags: ["debian","database","nosql"]
 aliases: ['/databases/cassandra/how-to-install-apache-cassandra-on-debian-9/']
+deprecated: true
 ---
 
 After completing this guide, you will have a single-node, production-ready installation of [Apache Cassandra](http://cassandra.apache.org/) hosted on your Linode running Debian 9. This tutorial will cover basic configuration options, as well as harden database security.
diff --git a/docs/guides/databases/elasticsearch/visualize-apache-web-server-logs-using-elastic-stack-on-debian-8/index.md b/docs/guides/databases/elasticsearch/visualize-apache-web-server-logs-using-elastic-stack-on-debian-8/index.md
index 9c498859415..a6650f3bd86 100644
--- a/docs/guides/databases/elasticsearch/visualize-apache-web-server-logs-using-elastic-stack-on-debian-8/index.md
+++ b/docs/guides/databases/elasticsearch/visualize-apache-web-server-logs-using-elastic-stack-on-debian-8/index.md
@@ -20,6 +20,7 @@ relations:
         key: visualize-apache-logs-using-elastic-stack
         keywords:
             - distribution: Debian 8
+deprecated: true
 ---
 
 ![Visualize Apache Web Server Logs Using an Elastic Stack on Debian 8](elastic-stack-visualize-server-logs-title.jpg "Visualize Apache Web Server Logs Using an Elastic Stack on Debian 8")
diff --git a/docs/guides/databases/mariadb/how-to-install-mariadb-on-debian-9/index.md b/docs/guides/databases/mariadb/how-to-install-mariadb-on-debian-9/index.md
index 0ce0c36ed9c..ef423d0d9b3 100644
--- a/docs/guides/databases/mariadb/how-to-install-mariadb-on-debian-9/index.md
+++ b/docs/guides/databases/mariadb/how-to-install-mariadb-on-debian-9/index.md
@@ -21,6 +21,7 @@ relations:
         keywords:
             - distribution: Debian 9
 tags: ["debian","mariadb","database"]
+deprecated: true
 ---
 
 MariaDB is a fork of the popular cross-platform MySQL database management system and is considered a full [drop-in replacement](https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/) for MySQL. MariaDB was created by one of MySQL's original developers in 2009 after MySQL was acquired by Oracle during the Sun Microsystems merger. Today MariaDB is maintained and developed by the [MariaDB Foundation](https://mariadb.org/en/foundation/) and community contributors with the intention of it remaining GNU GPL software.
diff --git a/docs/guides/databases/mongodb/install-mongodb-on-ubuntu-16-04/index.md b/docs/guides/databases/mongodb/install-mongodb-on-ubuntu-16-04/index.md
index f96ff4e3730..5801c2229a6 100644
--- a/docs/guides/databases/mongodb/install-mongodb-on-ubuntu-16-04/index.md
+++ b/docs/guides/databases/mongodb/install-mongodb-on-ubuntu-16-04/index.md
@@ -19,6 +19,7 @@ relations:
             - distribution: Ubuntu 16.04
 tags: ["ubuntu","database","nosql"]
 aliases: ['/databases/mongodb/install-mongodb-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 In this MongoDB tutorial, we explain how to install the database on Ubuntu 16.04, and then provide a short guide on some basic features and functions.
diff --git a/docs/guides/databases/mysql/how-to-install-mysql-on-debian-8/index.md b/docs/guides/databases/mysql/how-to-install-mysql-on-debian-8/index.md
index a6055eba1f0..d258f40bead 100644
--- a/docs/guides/databases/mysql/how-to-install-mysql-on-debian-8/index.md
+++ b/docs/guides/databases/mysql/how-to-install-mysql-on-debian-8/index.md
@@ -21,6 +21,7 @@ relations:
         keywords:
             - distribution: Debian 8
 tags: ["debian","database","mysql"]
+deprecated: true
 ---
 
 ![How to Install MySQL on Debian 8](how-to-install-mysql-on-debian-8.jpg "How to Install MySQL on Debian 8")
diff --git a/docs/guides/databases/mysql/install-and-configure-mysql-workbench-on-ubuntu/index.md b/docs/guides/databases/mysql/install-and-configure-mysql-workbench-on-ubuntu/index.md
index 938e39d5672..9a2d019f667 100644
--- a/docs/guides/databases/mysql/install-and-configure-mysql-workbench-on-ubuntu/index.md
+++ b/docs/guides/databases/mysql/install-and-configure-mysql-workbench-on-ubuntu/index.md
@@ -12,6 +12,7 @@ external_resources:
  - '[MySQL Workbench Manual](https://dev.mysql.com/doc/workbench/en/)'
  - '[Deploy MySQL Workbench for Database Administration](/docs/guides/deploy-mysql-workbench-for-database-administration/)'
 tags: ["ubuntu","database","mysql"]
+deprecated: true
 ---
 
 MySQL Workbench is a feature-rich graphical tool used to model data, build SQL queries, manage MySQL servers, and more. This guide will show you how to install Workbench using the Ubuntu package manager.
diff --git a/docs/guides/databases/mysql/install-and-configure-phpmyadmin-on-debian-8/index.md b/docs/guides/databases/mysql/install-and-configure-phpmyadmin-on-debian-8/index.md
index 0e0456f88bd..1527bb2790f 100644
--- a/docs/guides/databases/mysql/install-and-configure-phpmyadmin-on-debian-8/index.md
+++ b/docs/guides/databases/mysql/install-and-configure-phpmyadmin-on-debian-8/index.md
@@ -15,6 +15,7 @@ relations:
         keywords:
             - distribution: Debian 8
 tags: ["debian","database","mysql","php"]
+deprecated: true
 ---
 
 phpMyAdmin is a web application that provides a GUI to aid in MySQL database administration. It supports multiple MySQL servers and is a robust and easy alternative to using the MySQL command line client.
diff --git a/docs/guides/databases/postgresql/how-to-install-postgresql-on-ubuntu-16-04/index.md b/docs/guides/databases/postgresql/how-to-install-postgresql-on-ubuntu-16-04/index.md
index 086433cdb85..152a99f9bc7 100644
--- a/docs/guides/databases/postgresql/how-to-install-postgresql-on-ubuntu-16-04/index.md
+++ b/docs/guides/databases/postgresql/how-to-install-postgresql-on-ubuntu-16-04/index.md
@@ -19,6 +19,7 @@ relations:
         key: install-postrgesql-database
         keywords:
             - distribution: Ubuntu 16.04
+deprecated: true
 ---
 
 ![How to Install PostgreSQL on Ubuntu 16.04](how-to-install-postgresql-on-ubuntu-16-04.jpg "How to Install PostgreSQL on Ubuntu 16.04")
diff --git a/docs/guides/databases/redis/how-to-install-a-redis-server-on-ubuntu-or-debian8/index.md b/docs/guides/databases/redis/how-to-install-a-redis-server-on-ubuntu-or-debian8/index.md
index 105e046d54a..6f46d07d506 100644
--- a/docs/guides/databases/redis/how-to-install-a-redis-server-on-ubuntu-or-debian8/index.md
+++ b/docs/guides/databases/redis/how-to-install-a-redis-server-on-ubuntu-or-debian8/index.md
@@ -21,6 +21,7 @@ relations:
         keywords:
             - distribution: Ubuntu/Debian
 tags: ["ubuntu","debian","database","nosql"]
+deprecated: true
 ---
 
 ![Redis Server on Ubuntu or Debian](install-redis-server-ubuntu-debian.png "Redis Server on Ubuntu or Debian")
diff --git a/docs/guides/development/java/install-java-on-debian/index.md b/docs/guides/development/java/install-java-on-debian/index.md
index 2258a4c90e3..e43e42bc2eb 100644
--- a/docs/guides/development/java/install-java-on-debian/index.md
+++ b/docs/guides/development/java/install-java-on-debian/index.md
@@ -19,6 +19,7 @@ relations:
         key: install-java
         keywords:
             - distribution: Debian 8
+deprecated: true
 ---
 
 Java is a powerful programming language. Software written in Java can be compiled and run on any system. Unlike Python or C, Java does not come pre-installed on Linode distribution images. This guide installs the OpenJDK 7 runtime environment and development kit in Debian 8. OpenJDK is the free and open-source implementation of the Java SE Development Kit.
diff --git a/docs/guides/development/java/install-java-on-ubuntu-16-04/index.md b/docs/guides/development/java/install-java-on-ubuntu-16-04/index.md
index 6ac560d7324..a3cb1de5f7d 100644
--- a/docs/guides/development/java/install-java-on-ubuntu-16-04/index.md
+++ b/docs/guides/development/java/install-java-on-ubuntu-16-04/index.md
@@ -21,6 +21,7 @@ relations:
         key: install-java
         keywords:
             - distribution: Ubuntu 16.04
+deprecated: true
 ---
 
 ![Java](Install_Oracle_Java.jpg)
diff --git a/docs/guides/development/ror/ruby-on-rails-apache-debian/index.md b/docs/guides/development/ror/ruby-on-rails-apache-debian/index.md
index 108ac0f8a80..1f16c53beba 100644
--- a/docs/guides/development/ror/ruby-on-rails-apache-debian/index.md
+++ b/docs/guides/development/ror/ruby-on-rails-apache-debian/index.md
@@ -21,6 +21,7 @@ relations:
         key: ruby-on-rails-apache
         keywords:
             - distribution: Debian 9
+deprecated: true
 ---
 
 ![Ruby on Rails with Apache on Debian](ruby_on_rails_with_apache_debian.jpg "Ruby on Rails with Apache on Debian")
diff --git a/docs/guides/development/ror/ruby-on-rails-nginx-debian/index.md b/docs/guides/development/ror/ruby-on-rails-nginx-debian/index.md
index fb63428a263..6fae564a95c 100644
--- a/docs/guides/development/ror/ruby-on-rails-nginx-debian/index.md
+++ b/docs/guides/development/ror/ruby-on-rails-nginx-debian/index.md
@@ -27,6 +27,7 @@ relations:
         key: ruby-on-rails-nginx
         keywords:
             - distribution: Debian 9
+deprecated: true
 ---
 
 ![Ruby on Rails with nginx on Debian](ruby_on_rails_with_nginx_debian_8_smg.png "Ruby on Rails with nginx on Debian 8")
diff --git a/docs/guides/development/version-control/install-gogs-on-debian/index.md b/docs/guides/development/version-control/install-gogs-on-debian/index.md
index d536568e87c..7f2dd9e897a 100644
--- a/docs/guides/development/version-control/install-gogs-on-debian/index.md
+++ b/docs/guides/development/version-control/install-gogs-on-debian/index.md
@@ -20,6 +20,7 @@ relations:
         key: install-gogs
         keywords:
             - distribution: Debian 9
+deprecated: true
 ---
 
 [Gogs](http://gogs.io) is a self-hosted Git service, similar to GitLab. It is written in [Go](http://golang.org) and aims to be the easiest and most painless way to set up self-hosted Git service. Gogs is one of the best choices if you need to set up a private Git repository, but don't want to pay for the private plans on other Git services.
diff --git a/docs/guides/development/version-control/manage-distributed-version-control-with-mercurial/index.md b/docs/guides/development/version-control/manage-distributed-version-control-with-mercurial/index.md
index 4e53da3e08a..015f589fbfd 100644
--- a/docs/guides/development/version-control/manage-distributed-version-control-with-mercurial/index.md
+++ b/docs/guides/development/version-control/manage-distributed-version-control-with-mercurial/index.md
@@ -13,6 +13,7 @@ external_resources:
  - '[HG Init, a Guide by Joel Spolsky](http://hginit.com/)'
 audiences: ["beginner"]
 tags: ["version control system"]
+deprecated: true
 ---
 
 [Mercurial](https://www.mercurial-scm.org/) is one of the leading distributed version control systems which allows software developers and teams of collaborators to work on a common code base without the need to rely on a centralized server or constant network connection. Mercurial runs on multiple platforms and can be used to manage code projects on many different operating systems.
diff --git a/docs/guides/email/clients/install-roundcube-on-ubuntu/index.md b/docs/guides/email/clients/install-roundcube-on-ubuntu/index.md
index 1139c3794c9..087e36fad9f 100644
--- a/docs/guides/email/clients/install-roundcube-on-ubuntu/index.md
+++ b/docs/guides/email/clients/install-roundcube-on-ubuntu/index.md
@@ -12,6 +12,7 @@ tags: ["ubuntu","postfix","email","lamp"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 external_resources:
   - '[Roundcube Homepage](https://roundcube.net/)'
+deprecated: true
 ---
 
 ![Install Roundcube on Ubuntu 16.04 LTS](Install_Roundcube_on_Ubuntu_16_04_smg.png "Install Roundcube on Ubuntu")
diff --git a/docs/guides/email/clients/install-squirrelmail-on-ubuntu-16-04-or-debian-8/index.md b/docs/guides/email/clients/install-squirrelmail-on-ubuntu-16-04-or-debian-8/index.md
index 2d92e39f9b0..fca59a2fd91 100644
--- a/docs/guides/email/clients/install-squirrelmail-on-ubuntu-16-04-or-debian-8/index.md
+++ b/docs/guides/email/clients/install-squirrelmail-on-ubuntu-16-04-or-debian-8/index.md
@@ -17,6 +17,7 @@ relations:
         keywords:
             - distribution: Debian 8
 aliases: ['/email/clients/install-squirrelmail-on-ubuntu-16-04-or-debian-8/']
+deprecated: true
 ---
 
 ![Install SquirrelMail on Ubuntu or Debian](Install_SquirrelMail_smg.jpg)
diff --git a/docs/guides/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/index.md b/docs/guides/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/index.md
index a0ee07f152d..afcbe42b4d6 100644
--- a/docs/guides/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/index.md
+++ b/docs/guides/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/index.md
@@ -21,6 +21,7 @@ relations:
         keywords:
             - distribution: Debian 8
 aliases: ['/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/']
+deprecated: true
 ---
 {{< note >}}
 We have created a [new version of this guide](/docs/guides/configure-spf-and-dkim-in-postfix-on-debian-9/) to run on Debian 9.
diff --git a/docs/guides/email/postfix/pflogsumm-for-postfix-monitoring-on-centos-6/index.md b/docs/guides/email/postfix/pflogsumm-for-postfix-monitoring-on-centos-6/index.md
index 3f0effc544d..a5ecb831662 100644
--- a/docs/guides/email/postfix/pflogsumm-for-postfix-monitoring-on-centos-6/index.md
+++ b/docs/guides/email/postfix/pflogsumm-for-postfix-monitoring-on-centos-6/index.md
@@ -11,6 +11,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/email/postfix/pflogsumm-for-postfix-monitoring-on-centos-6/','/email/postfix/pflogsumm-centos-6/']
 external_resources:
  - '[Pflogsumm](http://jimsun.linxnet.com/postfix_contrib.html)'
+deprecated: true
 ---
 
 ![Header image](Pflogsumm_or_Postfix_Monitoring_on_CentOS_smg.jpg "Pflogsumm for Postfix Monitoring on CentOS 6")
diff --git a/docs/guides/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/index.md b/docs/guides/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/index.md
index 92730c80c35..c33bc35f6d9 100644
--- a/docs/guides/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/index.md
+++ b/docs/guides/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/index.md
@@ -11,6 +11,7 @@ tags: ["ubuntu"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/applications/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/','/applications/game-servers/just-cause-2-multiplayer-on-ubuntu/','/game-servers/deploy-just-cause-2-multiplayer-server-on-ubuntu/']
 dedicated_cpu_link: true
+deprecated: true
 ---
 
 [Just Cause 2](http://www.justcause2.com/) is a single-player game published by Square Enix. Because it has no multiplayer mode, the modding community has created a multiplayer mod for the game that is quite popular. This guide will explain how to prepare your Linode, install SteamCMD and then install and configure Just Cause 2's multiplayer mod.
diff --git a/docs/guides/game-servers/host-a-terraria-server-on-your-linode/index.md b/docs/guides/game-servers/host-a-terraria-server-on-your-linode/index.md
index 51c3dba83e0..247cf25f068 100644
--- a/docs/guides/game-servers/host-a-terraria-server-on-your-linode/index.md
+++ b/docs/guides/game-servers/host-a-terraria-server-on-your-linode/index.md
@@ -14,6 +14,7 @@ external_resources:
  - '[Terraria Wiki: Setting up a Terraria Server](http://terraria.gamepedia.com/Guide:Setting_up_a_Terraria_server)'
 aliases: ['/game-servers/host-a-terraria-server-on-your-linode/','/applications/game-servers/host-a-terraria-server-on-your-linode/']
 dedicated_cpu_link: true
+deprecated: true
 ---
 
 ![Hosta a Terraria Server on Your Linode](terraria-server.png "Hosta a Terraria Server on Your Linode")
diff --git a/docs/guides/game-servers/install-dont-starve-together-game-server-on-ubuntu/index.md b/docs/guides/game-servers/install-dont-starve-together-game-server-on-ubuntu/index.md
index 2366d13caf2..926066ce408 100644
--- a/docs/guides/game-servers/install-dont-starve-together-game-server-on-ubuntu/index.md
+++ b/docs/guides/game-servers/install-dont-starve-together-game-server-on-ubuntu/index.md
@@ -11,6 +11,7 @@ tags: ["debian", "ubuntu"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/applications/game-servers/dont-starve-together-on-ubuntu/','/game-servers/install-dont-starve-together-game-server-on-ubuntu/','/applications/game-servers/install-dont-starve-together-game-server-on-ubuntu/']
 dedicated_cpu_link: true
+deprecated: true
 ---
 
 ![Header image](Install_Dont_Starve_Together_Game_Server_on_Ubuntu_smg.jpg "Install Don't Starve Together Game Server on Ubuntu 14.04")
diff --git a/docs/guides/game-servers/pocketmine-server-on-debian-7/index.md b/docs/guides/game-servers/pocketmine-server-on-debian-7/index.md
index f9b96ade1de..617ee74c4d6 100644
--- a/docs/guides/game-servers/pocketmine-server-on-debian-7/index.md
+++ b/docs/guides/game-servers/pocketmine-server-on-debian-7/index.md
@@ -14,6 +14,7 @@ external_resources:
  - '[PocketMine Documentation](http://pocketmine-mp.readthedocs.org/en/latest/)'
 aliases: ['/game-servers/pocketmine-server-on-debian-7/','/applications/game-servers/pocketmine-server-on-debian-7/']
 dedicated_cpu_link: true
+deprecated: true
 ---
 
 PocketMine is a third party server for the MineCraft - Pocket Edition game for [Android](https://play.google.com/store/apps/details?id=com.mojang.minecraftpe) and [iOS](https://itunes.apple.com/us/app/minecraft-pocket-edition/id479516143?mt=8). It features plugin support, allowing you to customize your gameplay with others. This guide details installing PocketMine on a Linode running Debian 7.
diff --git a/docs/guides/networking/nfs/how-to-mount-nfs-shares-on-debian-9/index.md b/docs/guides/networking/nfs/how-to-mount-nfs-shares-on-debian-9/index.md
index f3c6f891763..c56e3972e85 100644
--- a/docs/guides/networking/nfs/how-to-mount-nfs-shares-on-debian-9/index.md
+++ b/docs/guides/networking/nfs/how-to-mount-nfs-shares-on-debian-9/index.md
@@ -11,6 +11,7 @@ keywords: ["NFS", "network file system"]
 aliases: ['/networking/how-to-mount-nfs-shares-on-debian-9/','/networking/how-to-mount-nfs-shares-on-debian-8/','/networking/nfs/how-to-mount-nfs-shares-on-debian-9/','/networking/basic-nfs-configuration-on-debian-7/','/networking/file-transfer/basic-nfs-debian/']
 tags: ["networking","debian"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+deprecated: true
 ---
 
 ![How to Mount NFS Shares on Debian 9](mount-nfs-shares-deb-9-title.jpg "How to Mount NFS Shares on Debian 9")
diff --git a/docs/guides/networking/vpn/set-up-a-hardened-openvpn-server/index.md b/docs/guides/networking/vpn/set-up-a-hardened-openvpn-server/index.md
index cee94c15676..843e05a4786 100644
--- a/docs/guides/networking/vpn/set-up-a-hardened-openvpn-server/index.md
+++ b/docs/guides/networking/vpn/set-up-a-hardened-openvpn-server/index.md
@@ -12,6 +12,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/networking/vpn/set-up-a-hardened-openvpn-server-on-debian-8/','/networking/vpn/set-up-a-hardened-openvpn-server/']
 external_resources:
  - '[Official OpenVPN Documentation](https://openvpn.net/index.php/open-source/documentation/howto.html)'
+deprecated: true
 ---
 
 [OpenVPN](https://openvpn.net/) is a tool for creating network tunnels between groups of computers that are not on the same local network. This is useful to remotely access services on a network or computer without making those services publicly accessible. When integrated with OpenSSL, OpenVPN encrypts all VPN traffic providing a secure connection between machines.
diff --git a/docs/guides/security/security-patches/disabling-sslv3-for-poodle/index.md b/docs/guides/security/security-patches/disabling-sslv3-for-poodle/index.md
index ad88cea7142..4324ba863a3 100644
--- a/docs/guides/security/security-patches/disabling-sslv3-for-poodle/index.md
+++ b/docs/guides/security/security-patches/disabling-sslv3-for-poodle/index.md
@@ -10,6 +10,7 @@ keywords: ["sslv3", "poodle", "security", "patch", "ubuntu", "debian", "centos",
 tags: ["web server","security","ssl"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/security/security-patches/disabling-sslv3-for-poodle/']
+deprecated: true
 ---
 
 ![Disabling_sslv3_for_poodle](Disabling_SSLv3_for_POODLE_smg.jpg)
diff --git a/docs/guides/security/security-patches/meltdown-and-spectre/index.md b/docs/guides/security/security-patches/meltdown-and-spectre/index.md
index c25b3f076da..5b76bc117df 100644
--- a/docs/guides/security/security-patches/meltdown-and-spectre/index.md
+++ b/docs/guides/security/security-patches/meltdown-and-spectre/index.md
@@ -16,6 +16,7 @@ external_resources:
   - '[Reboot Survival Guide](/docs/guides/reboot-survival-guide/)'
   - '[Linode Blog: CPU Vulnerabilities: Meltdown & Spectre](https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre/)'
 tags: ["security"]
+deprecated: true
 ---
 
 ## Summary
diff --git a/docs/guides/security/security-patches/patching-bash-for-the-shellshock-vulnerability/index.md b/docs/guides/security/security-patches/patching-bash-for-the-shellshock-vulnerability/index.md
index dbd91313eb1..5067274ebc4 100644
--- a/docs/guides/security/security-patches/patching-bash-for-the-shellshock-vulnerability/index.md
+++ b/docs/guides/security/security-patches/patching-bash-for-the-shellshock-vulnerability/index.md
@@ -10,6 +10,7 @@ keywords: ["bash", "shellshock", "security", "patch", "ubuntu", "debian", "cento
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 tags: ["security"]
 aliases: ['/security/security-patches/patching-bash-for-the-shellshock-vulnerability/']
+deprecated: true
 ---
 
 Shellshock, or Bashdoor, is a vulnerability that was discovered on September 12th, 2014 and embargoed until September 24th when it was assigned the CVE identifier [CVE-2014-6271](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271). The vulnerability pertains to Bash, which is a widely used Unix shell. This vulnerability affects all Linux distributions and allows remote execution of commands using environment variables.
diff --git a/docs/guides/security/security-patches/patching-glibc-for-the-ghost-vulnerability/index.md b/docs/guides/security/security-patches/patching-glibc-for-the-ghost-vulnerability/index.md
index dceac2b8fef..2417f8ba3cf 100644
--- a/docs/guides/security/security-patches/patching-glibc-for-the-ghost-vulnerability/index.md
+++ b/docs/guides/security/security-patches/patching-glibc-for-the-ghost-vulnerability/index.md
@@ -12,6 +12,7 @@ external_resources:
  - '[CVE-2015-0235](http://www.openwall.com/lists/oss-security/2015/01/27/9)'
 tags: ["security"]
 aliases: ['/security/security-patches/patching-glibc-for-the-ghost-vulnerability/']
+deprecated: true
 ---
 
 GHOST is a vulnerability that was announced on January 27th 2015, which affects the glibc library on Linux systems.  This vulnerability affects all Linux distributions running versions of glibc older than 2.18, and exploits a buffer overflow in the `__nss_hostname_digits_dots()` function. This guide will tell you how to safely upgrade your Linux distributions and secure your Linode against the GHOST vulnerability.
diff --git a/docs/guides/security/security-patches/patching-openssl-for-the-heartbleed-vulnerability/index.md b/docs/guides/security/security-patches/patching-openssl-for-the-heartbleed-vulnerability/index.md
index 6a57e76a3d7..d926f42617f 100644
--- a/docs/guides/security/security-patches/patching-openssl-for-the-heartbleed-vulnerability/index.md
+++ b/docs/guides/security/security-patches/patching-openssl-for-the-heartbleed-vulnerability/index.md
@@ -12,6 +12,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/security/patching-openssl-for-the-heartbleed-vulnerability/','/security/security-patches/patching-openssl-for-the-heartbleed-vulnerability/','/security/openssl-heartbleed/']
 external_resources:
  - '[Heartbleed.com](http://heartbleed.com/)'
+deprecated: true
 ---
 
 ![Patching OpenSSL for the Heartbleed Vulnerability](Patching_OpenSSL_for_the_Heartbleed_Vulnerability_smg.png "Patching OpenSSL for the Heartbleed Vulnerability")
diff --git a/docs/guides/security/upgrading/upgrade-to-ubuntu-16-04/index.md b/docs/guides/security/upgrading/upgrade-to-ubuntu-16-04/index.md
index 2a90abf46c1..8142a694cd8 100644
--- a/docs/guides/security/upgrading/upgrade-to-ubuntu-16-04/index.md
+++ b/docs/guides/security/upgrading/upgrade-to-ubuntu-16-04/index.md
@@ -15,6 +15,7 @@ relations:
         keywords:
             - distribution: Ubuntu 16.04
 aliases: ['/security/upgrading/upgrade-to-ubuntu-16-04/']
+deprecated: true
 ---
 
 ![Upgrade to Ubuntu 16.04](How_to_Upgrade_to_Ubuntu_smg.jpg)
diff --git a/docs/guides/uptime/monitoring/how-to-install-and-configure-graylog2-on-debian-9/index.md b/docs/guides/uptime/monitoring/how-to-install-and-configure-graylog2-on-debian-9/index.md
index ce2c425be4d..3c6ef3bc7c4 100644
--- a/docs/guides/uptime/monitoring/how-to-install-and-configure-graylog2-on-debian-9/index.md
+++ b/docs/guides/uptime/monitoring/how-to-install-and-configure-graylog2-on-debian-9/index.md
@@ -15,6 +15,7 @@ external_resources:
 - '[Elasticsearch](https://www.elastic.co/guide/index.html)'
 dedicated_cpu_link: true
 aliases: ['/uptime/monitoring/how-to-install-and-configure-graylog2-on-debian-9/']
+deprecated: true
 ---
 
 ## What is Graylog?
diff --git a/docs/guides/uptime/monitoring/install-icinga2-monitoring-on-debian-9/index.md b/docs/guides/uptime/monitoring/install-icinga2-monitoring-on-debian-9/index.md
index e1fdd9d0f90..6c0cebf1557 100644
--- a/docs/guides/uptime/monitoring/install-icinga2-monitoring-on-debian-9/index.md
+++ b/docs/guides/uptime/monitoring/install-icinga2-monitoring-on-debian-9/index.md
@@ -12,6 +12,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 external_resources:
  - '[Official Icinga Documentation](https://www.icinga.com/docs/icinga2/latest/doc/01-about/)'
 aliases: ['/uptime/monitoring/install-icinga2-monitoring-on-debian-9/']
+deprecated: true
 ---
 
 ![Install Icinga 2 Monitoring on Debian 9](Icinga2.jpg "Install Icinga 2 Monitoring on Debian 9")
diff --git a/docs/guides/uptime/monitoring/install-nagios-4-on-ubuntu-debian-8/index.md b/docs/guides/uptime/monitoring/install-nagios-4-on-ubuntu-debian-8/index.md
index cf7b5b7c1ae..65941405050 100644
--- a/docs/guides/uptime/monitoring/install-nagios-4-on-ubuntu-debian-8/index.md
+++ b/docs/guides/uptime/monitoring/install-nagios-4-on-ubuntu-debian-8/index.md
@@ -17,6 +17,7 @@ relations:
         key: install-nagios-monitoring
         keywords:
             - distribution: Debian 8
+deprecated: true
 ---
 
 ![Install Nagios 4 on Ubuntu and Debian 8](Install_Nagios_4_smg.jpg)
diff --git a/docs/guides/web-servers/apache/apache-web-server-debian-8/index.md b/docs/guides/web-servers/apache/apache-web-server-debian-8/index.md
index 27929566039..08690bd542e 100644
--- a/docs/guides/web-servers/apache/apache-web-server-debian-8/index.md
+++ b/docs/guides/web-servers/apache/apache-web-server-debian-8/index.md
@@ -18,6 +18,7 @@ relations:
         key: install-apache-server
         keywords:
             - distribution: Debian 8
+deprecated: true
 ---
 
 ![How to Install and Configure Apache Web Server on Debian 8](Apache_Web_Server_on_Debian_8_Jessie_smg.jpg)
diff --git a/docs/guides/web-servers/apache/install-php-fpm-and-apache-on-debian-8/index.md b/docs/guides/web-servers/apache/install-php-fpm-and-apache-on-debian-8/index.md
index 9187f2ac86d..ebd16ad19ee 100644
--- a/docs/guides/web-servers/apache/install-php-fpm-and-apache-on-debian-8/index.md
+++ b/docs/guides/web-servers/apache/install-php-fpm-and-apache-on-debian-8/index.md
@@ -13,6 +13,7 @@ aliases: ['/websites/apache/install-php-fpm-and-apache-on-debian-8/','/web-serve
 external_resources:
  - '[The PHP Homepage](http://php.net/)'
  - '[FastCGI Process Manager](http://php.net/manual/en/install.fpm.configuration.php)'
+deprecated: true
 ---
 
 PHP-FPM is an implementation of the FastCGI protocol for PHP. This guide covers installing PHP-FPM for Apache on Debian 8 (Jessie).
diff --git a/docs/guides/web-servers/lamp/lamp-on-debian-8-jessie/index.md b/docs/guides/web-servers/lamp/lamp-on-debian-8-jessie/index.md
index 0355237d1e1..737b2e2b77c 100644
--- a/docs/guides/web-servers/lamp/lamp-on-debian-8-jessie/index.md
+++ b/docs/guides/web-servers/lamp/lamp-on-debian-8-jessie/index.md
@@ -20,6 +20,7 @@ relations:
         key: install-lamp-stack
         keywords:
             - distribution: Debian 8
+deprecated: true
 ---
 
 Setting up a LAMP (Linux, Apache, MySql, PHP) stack on your server will allow for the creation and hosting of websites and web applications. This guide shows you how to install a LAMP stack on Debian 8 (Jessie).
diff --git a/docs/guides/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04/index.md b/docs/guides/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04/index.md
index 3cfbeb6b613..d57a4aaf4ed 100644
--- a/docs/guides/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04/index.md
+++ b/docs/guides/web-servers/lemp/how-to-install-a-lemp-server-on-ubuntu-16-04/index.md
@@ -15,6 +15,7 @@ relations:
         key: install-lemp-stack
         keywords:
             - distribution: Ubuntu 16.04
+deprecated: true
 ---
 
 ![LEMP Server on Ubuntu 16.04](lemp-server-on-ubuntu-1604.png "LEMP Server on Ubuntu 16.04")
diff --git a/docs/guides/web-servers/lemp/install-a-lemp-stack-on-debian/index.md b/docs/guides/web-servers/lemp/install-a-lemp-stack-on-debian/index.md
index 9df793e01b2..01d57d90e81 100644
--- a/docs/guides/web-servers/lemp/install-a-lemp-stack-on-debian/index.md
+++ b/docs/guides/web-servers/lemp/install-a-lemp-stack-on-debian/index.md
@@ -15,6 +15,7 @@ relations:
         key: install-lemp-stack
         keywords:
             - distribution: Debian 9
+deprecated: true
 ---
 
 ## What is a LEMP Stack?
diff --git a/docs/guides/web-servers/lighttpd/use-lighttpd-web-server-on-ubuntu-16-04/index.md b/docs/guides/web-servers/lighttpd/use-lighttpd-web-server-on-ubuntu-16-04/index.md
index 1395c233f5d..8c998c857f3 100644
--- a/docs/guides/web-servers/lighttpd/use-lighttpd-web-server-on-ubuntu-16-04/index.md
+++ b/docs/guides/web-servers/lighttpd/use-lighttpd-web-server-on-ubuntu-16-04/index.md
@@ -21,6 +21,7 @@ relations:
         key: install-lighttpd
         keywords:
             - distribution: Ubuntu 16.04
+deprecated: true
 ---
 
 Lighttpd provides a lightweight web server that is capable of serving large loads while using less memory than servers like Apache. It is commonly deployed on high traffic sites, including WhatsApp and xkcd.
diff --git a/docs/guides/websites/cms/drupal/managing-web-content-with-drupal-7/index.md b/docs/guides/websites/cms/drupal/managing-web-content-with-drupal-7/index.md
index 675309e72be..8a9869f3b3c 100644
--- a/docs/guides/websites/cms/drupal/managing-web-content-with-drupal-7/index.md
+++ b/docs/guides/websites/cms/drupal/managing-web-content-with-drupal-7/index.md
@@ -10,6 +10,7 @@ keywords: ["drupal", "cms", "web framework", "web application", "php", "content
 tags: ["drupal","cms","lamp"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/websites/cms/drupal/managing-web-content-with-drupal-7/','/websites/cms/managing-web-content-with-drupal-7/']
+deprecated: true
 ---
 
 Drupal is an advanced and powerful content management framework, built on the PHP scripting language and supported by a [database](/docs/databases/) engine like [MySQL](/docs/databases/mysql/). Drupal provides a flexible system that can be used to manage websites of all different types and profiles. Drupal is capable of providing the tools necessary to create rich, interactive "community" websites with forums, user blogs, and private messaging. Drupal can also provide support for multifaceted personal publishing projects and can power podcasts, blogs, and knowledge-based systems, all within a single, unified platform.
diff --git a/docs/guides/websites/cms/ghost/how-to-install-ghost-cms-on-ubuntu-16-04/index.md b/docs/guides/websites/cms/ghost/how-to-install-ghost-cms-on-ubuntu-16-04/index.md
index fe41a83766a..17526c9fdfc 100644
--- a/docs/guides/websites/cms/ghost/how-to-install-ghost-cms-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/cms/ghost/how-to-install-ghost-cms-on-ubuntu-16-04/index.md
@@ -19,6 +19,7 @@ relations:
         key: how-to-install-ghost-cms
         keywords:
            - distribution: Ubuntu 16.04
+deprecated: true
 ---
 
 ![How to Install Ghost CMS on Ubuntu 16.04](ghost-blog-ubuntu-16-04-title-graphic.png "How to Install Ghost CMS on Ubuntu 16.04")
diff --git a/docs/guides/websites/cms/how-to-install-a-webmin-control-panel-and-modules/index.md b/docs/guides/websites/cms/how-to-install-a-webmin-control-panel-and-modules/index.md
index e565323c6b5..652458dba68 100644
--- a/docs/guides/websites/cms/how-to-install-a-webmin-control-panel-and-modules/index.md
+++ b/docs/guides/websites/cms/how-to-install-a-webmin-control-panel-and-modules/index.md
@@ -16,6 +16,7 @@ external_resources:
  - '[Webmin Documentation](http://www.webmin.com/docs.html)'
  - '[Webmin Modules](http://www.webmin.com/standard.html)'
  - '[Webmin FAQ](http://www.webmin.com/faq.html)'
+deprecated: true
 ---
 
 ![How to Install a Webmin Control Panel and Modules on Ubuntu](Webmin_Control_Panel_smg.jpg)
diff --git a/docs/guides/websites/cms/solr/add-a-custom-search-to-your-site-with-solr/index.md b/docs/guides/websites/cms/solr/add-a-custom-search-to-your-site-with-solr/index.md
index 176f9e7dce9..f2aaa2c40be 100644
--- a/docs/guides/websites/cms/solr/add-a-custom-search-to-your-site-with-solr/index.md
+++ b/docs/guides/websites/cms/solr/add-a-custom-search-to-your-site-with-solr/index.md
@@ -11,6 +11,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 external_resources:
   - '[Apache Solr Reference Guide](https://lucene.apache.org/solr/guide/6_6/)'
 aliases: ['/websites/cms/solr/add-a-custom-search-to-your-site-with-solr/','/websites/cms/add-a-custom-search-to-your-site-with-solr/']
+deprecated: true
 ---
 
 Apache Solr is an open source search platform that provides administrators with a customizable and scalable solution for managing online content. Solr can be configured to index all uploaded data, resulting in fast search results, whether used enterprise-wide or with a single website. In addition to a built-in web control interface, developers can also link access via a client API.
diff --git a/docs/guides/websites/cms/solr/turbocharge-wordpress-search-with-solr/index.md b/docs/guides/websites/cms/solr/turbocharge-wordpress-search-with-solr/index.md
index 7f7b8db9ea3..ae543ecf121 100644
--- a/docs/guides/websites/cms/solr/turbocharge-wordpress-search-with-solr/index.md
+++ b/docs/guides/websites/cms/solr/turbocharge-wordpress-search-with-solr/index.md
@@ -9,6 +9,7 @@ keywords: ["wordpress", "search", "solr", "ubuntu", "debian"]
 tags: ["ubuntu","wordpress","cms","debian"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/websites/cms/solr/turbocharge-wordpress-search-with-solr/','/websites/cms/turbocharge-wordpress-search-with-solr/']
+deprecated: true
 ---
 
 The standard search that is built into WordPress does not provide the best search experience you can offer your visitors, given its inability to suggest search phrases, catch typos, understand word variations, organize and filter results, and index documents for search results. *Full text search engines* often offer these features and **Apache Solr** is a free, open-source option that does.
diff --git a/docs/guides/websites/cms/wordpress/how-to-install-wordprress-using-wp-cli-on-debian-9/index.md b/docs/guides/websites/cms/wordpress/how-to-install-wordprress-using-wp-cli-on-debian-9/index.md
index b9627c6b920..597f6a21d29 100644
--- a/docs/guides/websites/cms/wordpress/how-to-install-wordprress-using-wp-cli-on-debian-9/index.md
+++ b/docs/guides/websites/cms/wordpress/how-to-install-wordprress-using-wp-cli-on-debian-9/index.md
@@ -20,6 +20,7 @@ relations:
         keywords:
            - distribution: Debian 9
 aliases: ['/websites/cms/wp-cli/how-to-install-wordprress-using-wp-cli-on-debian-9/','/websites/cms/wordpress/how-to-install-wordprress-using-wp-cli-on-debian-9/']
+deprecated: true
 ---
 
 WordPress is well-known for its rich content management feature set, ease of use, and quick installation time. The [WordPress command line interface (WP-CLI)](https://wp-cli.org/) provides useful commands and utilities to install, configure, and manage a WordPress site. This guide walks you through some common tasks you can complete using the WP-CLI.
diff --git a/docs/guides/websites/cms/wordpress/install-wordpress-on-ubuntu-16-04/index.md b/docs/guides/websites/cms/wordpress/install-wordpress-on-ubuntu-16-04/index.md
index 898da4a197f..e418d9b7f86 100644
--- a/docs/guides/websites/cms/wordpress/install-wordpress-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/cms/wordpress/install-wordpress-on-ubuntu-16-04/index.md
@@ -18,6 +18,7 @@ relations:
         keywords:
            - distribution: Ubuntu 16.04
 aliases: ['/websites/cms/install-wordpress-on-ubuntu-16-04/','/websites/cms/wordpress/install-wordpress-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 In this guide, you'll learn to how to install WordPress on a Linode running Ubuntu 16.04. WordPress is a popular dynamic content management system focused on blogs. WordPress can be deployed on a LAMP or LEMP stack, and features an extensive plugin framework and theme system that allows site owners and developers to use its simple, yet powerful publishing tools.
diff --git a/docs/guides/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04/index.md b/docs/guides/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04/index.md
index 2246207701a..77d51ffae71 100644
--- a/docs/guides/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04/index.md
@@ -12,6 +12,7 @@ keywords: ["prestashop", "ecommerce", "cms"]
 tags: ["cms", "lamp", "ssl", "ubuntu"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/websites/ecommerce/how-to-install-prestashop-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 ![How to Install PrestaShop of Ubuntu 16.04 LTS](PrestaShop.jpg)
diff --git a/docs/guides/websites/ecommerce/install-magento-on-ubuntu-16-04/index.md b/docs/guides/websites/ecommerce/install-magento-on-ubuntu-16-04/index.md
index 429917c1b98..384c399f386 100644
--- a/docs/guides/websites/ecommerce/install-magento-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/ecommerce/install-magento-on-ubuntu-16-04/index.md
@@ -17,6 +17,7 @@ relations:
         keywords:
            - distribution: Ubuntu 16.04
 aliases: ['/websites/ecommerce/install-magento-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 In this guide you'll learn how to install Magento on Ubuntu 16.04. Magento Community Edition (CE) is a free, open-source e-commerce platform. It's one of the most popular solutions for self-hosted online stores due to its simple yet powerful admin panel and large developer community.
diff --git a/docs/guides/websites/erp/install-an-odoo-11-stack-on-ubuntu-16-04/index.md b/docs/guides/websites/erp/install-an-odoo-11-stack-on-ubuntu-16-04/index.md
index 737ccaa257a..a903161cb6b 100644
--- a/docs/guides/websites/erp/install-an-odoo-11-stack-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/erp/install-an-odoo-11-stack-on-ubuntu-16-04/index.md
@@ -17,6 +17,7 @@ external_resources:
   - '[Install an SSL certificate with LetsEncrypt](/docs/guides/install-lets-encrypt-to-create-ssl-certificates/)'
   - '[How to Set up tinc, a Peer-to-Peer VPN](/docs/guides/how-to-set-up-tinc-peer-to-peer-vpn/)'
   - '[Using Terraform to Provision Linode Environments](/docs/guides/how-to-build-your-infrastructure-using-terraform-and-linode/)'
+deprecated: true
 ---
 
 ![Install an Odoo 11 Stack on Ubuntu 16.04 using Linode](install-an-odoo-11-stack-on-ubuntu-16-04-using-linode.png "Odoo 11 on Ubuntu 16.04 Title Graphic")
diff --git a/docs/guides/websites/erp/install-odoo-10-on-ubuntu-16-04/index.md b/docs/guides/websites/erp/install-odoo-10-on-ubuntu-16-04/index.md
index 79a6fa040d1..4673e77b964 100644
--- a/docs/guides/websites/erp/install-odoo-10-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/erp/install-odoo-10-on-ubuntu-16-04/index.md
@@ -13,6 +13,7 @@ aliases: ['/websites/cms/install-odoo-10-on-ubuntu-16-04/','/websites/erp/instal
 external_resources:
  - '[Odoo User Documentation](https://www.odoo.com/documentation/user/10.0/)'
  - '[Odoo Developer Documentation](https://www.odoo.com/documentation/10.0)'
+deprecated: true
 ---
 
 [Odoo](https://www.odoo.com/) (formerly known as OpenERP) is an open-source suite of business applications including customer relationship management (CRM), sales pipeline, project management, manufacturing, invoicing, accounting, eCommerce, and inventory tools, just to name a few. There are thirty-four main applications created by the Odoo team and more than 5,500 developed by community members, covering a wide range of business needs.
diff --git a/docs/guides/websites/erp/install-odoo-9-erp-on-ubuntu-14-04/index.md b/docs/guides/websites/erp/install-odoo-9-erp-on-ubuntu-14-04/index.md
index 13ab755fb39..fcfbd332f24 100644
--- a/docs/guides/websites/erp/install-odoo-9-erp-on-ubuntu-14-04/index.md
+++ b/docs/guides/websites/erp/install-odoo-9-erp-on-ubuntu-14-04/index.md
@@ -12,6 +12,7 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/websites/erp/install-odoo-9-erp-on-ubuntu-14-04/','/websites/cms/install-odoo-9-erp-on-ubuntu-14-04/']
 external_resources:
  - '[Odoo User Documentation](https://doc.odoo.com/book/)'
+deprecated: true
 ---
 
 [Odoo](https://www.odoo.com/) (formerly known as OpenERP) is an open-source suite of business applications including: Customer Relationship Management, Sales Pipeline, Project Management, Manufacturing, Invoicing , Accounting, eCommerce and Inventory just to name a few. There are 31 main applications created by Odoo team and over 4,500+ developed by community members covering a wide range of business needs.
diff --git a/docs/guides/websites/forums/install-a-simple-machines-forum-on-your-website/index.md b/docs/guides/websites/forums/install-a-simple-machines-forum-on-your-website/index.md
index d79c5691410..ee2ce071443 100644
--- a/docs/guides/websites/forums/install-a-simple-machines-forum-on-your-website/index.md
+++ b/docs/guides/websites/forums/install-a-simple-machines-forum-on-your-website/index.md
@@ -15,7 +15,7 @@ external_resources:
  - '[Modifications, Styles, and Upgrades](http://custom.simplemachines.org/)'
  - '[Functions Database](http://support.simplemachines.org/function_db/)'
  - '[SMF Community Forum](http://www.simplemachines.org/community/index.php)'
-deprecated: false
+deprecated: true
 ---
 
 Simple Machines Forum (SMF) is a popular forum solution for small- to large-sized communities that offers a variety of features. With its modular design and flexibility, users can create their own plugins to modify the behavior of SMF in any way they wish.
diff --git a/docs/guides/websites/forums/install-and-run-askbot-on-ubuntu-16-04/index.md b/docs/guides/websites/forums/install-and-run-askbot-on-ubuntu-16-04/index.md
index 082236e7b9d..0528b87bee7 100644
--- a/docs/guides/websites/forums/install-and-run-askbot-on-ubuntu-16-04/index.md
+++ b/docs/guides/websites/forums/install-and-run-askbot-on-ubuntu-16-04/index.md
@@ -14,6 +14,7 @@ external_resources:
  - '[AskBot Official Q&A Forum](https://askbot.org)'
  - '[AskBot Official Website](https://askbot.com)'
 aliases: ['/websites/forums/install-and-run-askbot-on-ubuntu-16-04/']
+deprecated: true
 ---
 
 ![AskBot with Let's Encrypt on Ubuntu](AskBot.jpg)
diff --git a/docs/guides/websites/wikis/dokuwiki-engine/index.md b/docs/guides/websites/wikis/dokuwiki-engine/index.md
index 36ca16d941a..068f2b69a56 100644
--- a/docs/guides/websites/wikis/dokuwiki-engine/index.md
+++ b/docs/guides/websites/wikis/dokuwiki-engine/index.md
@@ -13,6 +13,7 @@ aliases: ['/web-applications/wikis/dokuwiki/','/websites/wikis/dokuwiki-engine/'
 external_resources:
  - '[The Doku Wiki Project Home Page](http://www.dokuwiki.org/dokuwiki)'
  - '[Doku Wiki Manual](http://www.dokuwiki.org/manual)'
+deprecated: true
 ---
 
 DokuWiki is a flexible and extensible wiki engine that aims to be easy to manage while providing a rich feature set to enable collaborative document editing and creation for users of all skill levels and technical inclinations. DokuWiki stores wiki pages in text files on the web-server rather than in a database management system, which increases data usability and portability for moderately sized wiki projects without requiring the system resources to power a relational database server.
diff --git a/docs/products/compute/compute-instances/_index.md b/docs/products/compute/compute-instances/_index.md
index 4c0f384af35..b3cf51a1f86 100644
--- a/docs/products/compute/compute-instances/_index.md
+++ b/docs/products/compute/compute-instances/_index.md
@@ -49,6 +49,7 @@ Linode bundles the following services with all Compute Instances:
 - Domain management through our [DNS Manager](https://www.linode.com/products/dns-manager/)
 - Seamless firewall management with [Cloud Firewalls](https://www.linode.com/products/cloud-firewall/)
 - Private Layer 2 networks with [VLANs](https://www.linode.com/products/vlan/)
+- Physical placement of your Compute Instances in a data center with [Placement Groups](/docs/products/compute/compute-instances/guides/placement-groups/)
 - Metrics and monitoring through the [Cloud Manager](https://www.linode.com/products/monitoring/) and [Longview](/docs/products/tools/longview/) (free plan)
 - Reusable deployment scripts through [StackScripts](https://www.linode.com/products/stackscripts/)
 
diff --git a/docs/products/compute/compute-instances/guides/_index.md b/docs/products/compute/compute-instances/guides/_index.md
index ca9641bee80..ef4eb4ec884 100644
--- a/docs/products/compute/compute-instances/guides/_index.md
+++ b/docs/products/compute/compute-instances/guides/_index.md
@@ -2,7 +2,7 @@
 title: Guides
 title_meta: "Guides and Tutorials for Compute Instances"
 description: "A collection of guides to help you start deploying Compute Instances and using them to host your web applications and Cloud workloads"
-modified: 2024-01-03
+modified: 2024-06-20
 tab_group_main:
     weight: 30
 aliases: ['/products/compute/shared-linodes/guides/','/products/compute/shared-cpu/guides/','/products/compute/gpu/guides/','/products/compute/dedicated-cpu/guides/','/products/compute/high-memory/guides/']
@@ -22,6 +22,7 @@ aliases: ['/products/compute/shared-linodes/guides/','/products/compute/shared-c
 - [Access Your Desktop Environment Using Glish (Linode Graphical Shell)](/docs/products/compute/compute-instances/guides/glish/)
 - [Reset Root Password](/docs/products/compute/compute-instances/guides/reset-root-password/)
 - [Clone a Compute Instance](/docs/products/compute/compute-instances/guides/clone-instance/)
+- [Physically Group Compute Instances to Meet Your Needs](/docs/products/compute/compute-instances/guides/placement-groups)
 - [Initiate a Cross Data Center Migration](/docs/products/compute/compute-instances/guides/migrate-to-different-dc/)
 - [Configure Email Alerts for Resource Usage on Compute Instances](/docs/products/compute/compute-instances/guides/resource-usage-email-alerts/)
 
diff --git a/docs/products/compute/compute-instances/guides/clone-instance/index.md b/docs/products/compute/compute-instances/guides/clone-instance/index.md
index 362240b2402..8227669c0cb 100644
--- a/docs/products/compute/compute-instances/guides/clone-instance/index.md
+++ b/docs/products/compute/compute-instances/guides/clone-instance/index.md
@@ -16,7 +16,7 @@ Linode's cloning feature allows you to duplicate a Compute Instance's disks (and
 This process copies all disks and configuration profiles to a newly created Compute Instance on your account.
 
 {{< note >}}
-Before continuing, it's recommended to power off the instance you would like to clone. This helps prevent data corruption.
+Before continuing, you should power off the instance you want to clone. This helps prevent data corruption.
 {{< /note >}}
 
 1. Log in to the [Cloud Manager](https://cloud.linode.com).
@@ -30,7 +30,7 @@ Before continuing, it's recommended to power off the instance you would like to
 1. Under **Select Linode to Clone From**, search for and select the instance you wish to clone. If the selected instance is running, **Power Off** appears to the right.
 
 1. To help prevent data corruption during cloning, click **Power Off**.
-   
+
     {{< note >}}
     If you're using a mobile device, available instances appear as cards without the Power Off option. To power off an instance from a mobile device, go to the instance's details page.
     {{< /note >}}
@@ -38,7 +38,9 @@ Before continuing, it's recommended to power off the instance you would like to
 1. Complete the remainder of the form. Enter a label and select the region, the plan, and other options for the new Compute Instance.
 
     {{< note >}}
-    The plan's storage must be greater than the combined disk size of the original instance. If you wish to select a plan with less storage, you may need to [resize your disks](/docs/products/compute/compute-instances/guides/disks-and-storage/) before cloning.
+    - The plan's storage must be greater than the combined disk size of the original instance. If you wish to select a plan with less storage, you may need to [resize your disks](/docs/products/compute/compute-instances/guides/disks-and-storage/) before cloning.
+
+    - If the target Compute Instance is in a [placement group](/docs/products/compute/compute-instances/guides/placement-groups/), the clone isn't automatically included in the same placement group. You need to specify a placement group to include it in. The target placement group needs to have capacity to include a cloned Compute Instance and it needs to be in the same data center as the clone.
     {{< /note >}}
 
 1. Click the **Create Linode** button to start the cloning process. Cloning a Compute Instance can be much longer than creating a new instance based on a distribution image or custom image. The length of time depends on the size of the disks, among other factors. To keep track of the cloning progress, a status bar is displayed above the original Compute Instance with the percentage of completion.
diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/add_disk.png b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/add_disk.png
index ccbc84b3c27..7f444695eff 100644
Binary files a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/add_disk.png and b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/add_disk.png differ
diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/block-device-assignment.png b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/block-device-assignment.png
index d106a69ca44..917affa51e5 100644
Binary files a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/block-device-assignment.png and b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/block-device-assignment.png differ
diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/boot-this-config.png b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/boot-this-config.png
index 3f44059ede3..82d3262e2b3 100644
Binary files a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/boot-this-config.png and b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/boot-this-config.png differ
diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/image-selection.png b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/image-selection.png
index ba9d61b4a7b..15193f7bba9 100644
Binary files a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/image-selection.png and b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/image-selection.png differ
diff --git a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md
index 072cc4c4636..0063189cfb7 100644
--- a/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md
+++ b/docs/products/compute/compute-instances/guides/copy-a-disk-image-to-a-different-account/index.md
@@ -3,7 +3,7 @@ title: "Copying a Disk to a Different Account"
 title_meta: "How to Copy a Disk to a Different Account"
 description: "Review this guide to find out how to copy a disk of a Linode from one Linode account to another."
 published: 2020-06-01
-modified: 2022-03-28
+modified: 2024-06-20
 keywords: ["disk", "migration", "moving to different accounts"]
 tags: ["linode platform","cloud manager"]
 image: copying_a_disk_to_a_differnet_account_smg.png
@@ -13,7 +13,7 @@ aliases: ['/migration/copy-disk-image-different-account/','/linode-platform/mana
 You can copy a disk of a Linode from one Linode account to another. This is a great way to prepare a disk for another Linode customer and transfer it from one individual account to another individual account. Or if you have multiple Linode accounts, this guide provides instructions to consolidate all the disks in one account.
 
 {{< note >}}
-If you are copying a disk of a Linode that hosts applications, then ensure that you complete the backup and migrate steps for the respective applications.
+If you're copying a disk from a Linode that hosts applications, then ensure that you complete the backup and migrate steps for the respective applications.
 {{< /note >}}
 
 ## Preparing the Receiving Linode
@@ -23,18 +23,20 @@ You need to prepare the *receiving* Linode before initiating the transfer. First
 ### Creating a New Receiving Linode
 
 1.  Log in to the [Cloud Manager](https://cloud.linode.com) with the username and password you created when signing up.
+
 1.  Click **Create** at the top of the page and select **Linode**.
+
 1.  Click **X** to not choose any **Image** in the **Choose a Distribution** section of the [Distributions](/docs/products/compute/compute-instances/guides/distributions/) tab.
 
     ![Creating a receiving Linode](image-selection.png)
 
-1. Choose the region where you would like the Linode to reside. If you're not sure which to select, see our [How to Choose a Data Center](/docs/products/platform/get-started/guides/choose-a-data-center/) guide. You can also generate [MTR reports](/docs/guides/diagnosing-network-issues-with-mtr/) for a deeper look at the route path between you and a data center in each specific region.
+1.  Choose the region where you would like the Linode to reside. If you're not sure which to select, see our [How to Choose a Data Center](/docs/products/platform/get-started/guides/choose-a-data-center/) guide. You can also generate [MTR reports](/docs/guides/diagnosing-network-issues-with-mtr/) for a deeper look at the route path between you and a data center in each specific region.
 
-1. Select a Linode plan.
+1.  Select a Linode plan.
 
 1.  Give the Linode a label. This is a name to help you easily identify it within the Cloud Manager's Dashboard. If desired, assign a tag to the Linode in the **Add Tags** field.
 
-1. Skip the **Root Password** and **SSH Keys** fields, as they are disabled when creating an empty Linode.
+1.  Skip the **Root Password** and **SSH Keys** fields, as they are disabled when creating an empty Linode.
 
 1.  Click **Create Linode**. The system directs you to the *Linodes* page that reports the status of the Linode as it boots up.
 
@@ -46,14 +48,17 @@ To hold the files transferred from the other Linode, create two new disks labele
 
 1.  Go to the **Storage** tab and click **Add a Disk** in the **Disks** section. The **Add Disk** window appears.
 
-    ![Adding a disk](add_disk.png)
+    ![Creating a receiving Linode](add_disk.png)
 
 1.  Type a descriptive name such as `copy` for the disk in the **Label** field.
+
 1.  Select `ext4` in the **Filesystem** dropdown field.
+
 1.  Set the size of the disk in the **Size** field. The size of the disk must be large enough to hold the contents of the disk that you want to copy.
+
 1.  Click **Add** to create the disk.
-1.  Repeat the steps to create a disk labeled `swap` and select `swap` in the **Filesystem** dropdown field.
-    Ensure that the size of the `swap` disk is the same as that of the `swap` disk of the disk that you want to copy.
+
+1.  Repeat the steps to create a disk labeled `swap` and select `swap` in the **Filesystem** dropdown field. Ensure that the size of the `swap` disk is the same as that of the `swap` disk of the disk that you want to copy.
 
 The system creates disks to hold the files from the disk of other account.
 
@@ -61,10 +66,13 @@ The system creates disks to hold the files from the disk of other account.
 
 Start the receiving Linode in rescue mode:
 
-1.  Select the Linode that is receiving the disk. The Linode's dashboard appears.
+1. Select the Linode that is receiving the disk. The Linode's dashboard appears.
+
 1. Select the **More Options Ellipsis** and click the **Rescue** button.
-1.  Set the **/dev/sda** field to `copy` and **/dev/sdb** to `swap`.
-1.  Click **Reboot into Rescue Mode**.
+
+1. Set the **/dev/sda** field to `copy` and **/dev/sdb** to `swap`.
+
+1. Click **Reboot into Rescue Mode**.
 
 ### Access the Linode in Rescue Mode
 
diff --git a/docs/products/compute/compute-instances/guides/create/create-instance-pg.png b/docs/products/compute/compute-instances/guides/create/create-instance-pg.png
new file mode 100644
index 00000000000..7c574f94ebc
Binary files /dev/null and b/docs/products/compute/compute-instances/guides/create/create-instance-pg.png differ
diff --git a/docs/products/compute/compute-instances/guides/create/index.md b/docs/products/compute/compute-instances/guides/create/index.md
index d4b1caf1517..639074997e2 100644
--- a/docs/products/compute/compute-instances/guides/create/index.md
+++ b/docs/products/compute/compute-instances/guides/create/index.md
@@ -3,26 +3,27 @@ title: "Create a Compute Instance"
 title_meta: "Create a Compute Instance on the Linode Platform"
 description: "Learn how to create a new Compute Instance, including choosing a distribution, region, and plan size."
 published: 2022-04-19
-modified: 2024-05-21
+modified: 2024-06-20
 keywords: ["getting started", "deploy", "linode", "linux"]
 aliases: ['/guides/creating-a-compute-instance/','/products/compute/dedicated-cpu/guides/deploy/']
 ---
 
 This guide walks you through creating a Compute Instance (also frequently called a *Linode*) through the Cloud Manager. Whether this is your first time using Linode or if you're a long time user, you should carefully consider each step in the process to make sure you're getting the most of your Linode services.
 
-1. [Open the Create Form in the Cloud Manager](#open-the-create-form-in-the-cloud-manager)
-1. [Choose a Distribution, App, or Image](#choose-a-distribution-app-or-image)
-1. [Select a Region](#select-a-region)
-1. [Choose an Instance Type and Plan](#choose-an-instance-type-and-plan)
-1. [Set the Label and Add Tags](#set-the-label-and-add-tags)
-1. [Create a Password and Add SSH Keys](#create-a-password-and-add-ssh-keys)
-1. [Assign to a VPC](#assign-to-a-vpc)
-1. [Assign to a Cloud Firewall](#assign-to-a-cloud-firewall)
-1. [Assign to a VLAN](#assign-to-a-vlan)
-1. [Configure Additional Options](#configure-additional-options)
-1. [Add User Data](#add-user-data)
-1. [Deploy the Instance](#deploy-the-instance)
-1. [Getting Started After Deployment](#getting-started-after-deployment)
+- [Open the Create Form in the Cloud Manager](#open-the-create-form-in-the-cloud-manager)
+- [Choose a Distribution, App, or Image](#choose-a-distribution-app-or-image)
+- [Select a Region](#select-a-region)
+- [Choose an Instance Type and Plan](#choose-an-instance-type-and-plan)
+- [Set the Label and Add Tags](#set-the-label-and-add-tags)
+- [Create a Password and Add SSH Keys](#create-a-password-and-add-ssh-keys)
+- [Assign to a VPC (Optional) {#assign-to-a-vpc}](#assign-to-a-vpc-optional-assign-to-a-vpc)
+- [Assign to a Cloud Firewall (Optional) {#assign-to-a-cloud-firewall}](#assign-to-a-cloud-firewall-optional-assign-to-a-cloud-firewall)
+- [Assign to a VLAN (Optional) {#assign-to-a-vlan}](#assign-to-a-vlan-optional-assign-to-a-vlan)
+- [Assign to a Placement Group (Optional) {#assign-to-a-placement-group}](#assign-to-a-placement-group-optional-assign-to-a-placement-group)
+- [Configure Additional Options](#configure-additional-options)
+- [Add User Data](#add-user-data)
+- [Deploy the Instance](#deploy-the-instance)
+- [Getting Started After Deployment](#getting-started-after-deployment)
 
 ## Open the Create Form in the Cloud Manager
 
@@ -130,6 +131,16 @@ Add this Compute Instance to a secure private network. VLANs are available at no
 In most cases, it's recommended to use a VPC over a VLAN. VPCs operate on a higher network layer and come with more IP addressing and IP routing functionality. Additionally, you can further segment out network traffic through subnets, each of which has its own CIDR range. Review [these differences](/docs/products/networking/vpc/#difference-between-private-network-options-vpcs-vlans-and-private-ips) to learn more.
 {{< /note >}}
 
+## Assign to a Placement Group (Optional) {#assign-to-a-placement-group}
+
+![Creating a receiving Linode](create-instance-pg.png)
+
+Add this Compute Instance to a Placement Group to manage its physical location in a data center ("region"). Placement Groups can be set up to group your compute instances close together to help with performance, or further apart to support high availability. Placement Groups are available at no additional cost, but they're not available in all regions. See [Work with Placement Groups](/docs/products/compute/compute-instances/guides/placement-groups/) to learn more.
+
+{{< note >}}
+If you don't have an existing Placement Group, you can click **Create Placement Group** to create a new one. This takes you to a separate interface, outside creating your compute instance. For ease of use, create your compute instances in a supported region, then later create a Placement Group and assign your compute instances to it.
+{{< /note >}}
+
 ## Configure Additional Options
 
 The following features and services can be configured during the Compute Instance's creation or at any point after.
diff --git a/docs/products/compute/compute-instances/guides/failover/index.md b/docs/products/compute/compute-instances/guides/failover/index.md
index 59f2cfea75e..68175b54d05 100644
--- a/docs/products/compute/compute-instances/guides/failover/index.md
+++ b/docs/products/compute/compute-instances/guides/failover/index.md
@@ -2,7 +2,7 @@
 title: "Configure Failover on a Compute Instance"
 description: "This guide discusses how to enable failover on a Linode Compute Instance through using our IP Sharing feature with software such as keepalived or FRR."
 published: 2022-03-23
-modified: 2024-02-20
+modified: 2024-06-20
 keywords: ['IP failover','IP sharing','elastic IP']
 aliases: ['/guides/ip-failover/']
 tags: ["media"]
@@ -53,11 +53,8 @@ Within Linode's platform, failover is configured by first enabling [IP Sharing](
 | Washington, DC (USA) | **Supported** | BGP-based (new) | [lelastic](/docs/products/compute/compute-instances/guides/failover/#configure-failover) / [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) | 17 |
 
 {{< note >}}
-If a data center is marked as *undergoing network upgrades*, customers may encounter issues enabling IP Sharing and configuring failover. For Compute Instances that already have IP Sharing enabled, this feature should still function as intended. Once the network upgrades are completed, IP Sharing will be supported through the new method (BGP). Review documentation on our [planned network infrastructure upgrades](/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/) to learn more about these changes.
-{{< /note >}}
-
-{{< note >}}
-IP failover for VLAN IP addresses is supported within every data center where VLANs are available. This feature does not depend on Linode's IP Sharing feature and depends on ARP-based failover software, such as keepalived.
+- If a data center is marked as *undergoing network upgrades*, customers may encounter issues enabling IP Sharing and configuring failover. For Compute Instances that already have IP Sharing enabled, this feature should still function as intended. Once the network upgrades are completed, IP Sharing will be supported through the new method (BGP). Review documentation on our [planned network infrastructure upgrades](/docs/products/compute/compute-instances/guides/network-infrastructure-upgrades/) to learn more about these changes.
+- IP failover for VLAN IP addresses is supported within every data center where VLANs are available. This feature does not depend on Linode's IP Sharing feature and depends on ARP-based failover software, such as keepalived.
 {{< /note >}}
 
 ## IP Address Failover Methods
@@ -75,18 +72,13 @@ IP failover for VLAN IP addresses is supported within every data center where VL
 The instructions within this guide enable you to configure failover using IP Sharing and the [lelastic](https://github.com/linode/lelastic) tool, a Linode provided tool based on GoBGP that automates much of the configuration. While lelastic enables many basic implementations of failover, you may want to consider using FRR or any other BGP client if your implementation is more advanced. See [Configuring IP Failover over BPG using FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/).
 
 {{< note >}}
-If your data center supports the legacy method (ARP), use the [Configuring IP Failover using keepalived](/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/) guide instead. That guide should also be used when setting up failover for VLAN IP addresses.
+- If your data center supports the legacy method (ARP), use the [Configuring IP Failover using keepalived](/docs/products/compute/compute-instances/guides/failover-legacy-keepalived/) guide instead. That guide should also be used when setting up failover for VLAN IP addresses.
+- If you've included your compute instances in a [placement group](/docs/products/compute/compute-instances/guides/placement-groups/), the group needs to use **Anti-affinity** as its Affinity Type, which spreads them out in a data center. The opposite Affinity Type, **Affinity** physically places compute instances close together, sometimes on the same host. This defeats the purpose of fail over.
 {{< /note >}}
 
-To configure failover, complete each section in the order shown:
-
-1.  [Create and Share the Shared IP Address](#create-and-share-the-shared-ip-address)
-1.  For *each* Compute Instance:
-    - [Add the Shared IP to the Networking Configuration](#add-the-shared-ip-to-the-networking-configuration)
-    - [Install and Configure Lelastic](#install-and-configure-lelastic)
-1.  [Test Failover](#test-failover)
+To configure failover, complete each section that follows.
 
-### Create and Share the Shared IP Address
+### 1. Create and Share the Shared IP Address
 
 1.  Log in to the [Cloud Manager](https://cloud.linode.com/).
 
@@ -106,7 +98,7 @@ To configure failover, complete each section in the order shown:
     When IP Sharing is enabled for an IP address, all connectivity to that IP address is immediately lost *until* it is configured on [Lelastic](#install-and-configure-lelastic), [FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/), or another BGP routing tool. This is not an issue when adding a new IP address, but should be considered if you are enabling IP Sharing on an existing IP address that is actively being used.
     {{< /note >}}
 
-### Add the Shared IP to the Networking Configuration
+### 2. Add the Shared IP to the Networking Configuration
 
 Adjust the network configuration file on *each* Compute Instance, adding the shared IP address and restarting the service.
 
@@ -175,7 +167,7 @@ Adjust the network configuration file on *each* Compute Instance, adding the sha
 
         Since the loopback interface is not used, you must also add the `-allifs` option to the lelastic command (discussed in a separate section below).
 
-### Install and Configure Lelastic
+### 3. Install and Configure Lelastic
 
 Next, we need to configure the failover software on *each* Compute Instance. For this, the [lelastic](https://github.com/linode/lelastic) utility is used. For more control or for advanced use cases, follow the instructions within the [Configuring IP Failover over BPG using FRR](/docs/products/compute/compute-instances/guides/failover-bgp-frr/) guide instead of using lelastic.
 
diff --git a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md
index f6ca81afba5..e1229a64e91 100644
--- a/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md
+++ b/docs/products/compute/compute-instances/guides/migrate-to-different-dc/index.md
@@ -1,49 +1,46 @@
 ---
-title: Initiate a Cross Data Center Migration for a Compute Instance
+title: Migrate to a New Data Center
 description: "Learn how to migrate a Compute Instance across data centers using the Cloud Manager."
-published: 2019-02-04
-modified: 2023-09-21
 keywords: ["choose", "help", "migration", "data center"]
 tags: ["linode platform","cloud manager"]
+modified: 2024-05-09
+modified_by:
+  name: Linode
+published: 2019-02-04
 aliases: ['/platform/disk-images/how-to-initiate-a-cross-data-center-migration-for-your-linode/','/platform/migrating-to-a-different-data-center/','/guides/how-to-initiate-a-cross-data-center-migration-for-your-linode/']
 ---
 
-When a Compute Instance is created, it is stored on whichever data center was selected during the creation process. If you wish to change this data center, you can initiate a cross data center migration at any time. This moves your Compute Instance to whichever data center you wish.
+When you create a Compute Instance, it's stored on a specific data center you select. If you need to change this, you can initiate a cross-data-center migration, to move it to another data center.
 
 {{< note >}}
 Review the [Choosing a Data Center](/docs/products/platform/get-started/guides/choose-a-data-center/) guide to learn how to choose and speed test a data center.
 {{< /note >}}
 
-## In this Guide:
-
-This guide will cover the following topics:
-
-- [Important details to know before initiating a cross data center migration](#things-to-know-before-migrating).
-- [How to migrate your Compute Instance to a different data center](#migrating-to-a-new-data-center).
+## Before You Begin
 
-## Things to Know Before Migrating
+Various changes applied by the migration can impact your instance's configuration and the devices connected to it. They can all be seen in a caution message before proceeding with your migration within the Cloud Manager. Here are some changes you should be aware of:
 
-Migrating your Compute Instance to a new data center will result in a number of changes that may impact your instance's configuration and external devices connected to it. All of these changes can be seen in a caution message before proceeding with your migration within the Cloud Manager. Changes to be aware of are as follows:
+- **IP addresses are not transferrable** They aren't migrated to the new data center with your Compute Instance. Akamai issues a new IPv4 and IPv6 address for your instance, and you can access them once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and you can see them in your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to learn how to access Networking information in the Cloud Manager.
 
-- IP addresses are not transferrable across data centers and they will not be migrated with your Compute Instance. Your instance will be issued a new IPv4 and IPv6 address, which will be accessible once the migration completes. When your instance enters the migration queue, new IP addresses are reserved and can be viewed on your instance's **Networking** detail page. See the [Find Your Linode's IP Address](/docs/guides/find-your-linodes-ip-address/) guide to learn how to access Networking information in the Cloud Manager.
-
-- Any DNS records that point to the original IP address should be changed to use the new IP address once migrated. If you're hosting your DNS with us, this can be done through the [DNS Manager](/docs/products/networking/dns-manager/), while [rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) can be configured directly on each Compute Instance's Networking detail page.
+- **DNS records need to be updated**. You need to update DNS records with the new IP address once migrated. If you're hosting your DNS with us, this can be done through the [DNS Manager](/docs/products/networking/dns-manager/), while [rDNS](/docs/products/compute/compute-instances/guides/configure-rdns/) can be configured directly on each Compute Instance's Networking detail page.
 
     {{< note >}}
-    If any of these DNS records are in use, the software using them will not be able to connect after the migration is completed *until* the DNS records have been upgraded and the changes have propagated.
+    If any DNS records are in use, the software using them won't be able to connect during or after the migration. After the migration, you need to make the necessary changes to the DNS, and they need to propagate.
     {{< /note >}}
 
-- Any existing Backups created through our [Linode Backup Service](/docs/products/storage/backups/) will not be migrated. Once the Compute Instance's migration has completed, your backup service will restart on its normal schedule.
+- **Existing Backups can't be migrated**. Any [Linode Backup Service](/docs/products/storage/backups/) backup you have scheduled during the migration is skipped. Once the migration completes, Cloud Manager restarts your backup service on its normal schedule.
+
+- **Block Storage volumes can't be migrated to other data centers**. If you have a Block Storage volume attached to your Compute Instance, the migration detaches it as it begins. See our [Transfer Block Storage Data between Data Centers](/docs/products/storage/block-storage/guides/transfer-volume-data-between-data-centers/) guide to learn how to transfer a Block Storage volume's data between data centers.
 
-- Block Storage volumes cannot be migrated to other regions. If you have a Block Storage volume attached to your Compute Instance, it will be detached when the migration begins. See our [Transfer Block Storage Data between Data Centers](/docs/products/storage/block-storage/guides/transfer-volume-data-between-data-centers/) guide to learn how to transfer a Block Storage volume's data between data centers.
+- **Services need to be supported in the target data center**. If the Compute Instance is using IPv6 pools, VLANs, or other features that have not yet been deployed to all data centers, the destination data center needs to support these features, too. Any non-supported service is stripped from the migrated Compute Instance.
 
-- If the Compute Instance is using IPv6 pools, VLANs, or other features that have not yet been deployed to all data centers, the destination data center must also support these features.
+- **There is downtime during the migration**. Data transfer requires some time. This downtime varies, based on your total disk size and the speeds expected between each data center. Before the migration, Cloud Manager displays a calculated estimate for this downtime in the "Caution" message.
 
-- Migrations will include a period of downtime while your data is transferred. This estimate varies depending on your total disk size and the speeds expected between each data center. A calculated estimate will be displayed within the "Caution" message displayed before moving forward with your migration.
+- **Pricing can vary between data centers**. In some newer data centers, services and network transfer are billed at separate rates due to higher region-based infrastructure costs. Before you migrate from one region to another, confirm any applicable price differences. See our [Pricing](https://www.linode.com/pricing/) page for a list of pricing and plan options.
 
-- Pricing may vary between data centers. Services and network transfer in some newer data centers are billed at separate rates due to higher region-based infrastructure costs. Before you migrate from one region to another, you must confirm any applicable price differences that will occur as a result of the migration. See our [Pricing](https://www.linode.com/pricing/) page for a complete list of pricing and plan options.
+- **Migration removes a compute instance from a placement group**. A [placement group](/docs/products/compute/compute-instances/guides/placement-groups/) needs to exist in a specific data center, and its member compute instances need to be in that *same data center*. If the target data center supports them, you can select to create a new placement group during the migration set up.
 
-## Migrating to a New Data Center
+## Migrate to a New Data Center
 
 1. Log in to the [Cloud Manager](https://www.cloud.linode.com) and click on the **Linodes** link in the sidebar.
 
@@ -53,12 +50,8 @@ Migrating your Compute Instance to a new data center will result in a number of
 
     This same menu also appears within each individual Compute Instance's dashboard page.
 
-1. In **Migrate Linode** form, review the details of the migration and check the **Accept** box to agree to these conditions and expectations.
+3. In **Migrate Linode** form, review the details of the migration and check the **Accept** box to agree to these conditions and expectations.
 
-1. Under **Configure Migration**, select the destination region. This will be the data center that the Compute Instance is migrated to.
+1. Under **Configure Migration**, select the destination **Region** for the migration.
 
-1. Click on the **Enter Migration Queue** button, which closes the form and enters the Compute Instance into the migration queue. You can monitor the progress of your migration from both within the list of Compute Instances and the Compute Instance's dashboard. Your instance will return to its previous state (powered on or off) once the migration has completed.
-
-{{< note >}}
-If migrating to a data center with different plan pricing, a note will display the difference in price prior to migrating.
-{{< /note >}}
\ No newline at end of file
+1. Click **Enter Migration Queue**. You can monitor the progress of your migration from the list of Compute Instances and the Compute Instance's dashboard. Cloud Manager returns your instance to its previous state (powered on or off) once the migration completes.
\ No newline at end of file
diff --git a/docs/products/compute/compute-instances/guides/placement-groups/index.md b/docs/products/compute/compute-instances/guides/placement-groups/index.md
new file mode 100644
index 00000000000..5aaf6648fb3
--- /dev/null
+++ b/docs/products/compute/compute-instances/guides/placement-groups/index.md
@@ -0,0 +1,192 @@
+---
+title: "Work with Placement Groups"
+description: "Learn how to group your compute instances to best meet your delivery model."
+published: 2024-06-20
+keywords: ["placement-group", "affinity", "compliance"]
+---
+
+When you deploy several compute instances in an Akamai data center ("region"), they're allocated to physical machines. This allocation varies based on several factors, including the compute instance plan and availability for that plan sizes. However, you may want your compute instances in specific physical locations, to best support your need. You may want them close together, even on the same host to speed up performance. Or, you may want to disperse them across several hosts to support high availability. Placement groups let you determine this physical location to meet either of these models.
+
+## Overview
+
+The Placement Groups service gives you a convenient way to set up groups of your compute instances, using Cloud Manager, API operations, or our CLI. Create a new placement group in a supported region and add new or existing compute instances from that region to your group. With the new group created, we physically move your compute instances into it, based on your desired model.
+
+## Availability
+
+The Placement Groups service is available in select regions. Currently, this includes:
+
+- Miami, FL (us-mia)
+
+- Chicago, IL (us-ord)
+
+{{< note >}}
+Placement Groups is in limited availability. Throughout this phase, we expect to increase the number of supported regions.
+{{< /note >}}
+
+## Affinity, enforcement, and compliance
+
+To distribute your compute instances in a placement group, we use the industry-recognized affinity standard. Pick from one of two types to serve as your "preferred container" type for your placement group:
+
+- **Affinity**. Your compute instances are physically close together, possibly on the same host. Set this as your preferred container if your application requirements value performance over availability.
+
+- **Anti-affinity**. Your compute instances are placed in separate fault domains, but they're still in the same region. Use this preferred container to better support a high-availability model.
+
+In addition to selecting the Affinity Type, you select how it's enforced when you add more Compute Instances to the placement group.
+
+- **Strict (Best practice)**. You can't add more compute instances to your placement group if your preferred container lacks capacity or is unavailable. For example, let's assume you've set **Anti-affinity** as your affinity type. If you try to add a compute instance that's on the same host, or there's no capacity outside that host in the region, you get an error and can't add the compute instance. This helps you keep your placement group compliant, because you can only pick compute instances that fit your desired model.
+
+- **Flexible**. You can add more compute instances to your placement group even if they're outside your affinity type's preferred container. However, if you add one and it violates your affinity type, the placement group becomes non-compliant. Once the necessary capacity is available in the data center, we physically move the compute instance for you to fit your affinity type's preferred container and make it compliant again. This can work for you if you know you need to add more compute instances to your group in the future.
+
+### Fix Non-compliance
+
+If a placement group becomes non-compliant, we're alerted and we'll bring it back into compliance as soon as possible. Non-compliance can only be fixed by Akamai staff. **_You can't fix it yourself_**.
+
+By design, a Strict placement group can't be made non-compliant when simply creating it or managing its Compute Instances. In rare cases, non-compliance can occur if we need to fail-over or migrate your Compute Instances for maintenance. Because of this, fixing non-compliance for Strict placement groups is prioritized over Flexible groups.
+
+## Create a placement group
+
+{{< tabs >}}
+{{< tab "Cloud Manager" >}}
+Here's how to create a new placement group and add existing compute instances to it.
+
+#### Before you begin
+
+Make sure you understand how placement groups work. Have a look at [Affinity, enforcement, and compliance](#affinity-enforcement-and-compliance).
+
+#### Creation process
+
+1.  Navigate to the **Placement Groups** page in [Akamai Cloud Manager](http://cloud.linode.com) and click **Create Placement Groups**. The **Create Placement Group** form opens.
+
+1.  Fill out the form with your desired settings:
+
+    - **Label**. Give your placement group an easily recognizable name.
+    - **Region**. Select the [data center](#availability) that includes the compute instances you want to add.
+    - **Affinity Type**. Select the [affinity](#affinity-enforcement-and-compliance) that meets your model.
+    - **Affinity Type Enforcement**. Pick how you want to [enforce](#affinity-enforcement-and-compliance) compliance for your placement group, when adding compute instances to it in the future.
+
+{{< note >}}
+- During the limited availability phase, only **Anti-affinity** is available for Affinity Type.
+- Once you create your placement group, you *can't change its Affinity Type Enforcement*.
+{{< /note >}}
+
+3.  When you're ready, click **Create Placement Group**. A summary of your group is revealed.
+
+4.  Select the **Linodes (0)** tab.
+
+1.  Click **Assign Linode to Placement Group**. The Assign Linodes form opens.
+
+1.  The **Linodes in \<Region\>** drop-down is auto-populated with eligible compute instances in your selected Region. Pick one to add it and click **Assign Linode**.
+
+    <div align=center>
+    <img src="pg-added-linode-v1.png" width=600 />
+    </div>
+
+7. Review the **Linode limit for this placement group**, and repeat steps 5-6 to add more compute instances, as necessary.
+
+{{< note >}}
+During the limited availability phase, you’re limited to a maximum of 5 compute instances in a placement group.
+{{< /note >}}
+
+With all your compute instances added, we begin provisioning by moving them into the placement group to meet your selected Affinity Type.
+
+{{< /tab >}}
+{{< tab "Linode API" >}}
+Here, we combine API operations to create a new placement group and add existing compute instances to it.
+
+#### Before you begin
+
+Make sure you understand how placement groups work. Have a look at [Affinity, enforcement, and compliance](#affinity-enforcement-and-compliance).
+
+#### List regions
+
+Run this API curl request, making sure to properly paste in or reference your [API token](/docs/products/tools/api/guides/manage-api-tokens/). Store the `id` and `label` values for the region where your target compute instances live.
+```command
+curl -H "Authorization: Bearer $TOKEN" \
+    https://api.linode.com/v4/regions
+```
+{{< note >}}
+During the limited availability phase, only specific [regions](#availability) support placement groups.
+{{< /note >}}
+
+#### Identify the maximum number of compute instances
+
+Run this request, using the stored region `id`. Store the `maximum_linodes_per_pg` value. This represents the maximum number of compute instances you can add to a placement group for that region.
+```command
+curl -H "Authorization: Bearer $TOKEN" \
+    https://api.linode.com/v4/regions/us-east
+```
+{{< note >}}
+During limited availability, you can have a maximum of 5 compute instances in a placement group.
+{{< /note >}}
+
+#### List compute instances
+
+Run this request using the stored region `id` to filter the response. Identify the specific compute instances you want to include -- up to the `maximum_linodes_per_pg` value -- and store the `id` value for each.
+```command
+curl -H "Authorization: Bearer $TOKEN"
+    -H 'X-Filter: { "region": "us-east" }'
+    https://api.linode.com/v4/networking/ips
+```
+
+#### Create a new placement group
+
+Run this request to create a new placement group. Store the `id` value that's generated for it.
+
+- `label`. Give your placement group an easily recognizable name.
+- `region`. Set this to the `label` you stored for your region.
+- `affinity-type`. Set this to the [affinity](#affinity-enforcement-and-compliance) that meets your model.
+- `is_strict`. Define how to [enforce](#affinity-enforcement-and-compliance) compliance for your placement group, when adding compute instances to it in the future. Set to `true`, strict enforcement is applied and `false` sets it to flexible.
+
+{{< note >}}
+- During the limited availability phase, only anti-affinity (`anti-affinity:local`) is available for `affinity-type`.
+- Once you create your placement group, you *can't change* its affinity type enforcement setting (`is_strict`).
+{{< /note >}}
+
+```command
+curl -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $TOKEN" \
+    -X POST -d '{
+      "label": "new-placement-group",
+      "region": "us-iad",
+      "affinity-type": "anti_affinity:local",
+      "is_strict": "true"
+    }' \
+    https://api.linode.com/v4/placement/groups
+```
+
+#### Add compute instances to the group
+
+In this request, populate the `linodes` array with a comma-separated data center list of stored `id` values for the compute instances. In the URL, target the new placement group using its stored `id`.
+
+```command
+curl -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $TOKEN" \
+    -X POST -d '{
+      "linodes": [
+        123, 456, 789
+      ]
+    }' \
+    https://api.linode.com/v4/placement/groups/12/assign
+```
+With all your compute instances added, we begin provisioning by moving them into the placement group to meet your selected affinity type.
+
+#### More with the Placement Groups API
+
+There are several other operations in the [Linode API](https://techdocs.akamai.com/linode-api/reference/post-placement-group) that let you interact with placement groups.
+
+{{< /tab >}}
+{{< /tabs >}}
+
+## Technical Specifications
+
+- Placement groups support dedicated and shared compute instance plans. Plan types can be mixed in a placement group. However, specialty hardware, such as GPUs aren't supported.
+
+- A compute instance can only exist in one placement group.
+
+- The Affinity Type and Region you select determine the maximum number of compute instances per placement group. This quantity is reflected in Cloud Manager when reviewing your placement group. With the API, the [GET /v4/regions/\{regionid\}](/docs/api/regions/#region-view) operation contains the `maximum_linodes_per_pg` element that displays this maximum.
+
+- Placement groups can be renamed or deleted. To delete a placement group, you need to remove all compute instances from it.
+
+- When you remove a compute instance from a placement group, it continues to function as-is, but the placement decisions are no longer guided by the group's Affinity Type.
+
+- Entry points to create a placement group are also available when creating a new compute instance or editing an existing one.
\ No newline at end of file
diff --git a/docs/products/compute/compute-instances/guides/placement-groups/pg-added-linode-v1.png b/docs/products/compute/compute-instances/guides/placement-groups/pg-added-linode-v1.png
new file mode 100644
index 00000000000..a9820457e2a
Binary files /dev/null and b/docs/products/compute/compute-instances/guides/placement-groups/pg-added-linode-v1.png differ
diff --git a/docs/products/compute/compute-instances/guides/resize/index.md b/docs/products/compute/compute-instances/guides/resize/index.md
index ff449008e8d..3188c7e148a 100644
--- a/docs/products/compute/compute-instances/guides/resize/index.md
+++ b/docs/products/compute/compute-instances/guides/resize/index.md
@@ -10,115 +10,116 @@ image: resizing_a_linode.png
 aliases: ['/platform/disk-images/resizing-a-linode-classic-manager/','/resizing/','/platform/disk-images/resizing-a-linode/','/migrate-to-linode/disk-images/resizing-a-linode/','/guides/resizing-a-linode/']
 ---
 
-Changing a Compute Instances plan (and plan type) is made easy through the Cloud Manger. This includes upgrading to a larger plan or downgrading to a smaller plan. If you're expecting a temporary burst of traffic to your website, or if you're not using your plan's resource allotment as much as you thought, you can temporarily or permanently resize your instance.
+You can easily change a Compute Instance's plan using Cloud Manger. Are you expecting a temporary burst of traffic to your website? Or, are you using your plan's resource allotment less than you thought? To accommodate, you can upgrade to a larger plan or downgrade to a smaller one, respectively. You can also change to a different plan type, such as switching from a Shared CPU plan to a Dedicated CPU plan.
 
-## What to Expect
+## Before you begin
 
-- You can upgrade your Compute Instance to a larger plan, downgrade to a smaller plan, or even change to a different plan type (such as switching from a Shared CPU plan to a Dedicated CPU plan).
+Consider these points before attempting a resize:
 
-- While resizing a Compute Instance, it is migrated to a different physical host within the same data center. This new host may have slightly different hardware, though performance is consistent across our entire fleet.
+- **Hardware changes, but performance is preserved**. While resizing a Compute Instance, Cloud Manager migrates it to a different physical host within the same data center. This new host may have slightly different hardware, but performance is consistent across our entire network.
 
--  The disks are transferred to the new hardware at a typical rate of ~150 MB/sec. While you can use this rate to approximate any downtime, the actual transfer speeds may vary and downtime may be shorter or longer than expected.
+- **There are two resize types**. You can choose from two resize types: a **warm resize** or a **cold resize**. The type you choose determines the amount of migration downtime during a resize. See [Warm Resize vs. Cold Resize](#warm-resize-vs-cold-resize) to determine which resize type is right for you.
 
-- You can choose from two resize types: a **warm resize** or a **cold resize**. Which type of resize you choose will determine the amount of downtime your instance will experience when migrating from one host to another. See [Warm Resize vs. Cold Resize](#warm-resize-vs-cold-resize) to determine which resize type is right for you.
+- **What's preserved**. All of your existing data and configuration settings are preserved during the resize, and your IP addresses remain the same.
 
-- All of your existing data and configuration settings are preserved during the resize, and your IP addresses remain the same.
+- **Placement groups aren't supported**. Resizing a compute instance removes it from a [placement group](/docs/products/compute/compute-instances/guides/placement-groups/). The migration required for resizing moves the compute instance to a different physical host in a data center. This can break the Affinity Type setting that's required for a placement group. If your compute instance is in a placement group and you need to resize it, talk to your Akamai account team about other options.
 
-## Warm Resize vs. Cold Resize
+- **The transfer rate during a resize**. Your compute instance's disks are transferred to the new hardware at approximately 150 MB/sec. However, actual transfer speeds may vary.
 
-There are two resize options to choose from when configuring your resize: **warm** and **cold**. The terms “warm” and “cold” refer to the [type of migration](/docs/products/compute/compute-instances/guides/compute-migrations/) that occurs during the resize process. Your instance must be powered on in order to attempt a warm migration. If your instance is powered off, you may proceed with a cold migration.
+## Warm resize vs. cold resize
 
-- **Warm resize:** A warm resize will make sure your Compute Instance remains up while migrating to a new host prior to being rebooted. During this process, your instance is synced across hosts while running, automatically powers off, goes through the resize job, and boots back up to complete the resize. If your instance fails to automatically power off, you will be notified of the failed job attempt. Should the warm resize fail, we recommend reattempting the resize process using the cold resize option. There is less downtime during a warm resize than a cold resize.
+You have two resize options to choose from: **warm** and **cold**. Each refer to the [type of migration](/docs/products/compute/compute-instances/guides/compute-migrations/) that occurs during the resize process.
 
-- **Cold resize:** A cold resize will shut down your Compute Instance, migrate it to a new host, and restore it to its state prior to the resize process (either booted or powered off). There is more downtime during a cold resize than a warm resize.
+- **Warm resize**. Your compute instance remains up during the migration and it's rebooted once the migration completes. So, make sure your instance is powered on for this resize. If you see a warning message about an inability to power down your compute instance, try the resize again using the cold resize option. There is less downtime during a warm resize than a cold resize.
 
-## Resizing a Compute Instance
+- **Cold resize**. This shuts down your compute instance, migrates it to a new host, and restores it to its booted state prior to the resize process.
 
-1.  Log in to the [Cloud Manager](https://cloud.linode.com) and select the **Linodes** link within the left sidebar.
+## Resize a compute instance
 
-1.  Within the list of Compute Instances, locate the instance you'd like to resize, click the corresponding **more options ellipsis** dropdown menu, and select **Resize**. This displays the **Resize Linode** panel.
+1.  Log in to the [Cloud Manager](https://cloud.linode.com) and select **Linodes**.
+
+2.  In the list of compute instances, find the one you want to resize, click the corresponding **...**, and select **Resize**. The **Resize Linode** panel is displayed.
 
     ![The Resize Linode panel in the Cloud Manager](resize-linode-plan.jpg)
 
-1.  Select the desired plan.
+3.  Select the plan you want:
 
-    -  **To select a larger plan**, review [Upgrading to a Larger Plan](#upgrading-to-a-larger-plan).
+    -  **Select a larger plan**. Review [Upgrade to a Larger Plan](#upgrading-to-a-larger-plan).
 
-    -  **To select a smaller plan**, you first need to resize the instance's disks. See [Downgrading to a Smaller Plan](#downgrading-to-a-smaller-plan).
+    -  **Select a smaller plan**. First, resize the instance's disks. See [Downgrade to a smaller plan](#downgrading-to-a-smaller-plan).
 
-    -  **To select a different plan type**, review [Switching to a Different Plan Type](#switching-to-a-different-plan-type).
+    -  **Select a different plan type**. Review [Switch to a different plan type](#switching-to-a-different-plan-type).
 
-1. Under **Choose Your Resize Type**, select **warm resize** or **cold resize** to determine how you would like your instance to resize. See [Warm Resize vs. Cold Resize](#warm-resize-vs-cold-resize) to help decide which option best suits your use case.
+4. Under **Choose Your Resize Type**, select **warm resize** or **cold resize**. See [Warm resize vs. cold resize](#warm-resize-vs-cold-resize) to help decide which option best suits your need.
 
-1.  Check **Auto Resize Disk** if you'd like to automatically resize your Compute Instance's primary disk. This can only be selected if the following conditions are met:
+5.  Check **Auto Resize Disk** if you want to automatically resize your compute instance's primary disk. You can only select this if you meet these conditions:
 
     - The new plan provides more storage space than the current plan.
-    - There is only a single ext3 or ext4 disk (not a raw disk). A swap disk can also be present, but it will not be resized.
-
-    ![The Auto Resize Disk checkbox](auto-resize-disk.png)
 
-1.  Enter the Compute Instance's label in the **Confirm** field and select the **Resize Linode** button to initiate the resize.
+    - There is only a single ext3 or ext4 disk (not a raw disk). A swap disk can also be present, but the process doesn't resize it.
 
-1.  If performing a warm resize, your instance will be powered on to complete the resize process. If performing a cold resize, your instance will return to its original power state (powered on or off).
+    ![The Auto Resize Disk checkbox](auto-resize-disk.png)
 
-You are now able to utilize the resources of your new plan.
+6.  Enter the Compute Instance's label in the **Confirm** field and click **Resize Linode**.
 
-## Upgrading to a Larger Plan
+With a warm resize, Cloud Manager powers your instance on to complete the resize process. If performing a cold resize, Cloud Manager returns your instance to its original power state.
 
-Upgrading to a plan with additional resources and capacity enables you to scale vertically. Larger plans can accommodate increased traffic and provide your application with the additional computing power it needs. Since larger plans come equipped with more resources, you may want to make adjustments to take advantage of these resources.
+## Upgrade to a larger plan
 
-- **Resize Disks:** When resizing a Compute Instance to a larger plan, you can (in most cases) opt to automatically resize the disks as well. If your instance does not meet the requirements for this functionality or if you decide not to do this automatically, you can manually resize the disks at any point. See [Resize a Linode's Disk](/docs/products/compute/compute-instances/guides/disks-and-storage/)
+You can scale vertically when upgrading your compute instance to a plan with additional resources and capacity. Larger plans can accommodate increased traffic and give your application the additional computing power it needs. Since larger plans come equipped with more resources, you may want to make adjustments to take advantage of these resources.
 
-- **Optimize Applications:** Many applications can be configured to enhance performance when additional resources become available. This configuration may include increasing the memory limit, enabling multiple threads, and increasing the maximum size of data, cache, logs, or other files. Review the documentation for your application and any software such as PHP, MySQL, Apache, or NGINX.
+- **Resize Disks**. In most cases, you can opt to automatically resize the disks when resizing your compute instance. If your instance doesn't meet the requirements for this functionality, or if you decide not to do this automatically, you can manually resize the disks later. See [Resize a Linode's Disk](/docs/products/compute/compute-instances/guides/disks-and-storage/)
 
-- **Enable Multi-Queue NICS:** When upgrading to a plan with two or more vCPU cores, make sure that the multi-queue NICs feature is enabled. In most cases, this feature is already enabled or will be enabled once the Compute Instance reboots during the resize process. However, older distributions may require additional steps. See [Configuring Multi-Queue NICS](/docs/products/compute/compute-instances/guides/multiqueue-nic/).
+- **Optimize Applications**. You can enhance the performance for many applications if additional resources are available. You can do things like increase the memory limit, enable multiple threads, and increase the maximum size of data, cache, logs, or other files. Review the documentation for your application and any software such as PHP, MySQL, Apache, or NGINX.
 
-## Downgrading to a Smaller Plan
+- **Enable Multi-Queue NICS**. If you're upgrading to a plan with two or more vCPU cores, make sure the **multi-queue NICs** feature is enabled. Typically this is enabled by default. However, older distributions may require additional steps. See [Configuring Multi-Queue NICS](/docs/products/compute/compute-instances/guides/multiqueue-nic/).
 
-Downgrading to a plan with less resources may be helpful when looking to reduce computing costs or after making your application use system resources more efficiently. When moving to a smaller plan, the combined size of the Compute Instance's disks must be equal to or less than the desired plan's storage allocation.
+## Downgrade to a smaller plan
 
-1.  Determine the storage space that's included in the new desired plan. This information is listed on the [Pricing Page](https://www.linode.com/pricing/) (under the *Storage* column).
+If you're looking to reduce computing costs, you can downgrade to a plan that uses fewer resources. This can also apply if you've tuned your application to use system resources more efficiently.
 
-1.  Determine the amount of disk space currently being used on your Compute Instance. To do this, log in to your instance via [SSH](/docs/guides/connect-to-server-over-ssh/) or [Lish](/docs/products/compute/compute-instances/guides/lish/) and run the following command:
+1. Determine the amount of disk space you're using on your compute instance. Log in to your instance via [SSH](/docs/guides/connect-to-server-over-ssh/) or [Lish](/docs/products/compute/compute-instances/guides/lish/) and run the following command and review the *Used* column data:
 
     ```command
     df -h
     ```
 
-    Specifically, review the *Used* column from the output of that command.
-
-    - If you're using less space than your intended plan requires, you can move onto the next step without any further action.
+2. Review Compute Instance plans to see if you can downsize. See the [Pricing Page](https://www.linode.com/pricing/).
 
-    - If you're using more space than your intended plan allows, you need to remove some files to free up some space before moving onto the next step. See the options for doing this in the [Download Files from Your Linode](/docs/guides/download-files-from-a-compute-instance/) guide.
+   {{< note >}}
+   If you're close to a downgraded size plan, you can try to free up space on your compute instance. See the options for doing this in the [Download Files from Your Linode](/docs/guides/download-files-from-a-compute-instance/) guide.
+   {{< /note >}}
 
-1.  Resize the Compute Instance's disks to fit within the storage space of the new plan. See [Resizing a Disk](/docs/products/compute/compute-instances/guides/disks-and-storage/).
+3.  Resize the compute instance's disks to fit within the new plan. See [Resize a Disk](/docs/products/compute/compute-instances/guides/disks-and-storage/).
 
-## Switching to a Different Plan Type
+## Switch to a different plan type
 
-There are multiple Compute Instance options available, each with their own benefits and use cases. When resizing your instance, you are also able to switch to a different plan type that may better suit your workload. For help deciding on a plan type, review the [Choosing a Compute Instance Type and Plan](/docs/products/compute/compute-instances/plans/choosing-a-plan/) guide for advice and a comparison of each plan.
+When resizing your instance, you can also switch to a different plan type that better suits your workload. Here are the Compute Instance plan types Akamai offers:
 
-To switch your plan type, follow the instructions outlined within [Resizing a Linode](#resizing-a-linode). When choosing the plan, select the tab that corresponds with your desired plan type.
+- **Dedicated CPU**. Optimized for CPU-intensive applications. This plan type is equipped with dedicated vCPU cores, suitable for almost any workload that requires consistently high CPU performance. Use cases include production (and high traffic) websites, e-commerce sites, machine learning, data processing, and much more. See [Dedicated CPU Compute Instances](https://www.linode.com/products/dedicated-cpu/).
 
-See below for the different Compute Instance plan types available:
+- **Shared CPU**. Balancing performance with value. This plan type is a solid foundation for many common use cases, including development, low-traffic websites, or any workload that doesn't require consistent 100% CPU usage. See [Shared CPU Compute Instances](https://www.linode.com/products/shared/).
 
-- **Dedicated CPU:** Optimized for CPU-intenseive applications. This plan type is equipped with dedicated vCPU cores, suitable for almost any workload that requires consistently high CPU performance. Use cases include production (and high traffic) websites, e-commerce sites, machine learning, data processing, and much more. See [Dedicated CPU Compute Instances](https://www.linode.com/products/dedicated-cpu/).
+- **Premium CPU**. Guaranteed hardware for CPU-intensive workloads. Built off of our Dedicated CPU offering, this plan comes equipped with the latest AMD EPYC™ CPUs to make sure your applications are running on the best available hardware with consistent high performance. Use cases include enterprise-grade production applications, video transcoding, and more. See [Premium CPU Compute Instances](https://www.linode.com/products/premium-cpu/).
 
-- **Shared CPU:** Balancing performance with value. This plan type is a solid foundation for many common use cases, including development, low-traffic websites, or any workload that doesn't require consistent 100% CPU usage. See [Shared CPU Compute Instances](https://www.linode.com/products/shared/).
-
-- **Premium CPU:** Guaranteed hardware for CPU-intensive workloads. Built off of our Dedicated CPU offering, this plan comes equipped with the latest AMD EPYC™ CPUs to make sure your applications are running on the best available hardware with consistent high performance. Use cases include enterprise-grade production applications, video transcoding, and more. See [Premium CPU Compute Instances](https://www.linode.com/products/premium-cpu/).
-
-- **High Memory:** Optimized for memory-intensive applications. This plan type is also equipped with dedicated vCPU cores, though they contain more memory than other similarly priced plans. Use cases include large or high-traffic databases, caching servers, and more. See [High Memory Compute Instances](https://www.linode.com/products/high-memory/).
+- **High Memory**. Optimized for memory-intensive applications. This plan type is also equipped with dedicated vCPU cores, though they contain more memory than other similarly priced plans. Use cases include large or high-traffic databases, caching servers, and more. See [High Memory Compute Instances](https://www.linode.com/products/high-memory/).
 
 - **GPU:** The only plan type that is equipped with high performance NVIDIA GPU cards. GPU plans are capable of processing large amounts of data in parallel, performing complex calculations much more efficiently. See [GPU Compute Instances](https://www.linode.com/products/gpu/).
 
 {{< note >}}
-Pricing and plan options may vary by region. See our [Pricing](https://www.linode.com/pricing/) page for more information on pricing options and [How to Choose a Data Center](/docs/products/platform/get-started/guides/choose-a-data-center/#product-availability) for plan and product availability.
+- See the [Choosing a Compute Instance Type and Plan](/docs/products/compute/compute-instances/plans/choosing-a-plan/) guide for advice and a comparison of each plan.
+
+- Pricing and plan options may vary by region. See our [Pricing](https://www.linode.com/pricing/) page for more information on pricing options and [How to Choose a Data Center](/docs/products/platform/get-started/guides/choose-a-data-center/#product-availability) for plan and product availability.
 {{< /note >}}
 
+### How to switch
+
+Follow the instructions in [Resize a Linode](#resizing-a-linode). When choosing the plan, select the tab that corresponds with your desired plan type.
+
 ## Troubleshooting
 
-- **If a warm resize fails:** Should the warm resize process fail for any reason, you will receive a notification in Cloud Manager, as well as an email notification regarding the failed job. There are several reasons a warm resize may fail, including the inability to successfully reboot due to internal configuration settings. If this is the case, we recommend proceeding with a cold resize.
+- **If a warm resize fails**. Cloud Manager generates a notification, and you get an email notification regarding the failed job. There are several reasons a warm resize may fail, including the inability to successfully reboot due to internal configuration settings. If this happens, try a cold resize.
 
-- **If a cold resize fails:** Should the cold resize process fail to complete, we recommend reattempting the resize. If it continues to fail, reach out to our [Support](/docs/products/platform/get-started/guides/support/) department for assistance.
+- **If a cold resize fails**. Retry it. If it continues to fail, reach out to our [Support](/docs/products/platform/get-started/guides/support/) department for assistance.
 
 For additional information on troubleshooting resizes or migrations, please see our [Compute Migrations](/docs/products/compute/compute-instances/guides/compute-migrations/) guide.
diff --git a/docs/products/platform/accounts/guides/user-security-controls/index.md b/docs/products/platform/accounts/guides/user-security-controls/index.md
index dec1a0087aa..46cd050cea8 100644
--- a/docs/products/platform/accounts/guides/user-security-controls/index.md
+++ b/docs/products/platform/accounts/guides/user-security-controls/index.md
@@ -14,7 +14,7 @@ To protect your Linode user account against unauthorized access, there are sever
 
 2FA (*two-factor authentication*) increases the security of your Linode account by requiring two forms of authentication: your password and an expiring token, also called a one-time passcode (OTP) or 2FA code. This follows the security principle of authenticating with something you *know* (a password) and something you *have* (the device used to generate the token). This additional layer of security reduces the risk that an unauthorized individual can gain access to your Linode account.
 
-If you *do not* have 2FA enabled and have not logged in to your account in 90 days, an OTP is sent to the email address associated with your user account. Should you not complete the login attempt within 60 minutes, the code expires and another login attempt is required to generate a new code.
+If you *do not* have 2FA enabled and have not logged in to your account in 30 days, an OTP is sent to the email address associated with your user account. Should you not complete the login attempt within 60 minutes, the code expires and another login attempt is required to generate a new code.
 
 **Linode highly recommends enabling 2FA**. See [Managing Two-Factor Authentication (2FA) on a User Account](/docs/guides/2fa/) to learn how to enable 2FA. To assist with account lockouts and recovery, you must first configure three [security questions](#security-questions) on your account before enabling 2FA.
 
diff --git a/docs/release-notes/api/v4.177.0.md b/docs/release-notes/api/v4.177.0.md
new file mode 100644
index 00000000000..d232ca9dc88
--- /dev/null
+++ b/docs/release-notes/api/v4.177.0.md
@@ -0,0 +1,55 @@
+---
+title: API v4.177.0
+date: 2024-06-18
+version: 4.177.0
+---
+
+### Added
+
+Several new operations in support of the [Placement Groups](/docs/products/compute/compute-instances/guides/placement-groups/) service launch (Limited Availability):
+
+  - **List placement groups** ([GET /placement/groups)](https://techdocs.akamai.com/linode-api/reference/get-placement-groups))
+  - **Get a placement group** ([GET /placement/groups/{id}](https://techdocs.akamai.com/linode-api/reference/get-placement-group))
+  - **Create a placement group** ([POST /placement/groups/](https://techdocs.akamai.com/linode-api/reference/post-placement-group))
+  - **Update a placement group** ([PUT /placement/groups/](https://techdocs.akamai.com/linode-api/reference/put-placement-group))
+  - **Assign a placement group** ([POST /placement/groups/{id}/assign](https://techdocs.akamai.com/linode-api/reference/post-group-assign))
+  - **Unassign a placement group** ([POST /placement/groups/{id}/unassign](https://techdocs.akamai.com/linode-api/reference/post-group-unassign))
+  - **Delete a placement group** ([DELETE /placement/groups/{id}](https://techdocs.akamai.com/linode-api/reference/delete-placement-group))
+
+### Changed
+
+- Updated operations in support of the Placement Groups service launch (Limited Availability):
+
+  - **List Linodes** ([GET /linode/instances](https://techdocs.akamai.com/linode-api/reference/get-linode-instances)) - Added `placement_group` object to show the placement group the Linode belongs to.
+  - **Get a Linode** ([GET /linode/instances/{linodeId}](https://techdocs.akamai.com/linode-api/reference/get-linode-instance)) - Added `placement_group` object to show the placement group the Linode belongs to.
+  - **Create a Linode** ([POST /linode/instances](https://techdocs.akamai.com/linode-api/reference/post-linode-instance)) - Added `placement_group` parameter to include a new Linode in an existing placement group.
+  - **Clone a Linode** ([POST /linode/instances/{linodeId}/clone](https://techdocs.akamai.com/linode-api/reference/post-clone-linode-instance)) - Added `placement_group` parameter to include the cloned Linode in an existing placement group.
+  - **Initiate a DC Migration/Pending Host Migration** ([POST /linode/instances/migrate](https://techdocs.akamai.com/linode-api/reference/post-migrate-linode-instance)) - Added `placement_group` parameter to include the migrated Linode in an existing placement group.
+  - **Get your account** ([GET /account](https://techdocs.akamai.com/linode-api/reference/get-account)) - Includes `Placement Group` in the `capabilities` array for accounts with access to the service.
+  - **Get a region** ([GET /regions/{regionId}](https://techdocs.akamai.com/linode-api/reference/get-region)) - Included various parameters that describe placement group availability and limitations in a region.
+
+- Updated several Object Storage operations to support the new `regions` objects:
+
+  - **Create an Object Storage bucket** ([POST /object-storage/buckets](https://techdocs.akamai.com/linode-api/reference/post-object-storage-bucket))
+  - **List Object Storage buckets** ([GET /object-storage/buckets](https://techdocs.akamai.com/linode-api/reference/get-object-storage-buckets))
+  - **List Object Storage buckets in a region** ([GET /object-storage/buckets/{regionId}](https://techdocs.akamai.com/linode-api/reference/get-object-storage-bucketin-cluster) -- Replaces the "List Object Storage buckets in a cluster" operation.)
+  - **Get an Object Storage bucket** ([GET /object-storage/buckets/{regionId}/{bucket}](https://techdocs.akamai.com/linode-api/reference/get-object-storage-bucket))
+  - **Remove an Object Storage bucket** ([DELETE /object-storage/buckets/{regionId}/{bucket}](https://techdocs.akamai.com/linode-api/reference/delete-object-storage-bucket))
+  - **Create a URL for an object** ([POST /object-storage/buckets/{regionId}/{bucket}/object-url](https://techdocs.akamai.com/linode-api/reference/post-object-storage-object-url))
+  - **Modify access to an Object Storage bucket** ([POST /object-storage/buckets/{regionId}/{bucket}/access](https://techdocs.akamai.com/linode-api/reference/post-object-storage-bucket-access))
+  - **Update access to an Object Storage bucket** ([PUT /object-storage/buckets/{regionId}/{bucket}/access](https://techdocs.akamai.com/linode-api/reference/put-storage-bucket-access))
+  - **Get an Object Storage object ACL config** ([GET /object-storage/buckets/{regionId}/{bucket}/object-acl](https://techdocs.akamai.com/linode-api/reference/get-object-storage-bucket-acl))
+  - **Update an object's ACL config** ([PUT /object-storage/buckets/{regionId}/{bucket}/object-acl](https://techdocs.akamai.com/linode-api/reference/put-object-storage-bucket-acl))
+  - **List Object Storage bucket contents** ([GET /object-storage/buckets/{regionId}/{bucket}/object-list](https://techdocs.akamai.com/linode-api/reference/get-object-storage-bucket-content))
+  - **Upload an Object Storage TLS/SSL certificate** ([POST /object-storage/buckets/{regionId}/{bucket}/ssl](https://techdocs.akamai.com/linode-api/reference/post-object-storage-ssl))
+  - **Get an Object Storage TLS/SSL certificate** ([GET /object-storage/buckets/{regionId}/{bucket}/ssl](https://techdocs.akamai.com/linode-api/reference/get-object-storage-ssl))
+  - **Delete an Object Storage TLS/SSL certificate** ([DELETE /object-storage/buckets/{regionId}/{bucket}/ssl](https://techdocs.akamai.com/linode-api/reference/delete-object-storage-ssl))
+  - **Create an Object Storage key** ([POST /object-storage/keys](https://techdocs.akamai.com/linode-api/reference/post-object-storage-keys))
+  - **List Object Storage keys** ([GET /object-storage/keys](https://techdocs.akamai.com/linode-api/reference/get-object-storage-keys))
+  - **Get an Object Storage key** ([GET /object-storage/keys/{keyId}](https://techdocs.akamai.com/linode-api/reference/get-object-storage-key))
+  - **Update an Object Storage key** ([PUT /object-storage/keys/{keyId}](https://techdocs.akamai.com/linode-api/reference/put-object-storage-key))
+
+- Deprecated the following Object Storage-related operations. They are still available, but other operations should be used instead:
+
+  - **List clusters** ([GET /object-storage/clusters](https://techdocs.akamai.com/linode-api/reference/get-object-storage-clusters))
+  - **Get a cluster** ([GET /object-storage/clusters/{clusterId}](https://techdocs.akamai.com/linode-api/reference/get-object-storage-cluster))
\ No newline at end of file
diff --git a/go.mod b/go.mod
index d02452f447e..ed5eb5a051d 100644
--- a/go.mod
+++ b/go.mod
@@ -7,5 +7,5 @@ require (
 	github.com/gohugoio/hugo-mod-jslibs/turbo/v7 v7.20300.20000 // indirect
 	github.com/instantpage/instant.page v5.1.1+incompatible // indirect
 	github.com/linode/linode-api-docs/v4 v4.176.0 // indirect
-	github.com/linode/linode-docs-theme v0.0.0-20240610162252-dd3795f29d6a // indirect
+	github.com/linode/linode-docs-theme v0.0.0-20240618214412-23d0d6b33823 // indirect
 )
diff --git a/go.sum b/go.sum
index 2d0dc272cf8..b0b963b58d1 100644
--- a/go.sum
+++ b/go.sum
@@ -284,6 +284,8 @@ github.com/linode/linode-docs-theme v0.0.0-20240605162953-7c4dfc828751 h1:vQ+k7/
 github.com/linode/linode-docs-theme v0.0.0-20240605162953-7c4dfc828751/go.mod h1:IHFGag+AZAtmiEdw1tfqB/svFE0NPxENx9XZH9F0VU4=
 github.com/linode/linode-docs-theme v0.0.0-20240610162252-dd3795f29d6a h1:63YCTfsqj+e3ejp72H5bqZyMjW3Y+aH7LbElBUV0+QQ=
 github.com/linode/linode-docs-theme v0.0.0-20240610162252-dd3795f29d6a/go.mod h1:IHFGag+AZAtmiEdw1tfqB/svFE0NPxENx9XZH9F0VU4=
+github.com/linode/linode-docs-theme v0.0.0-20240618214412-23d0d6b33823 h1:V7w2OtECiqbNn7Hgok1Om4ebW1qIxEL26XrYVqYLuTw=
+github.com/linode/linode-docs-theme v0.0.0-20240618214412-23d0d6b33823/go.mod h1:VJUOubAM5Rxfw4hPlBH+vQ5H6il0m3k5ZYn9OViz+Ok=
 github.com/linode/linode-website-partials v0.0.0-20221205205120-b6ea1aaa59fb/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
 github.com/linode/linode-website-partials v0.0.0-20221222200538-99862e429110/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
 github.com/linode/linode-website-partials v0.0.0-20230201145731-a8703d0a954a/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
@@ -303,3 +305,4 @@ github.com/linode/linode-website-partials v0.0.0-20231027173434-abbc557a5519/go.
 github.com/linode/linode-website-partials v0.0.0-20240130163753-4a933fe77633/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
 github.com/linode/linode-website-partials v0.0.0-20240424162657-dcb8464d17f3/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
 github.com/linode/linode-website-partials v0.0.0-20240426140442-12b76ccbfefd/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=
+github.com/linode/linode-website-partials v0.0.0-20240516182804-8b13c1f13759/go.mod h1:K1Em3lwb16JiCwNVftAFwWGhyB9Zkl/nXhxjBBUC1Ao=