AWS and GCP block storage migration guides

ci/vale/dictionary.txt

@@ -1022,6 +1022,8 @@ hybla
 Hydrolix
 hykes
 hypercorn
+Hyperdisk
+Hyperdisks
 hyperefficient
 HyperLogLog
 hyperparameter

docs/guides/applications/containers/build-a-cloud-native-private-registry-with-quay/index.md

@@ -9,7 +9,7 @@ keywords: ['build cloud-native container registry with quay','red hat quay','cen
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 ---
 
-Docker doesn’t provide long term storage or image distribution capabilities, so developers need something more. [Docker Registry](https://docs.docker.com/registry/) performs these tasks, and using it guarantees the same application runtime environment through virtualization. However, building an image can involve a significant time investment, which is where [Quay](https://www.redhat.com/en/resources/quay-datasheet) (pronounced *kway*) comes in. A registry like Quay can both build and store containers. You can then deploy these containers in a shorter time and with less effort than using Docker Registry. This guide explains how Quay can be an essential part of the development process and details how to deploy a Quay registry.
+Docker doesn’t provide long term storage or image distribution capabilities, so developers need something more. [Docker Registry](https://docs.docker.com/registry/) performs these tasks, and using it guarantees the same application runtime environment through virtualization. However, building an image can involve a significant time investment, which is where [Quay](https://www.redhat.com/en/resources/quay-datasheet) comes in. A registry like Quay can both build and store containers. You can then deploy these containers in a shorter time and with less effort than using Docker Registry. This guide explains how Quay can be an essential part of the development process and details how to deploy a Quay registry.
 
 ## What is Red Hat Quay?
 

docs/guides/platform/migrate-to-linode/migrate-from-azure-disk-storage-to-linode-block-storage/index.md

@@ -1,12 +1,11 @@
 ---
 slug: migrate-from-azure-disk-storage-to-linode-block-storage
 title: "Migrate From Azure Disk Storage to Linode Block Storage"
-description: "Two to three sentences describing your guide."
-og_description: "Optional two to three sentences describing your guide when shared on social media. If omitted, the `description` parameter is used within social links."
+description: "Learn how to migrate data from an Azure Disk Storage managed disk to a Linode Block Storage Volume."
 authors: ["Leon Yen","Nathan Melehan"]
 contributors: ["Leon Yen","Nathan Melehan"]
 published: 2024-11-18
-keywords: ['list','of','keywords','and key phrases']
+keywords: ['migrate','azure disk storage','linode block storage']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 ---
 
@@ -20,8 +19,7 @@ This guide describes the process of migrating a single volume from Azure Disk St
 
 2. The Azure VM sends data on the Azure data disk to a Block Storage Volume attached to the Linode instance via an established rsync connection.
 
-    2a. Egress costs for the migrated data are measured when the data leaves the Azure platform. These costs are billed by Azure.
-
+    1. Egress costs for the migrated data are measured when the data leaves the Azure platform. These costs are billed by Azure.
 {#azure-linode-bs-migration .large-diagram}
 
 ## Linode Block Storage vs. Azure Disk Storage