docs(ins): update wording

Author: bene2k1

pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx

@@ -27,7 +27,7 @@ Understanding the difference between these two techniques is key to making an in
 | Performance consistency         | Variable – depends on other workloads on the host        | High – consistent and predictable performance                 |
 | Cost                            | Lower                                                    | Higher                                                        |
 | Use case                        | Dev/test environments, low-traffic apps                  | Production apps, high-performance workloads                   |
-| CPU access                      | Shared with other Instances                              | Exclusive access to physical cores                            |
+| CPU access                      | Split with other Instances                               | Exclusive access to physical cores                            |
 | Best for                        | Personal blogs or forums, staging environments           | CI/CD, eCommerce, gaming, ML workloads                        |
 | Resource contention risk        | Possible during peak usage                               | None                                                          |
 | Latency sensitivity             | Not suitable for latency-sensitive apps                  | Ideal for latency-critical applications                       |
@@ -36,9 +36,11 @@ Understanding the difference between these two techniques is key to making an in
 Shared vCPU Instances, including [Learning](/instances/reference-content/learning/) and [Cost-Optimized](/instances/reference-content/cost-optimized/), are cost-effective virtual machines in which CPU resources are shared among multiple Instances.
 This means multiple virtual CPU cores are allocated to these Instances, but the physical CPU cores available on the hypervisors' hardware are shared among them.
 As a result, Instances share physical CPU time, and during peak demand from other Instances on the same host, your workloads might temporarily slow down due to CPU contention (also known as "CPU steal").
+While physical CPU threads are shared between Instances, vCPUs are dedicated to each Instance, and no data can be shared or accessed between Instances through this setup.
 
 ### Typical use cases
 - Development and staging environments
+- Small and non critical production environments
 - Low to medium-traffic websites
 - Personal blogs and forums
 - Applications tolerant to occasional performance variability