Apply suggestions from code review

bene2k1 · jcirinosclwy · web-flow · commit 83ffc506339f · 2025-08-20T15:00:04.000+02:00
Co-authored-by: Jessica &lt;113192637+jcirinosclwy@users.noreply.github.com&gt;
diff --git a/pages/instances/reference-content/general-purpose.mdx b/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               
diff --git a/pages/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx b/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.
diff --git a/pages/kubernetes/how-to/deploy-x86-arm-images.mdx b/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.
 
