Why topo ? Heterogeneity!

One of the coolest features about Topo is that it allows the user
to deploy firmware + application software as containerized workloads
to an heterogenous device with a single command and through standard
container tools.

Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>

Author: tgonzalezorlandoarm

content/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/overview-and-setup.md

@@ -18,7 +18,10 @@ The optional heterogeneous deployment with `remoteproc-runtime` requires a heter
 
 ## Why use Topo?
 
-Topo streamlines deploying pre-existing containerized workloads to new Arm-based Linux devices. Once a template is defined, use of Topo removes the need to deal with low-level setup and compatibility issues manually. Topo first assesses the system to identify processor features such as SVE or Neon on CPU, then advises which templates are appropriate for the device, before automating the deployment.
+Topo streamlines deploying containerized workloads to Arm-based Linux devices.
+If you have an heterogeneous device (e.g. Cortex-A + Cortex-M SoC such as the i.MX 93), Topo enables you to use it fully, deploying both firmware and application as containerized workloads through standard container tooling.
+
+Once a template is defined, use of Topo removes the need to deal with low-level setup and compatibility issues manually. Topo first assesses the system to identify processor features such as SVE or Neon on CPU, then advises which templates are appropriate for the device, before automating the deployment.
 
 Topo can also be leveraged by AI Agents to further streamline and automate.