Why Topo ? Automated deployment !

Topo not only saves you the troubles of setting everything up,
making sure there are no incompatibility issues as well as having
the necessary dependencies, etc.

Topo also helps you deploy in a simple command.
Instead of having to execute multiple SSH + container engine commands
all in sequence, Topo automates all of that away so that you don't have
to deal with that.

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

@@ -21,7 +21,7 @@ The optional heterogeneous deployment with `remoteproc-runtime` requires a heter
 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.
+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 end to end deployment, for which Topo deals with all the low-level instructions.
 
 Topo can also be leveraged by AI Agents to further streamline and automate.