Merge branch 'MTA-6390' of https://github.com/scaleway/docs-content into MTA-6390

Author: bene2k1

pages/instances/concepts.mdx

@@ -152,4 +152,4 @@ Tags allow you to organize, sort, filter, and monitor your cloud resources using
 
 ## x86 (Intel/AMD) Instances
 
-[x86 (Intel/AMD) Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and high-performance instances powered by AMD EPYC processors, tailored for development, testing, production workloads, and general-purpose applications.
+[x86 (Intel/AMD) Instances](https://www.scaleway.com/en/cost-optimized-instances/) are reliable and high-performance Instances powered by AMD EPYC processors, tailored for development, testing, production workloads, and general-purpose applications.

pages/instances/how-to/migrate-instances.mdx

@@ -32,7 +32,7 @@ Follow the instructions to [create an image](/instances/how-to/create-a-backup/#
 4. Click <Icon name="more" /> next to the Instance's image.
 5. Select **Create Instance from image** on the drop-down list. You are redirected to the Instance creation wizard, where the image has been preselected for you at step 2.
 6. Finish configuring the Instance according to your requirements. Notably:
-    - You are free to choose your Instance type as long it uses the same CPU architeckture (e.g. ARM to ARM or x86 to x86)
+    - You are free to choose your Instance type as long it uses the same CPU architecture (e.g. ARM to ARM or x86 to x86)
     - Click **Advanced options** and use the <Icon name="toggle" /> toggle to deselect **flexible IP**. This creates a the new Instance without a flexible IP, as we are going to attach the one from the existing Instance in the next step.
 7. Click **Create Instance** to finish. The Instance is created and shows in your Instances list.
 

pages/instances/reference-content/choosing-instance-type.mdx

@@ -4,7 +4,7 @@ description: Find out how to select the ideal Scaleway Instance type for your sp
 dates:
   validation: 2025-05-15
   posted: 2023-02-20
-tags: instance type stardust range vcpu hyperthread core ram bandwidth dedicated shared memory hypervisor vm storage dev1 play2 gp1 pro2 ent1 gpu arm learning development production production-optimized Development memory-optimized storage-optimized
+tags: instance comparison vcpu ram core
 ---
 
 Scaleway **CPU & GPU Instances** are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs.

pages/instances/reference-content/development.mdx

@@ -17,11 +17,11 @@ See below the technical specifications of Development Instances:
 
 | Range                         	| Development                                                              	|
 |:--------------------------------|:------------------------------------------------------------------------------|
-| Instance Type   	              | DEV1 <br /> GP1                                                      	        |
+| Instance type   	              | DEV1 <br /> GP1                                                      	        |
 | Availability Zone   	          | PAR1, PAR2, PAR3 (excl. DEV1), AMS1, AMS2, WAW1, WAW2                         |
 | Storage   	                    | Local or Block                                                                |
-| Max. Bandwidth   	              | From 200 to 500 Mbps                                                          |
-| CPU Type   	                    | DEV1: AMD EPYC 7281 (2,1 GHz) or equivalent<br />GP1: AMD EPYC 7410P (2 GHz) or equivalent|
+| Max. bandwidth   	              | From 200 to 500 Mbps                                                          |
+| CPU type   	                    | DEV1: AMD EPYC 7281 (2,1 GHz) or equivalent<br />GP1: AMD EPYC 7410P (2 GHz) or equivalent |
 | Resources   	                  | Shared vCPUs                                                                  |
 | Sizing   	                      | From 2 to 48 vCPUs <br />From 2 to 256 GiB RAM                                   |
 | vCPU:RAM ratio                  | Various<br />(1:1, 1:2, 1:3)                                                  |

pages/instances/reference-content/general-purpose.mdx

@@ -57,34 +57,34 @@ See below the technical specifications of General Purpose Instances:
 
 ## PLAY2 Instances and PRO2 Instances
 
-In the same **General Purpose** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of General Purpose and General Purpose Instances. They present the best price-performance ratio with the most flexible vCPU to RAM ratio, and provide features that target most standard and cloud-native workloads. In other words, these Instances keep costs down while still supporting a wide variety of cloud applications, such as medium-to-high-traffic web servers, medium-sized databases and e-commerce websites.
+In the same **General Purpose** range, you will also find PLAY2 and PRO2 Instances. These are the next generation of General Purpose and General Purpose Instances. They offer the best price-performance ratio with the most flexible vCPU to RAM ratio, and provide features that target most standard and cloud-native workloads. In other words, these Instances keep costs down while still supporting a wide variety of cloud applications, such as medium-to-high-traffic web servers, medium-sized databases, and e-commerce websites.
 
 See below the technical specifications of PLAY2 and PRO2 Instances:
 
 | Range                         	| General Purpose                                                              	|
 |:--------------------------------|:------------------------------------------------------------------------------|
-| Instance Type   	              | PLAY2 <br /> PRO2                                                    	        |
+| Instance type   	              | PLAY2 <br /> PRO2                                                    	        |
 | Availability Zone   	          | PAR1, PAR2, PAR3 (excl PLAY2), AMS1, AMS2, AMS3, WAW1, WAW2, WAW3             |
 | Storage   	                    | Block                                                                         |
-| Max. Bandwidth   	              | From 100 Mbps  to 6 Gbps                                                      |
-| CPU Type   	                    | AMD EPYC 7543 (2,8 GHz)                                                       |
+| Max. bandwidth   	              | From 100 Mbps to 6 Gbps                                                      |
+| CPU type   	                    | AMD EPYC 7543 (2,8 GHz)                                                       |
 | Resources   	                  | Shared vCPUs                                                                  |
 | Sizing   	                      | From 1 to 32 vCPUs <br />From 2 to 128 GiB RAM                                |
 | vCPU:RAM ratio                  | Various<br />(1:2, 1:4)                                                       |
 
 ## COP-ARM Instances
 
-An innovative option are COP-ARM Instances, which are powered by ARM CPUs. These Instances mark a significant step in the world of development and general purpose computing. Their ARM architecture is a key feature, offering an excellent price-performance ratio while maintaining various vCPU to RAM configurations. This ARM CPU design is especially efficient for various standard and cloud-native workloads, ensuring cost-effective operations. Ideal for a wide range of cloud applications, COP-ARM Instances are well-suited for managing medium-to-high-traffic web servers, medium-sized databases, and e-commerce platforms, all the while leveraging the unique advantages of the ARM architecture.
+COP-ARM Instances are an innovative option, powered by ARM CPUs. These Instances mark a significant step in the world of development and general-purpose computing. Their ARM architecture is a key feature, offering an excellent price-performance ratio while maintaining various vCPU to RAM configurations. This ARM CPU design is especially efficient for standard and cloud-native workloads, ensuring cost-effective operations. Ideal for a wide range of cloud applications, COP-ARM Instances are well-suited for managing medium-to-high-traffic web servers, medium-sized databases, and e-commerce platforms, all the while leveraging the unique advantages of the ARM architecture.
 
 The table below displays the technical specifications of COP-ARM Instances:
 
 | Range                         	| General Purpose                                                              	|
 |:--------------------------------|:------------------------------------------------------------------------------|
-| Instance Type   	              | COPARM1                                                             	        |
+| Instance type   	              | COPARM1                                                             	        |
 | Availability Zone   	          | PAR2                                                                          |
 | Storage   	                    | Block                                                                         |
-| Max. Bandwidth   	              | From 200 Mbps to 3.2 Gbps                                                     |
-| CPU Type   	                    | ARM (Ampere Altra Max M128-30)                                                |
+| Max. bandwidth   	              | From 200 Mbps to 3.2 Gbps                                                     |
+| CPU type   	                    | ARM (Ampere Altra Max M128-30)                                                |
 | Resources   	                  | Shared vCPUs                                                                  |
 | Sizing   	                      | From 2 to 128 vCPUs <br />From 8 to 128 GiB RAM                               |
 | vCPU:RAM ratio                  | 1:4               

pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx

@@ -166,7 +166,7 @@ Kubeconfig for cluster your-cluster-ID successfully written at /Users/youruserna
 A pool is a set of identical nodes. A pool has a name, a size (its current number of nodes), nodes number limits (min and max), and a Scaleway Instance type.
 
 <Message type="note">
-  Instance type with insufficient (less than 4GB) memory are not eligible to become nodes.
+  Instance type with insufficient (less than 4 GB) memory are not eligible to become nodes.
 </Message>
 
 Changing these limits increases/decreases the size of a pool. Thus, when autoscaling is enabled, the pool will grow or shrink inside those limits, depending on its load.

pages/kubernetes/how-to/deploy-x86-arm-images.mdx

@@ -12,7 +12,7 @@ However, Kubernetes provides several mechanisms to manage architectural diversit
 
 ## What is ARM architecture, and why is it different from x86?
 
- - ARM architecture is commonly used in devices like Raspberry Pi, IoT devices, and recent [General Purposes Instances based on ARM](https://www.scaleway.com/en/<ADD_LINK>>).
+ - ARM architecture is commonly used in devices like Raspberry Pi, IoT devices, and recent [General Purpose Instances based on ARM](https://www.scaleway.com/en/cost-optimized-instances-based-on-arm/).
  - Kubernetes clusters may consist of nodes with different architectures, including x86 and ARM.
  - Deploying applications across these diverse architectures requires special consideration.