Topo: correct the warning terminology

In certain scenarios, Warnings can indicate that the user needs to
install something in the target. Topo is unsure as to whether this
will be needed or not in the user's project, so it turns the missing
dependency into a warning rather than an error, but this doesn't
mean that the dependency is entirely optional in all scenarios.

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

Author: tgonzalezorlandoarm

content/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/assess-compatibility.md

@@ -86,7 +86,7 @@ Subsystem Driver (remoteproc): ✅ (m33, m0)
 
 A Topo health check confirms connectivity between the host and target, as well as the verifying the presence of dependencies such as docker.
 
-You should resolve any `❌` errors before moving on. Warnings (`⚠️`) can indicate optional capabilities you can add later. `ℹ️` provides other information. A `✅` confirms the presence of dependencies and no warnings or errors.
+You should resolve any `❌` errors before moving on. Warnings (⚠️) can indicate optional capabilities that may be needed in certain projects. `ℹ️` provides other information. A `✅` confirms the presence of dependencies and no warnings or errors.
 
 If you are using password-based SSH, you will likely see the `❌` error below: