docs(ins): update content

Author: bene2k1

macros/compute/instances-block-bandwidth-overview.mdx

@@ -38,17 +38,6 @@ Bandwidth impacts how your applications perform and interact with other systems.
 | DEV1-L                | 400 Mbit/s          | 200 MiB/s       |
 | DEV1-XL               | 500 Mbit/s          | 250 MiB/s       |
 
-## ENT1 range
-
-|   Instance Type      |   Internet Bandwidth (up to)  |   Block Bandwidth (up to)  |
-|-----------------------|-------------------------|---------------------|
-| ENT1-XXS              | 400 Mbit/s              | 400 MiB/s         |
-| ENT1-XS               | 800 Mbit/s              | 800 MiB/s         |
-| ENT1-S                | 1.6 Gbit/s             | 1.56 GiB/s         |
-| ENT1-M                | 3.2 Gbit/s             | 3.12 GiB/s         |
-| ENT1-L                | 6.4 Gbit/s             | 6.25 GiB/s         |
-| ENT1-XL               | 12.8 Gbit/s            | 12.5 GiB/s         |
-
 ## GP1 range
 
 |   Instance Type      |   Internet Bandwidth (up to)  |   Block Bandwidth (up to)  |

pages/instances/faq.mdx

@@ -267,25 +267,12 @@ You are free to bootstrap your own distribution.
 
 We provide a wide range of different Linux distributions and InstantApps for Instances. Refer to [Scaleway Instance OS images and InstantApps](/instances/reference-content/images-and-instantapps/) for a complete list of all available OSes and InstantApps.
 
-### What are the differences between ENT1 and POP2 Instances?
-
-Both ENT1 and POP2 Instance types share the following features:
-- Identical hardware specifications
-- Dedicated vCPU allocation
-- Same pricing structure
-- Accelerated booting process
-
-POP2 Instances provide CPU- and memory-optimized variants tailored to suit your workload requirements more effectively. The primary distinction between ENT1 and POP2 lies in [AMD Secure Encrypted Virtualization (SEV)](https://www.amd.com/fr/developer/sev.html), which is disabled for POP2 Instances.
-By choosing POP2 Instances, you gain access to the latest features, such as the potential for live migration of Instances in the future, ensuring that your infrastructure remains aligned with evolving demands and technological advancements.
-We recommend choosing POP2 Instances for most general workloads unless your specific workload requires features unique to ENT1 Instances.
-
 ### Where are my Instances located?
 
 Scaleway offers different Instance ranges in all regions: Paris (France), Amsterdam (Netherlands), and Warsaw (Poland).
 
 Check the [Instances availability guide](/account/reference-content/products-availability/) to discover where each Instance type is available.
 
-
 ### What makes FR-PAR-2 a sustainable region?
 
 `FR-PAR-2` is our sustainable and environmentally efficient Availability Zone (AZ) in Paris.

pages/instances/reference-content/understanding-instance-pricing.mdx

@@ -45,9 +45,9 @@ For cost optimization, Scaleway offers [savings plans](/billing/additional-conte
 
 The **Compute savings plan** applies to the following Instance types across all regions:
 
-- **Cost-optimized**: DEV1, GP1, PLAY2, PRO2
-- **Production-optimized**: ENT1, POP2
-- **Workload-optimized**: POP2 HC
+- Development Instances
+- General Purpose Instances
+- Specialized Instances
 
 However, savings plans **do not apply** to the following Instance types: H100, RENDER, L40S, L4, COPARM1, START1, X64, and POP-WIN.
 

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 memory are not eligible to become nodes (DEV1-S, PLAY2-PICO, STARDUST)
+  Instance type with insufficient (less than 4GB) 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 [Cost-Optimized Instances based on ARM](https://www.scaleway.com/en/cost-optimized-instances-based-on-arm/).
+ - 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>>).
  - Kubernetes clusters may consist of nodes with different architectures, including x86 and ARM.
  - Deploying applications across these diverse architectures requires special consideration.