Merge pull request #3367 from tgonzalezorlandoarm/main

Update learning_objectives for the Topo Templates LP + capitalization

Author: pareenaverma

content/learning-paths/cross-platform/create-your-own-topo-templates/_index.md

@@ -1,5 +1,5 @@
 ---
-title: Create your own Topo templates
+title: Create your own Topo Templates
 
 draft: true
 cascade:
@@ -12,17 +12,17 @@ minutes_to_complete: 30
 who_is_this_for: This is an introductory topic for embedded, edge, and cloud software developers who want to create their own Topo Templates projects to be natively deployed with Topo.
 
 learning_objectives:
-    - Install Topo and verify that the host and target environments are ready for deployment
-    - Run health checks and generate a target description to identify compatible Arm processor features and templates
-    - Clone a Topo template and deploy a containerized workload to an Arm-based Linux target
-    - (Optional) Deploy firmware and applications to heterogeneous Cortex-A + Cortex-M devices using remoteproc-runtime
+    - Explain the purpose and structure of a Topo Template
+    - Clone and deploy an existing Topo Template to validate the Template workflow
+    - Add clone-time arguments to customize a Topo Template
+    - Create a new Topo Template from a Docker Compose project
+    - Add x-topo metadata for configurable arguments, deployment guidance, and hardware requirements
 
 prerequisites:
     - This learning path builds on [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/).
     - A host machine (x86 or Arm) with Linux, macOS, or Windows
-    - An Arm-based Linux target accessible over SSH, for example an Arm-based Linux VM, Raspberry Pi, DGX Spark, or NXP i.MX 93
+    - (Optional) An Arm-based Linux target accessible over SSH, for example an Arm-based Linux VM, Raspberry Pi, DGX Spark, or NXP i.MX 93
     - Docker installed on the host and target. For installation steps, see [Install Docker](/install-guides/docker/).
-    - lscpu installed on the target (pre-installed on most Linux distributions)
     - Basic familiarity with containers and CLI tools
 
 author: Tomas Agustin Gonzalez Orlando
@@ -52,7 +52,7 @@ shared_between:
 
 further_reading:
     - resource:
-        title: Topo template format
+        title: Topo Template format
         link: https://github.com/arm/topo-template-format
         type: documentation
     - resource:

content/learning-paths/cross-platform/create-your-own-topo-templates/creating-a-new-template.md

@@ -109,7 +109,7 @@ RUN sed -i "s|{{CARD_MESSAGE}}|${CARD_MESSAGE}|g" /usr/share/nginx/html/index.ht
 RUN sed -i "s|{{ACCENT_COLOR}}|${ACCENT_COLOR}|g" /usr/share/nginx/html/index.html
 ```
 
-Topo passes configuration values to templates through Docker build arguments. The `ARG` lines define the values consumed during the image build.
+Topo passes configuration values to Templates through Docker build arguments. The `ARG` lines define the values consumed during the image build.
 
 ### Create the compose file
 

content/learning-paths/cross-platform/create-your-own-topo-templates/hello-world-template.md

@@ -16,7 +16,7 @@ List the available Topo Templates from the curated list in Topo:
 topo templates
 ```
 
-The output should be similar to the following, the Hello World template should be present:
+The output should be similar to the following, the Hello World Template should be present:
 
 ```output
 Hello World | https://github.com/Arm-Examples/topo-welcome.git | main
@@ -34,7 +34,7 @@ Lightbulb Moment | https://github.com/Arm-Examples/topo-lightbulb-moment.git | m
 (...)
 ```
 
-### Clone the Hello World template
+### Clone the Hello World Template
 
 ```bash
 topo clone https://github.com/Arm-Examples/topo-welcome.git

content/learning-paths/cross-platform/create-your-own-topo-templates/modifying-hello-world.md

@@ -8,9 +8,9 @@ layout: learningpathall
 
 ## Modify the Hello World Template
 
-In the previous section, you cloned and deployed the Hello World Template. In this section, you will modify the template so the greeting emoji can be configured when someone clones the template.
+In the previous section, you cloned and deployed the Hello World Template. In this section, you will modify the Template so the greeting emoji can be configured when someone clones the Template.
 
-### Add a new template argument
+### Add a new Template argument
 
 Open the Hello World Template `compose.yaml` file:
 
@@ -82,7 +82,7 @@ Open the HTML file used by the web application. Find the line with the hard-code
 <span class="emoji floating">🐳</span>
 ```
 
-Replace it with the `GREETING_EMOJI` template variable:
+Replace it with the `GREETING_EMOJI` Template variable:
 
 ```html
 <span class="emoji floating">{{GREETING_EMOJI}}</span>
@@ -114,21 +114,21 @@ RUN sed -i "s|{{GREETING_NAME}}|${GREETING_NAME}|" /usr/share/nginx/html/index.h
 RUN sed -i "s|{{GREETING_EMOJI}}|${GREETING_EMOJI}|" /usr/share/nginx/html/index.html
 ```
 
-### Clone the modified template
+### Clone the modified Template
 
-Create a new directory for a fresh clone of your modified local template:
+Create a new directory for a fresh clone of your modified local Template:
 
 ```bash
 mkdir ../newdir/
 ```
 
-Clone the local template into the new directory:
+Clone the local Template into the new directory:
 
 ```bash
 topo clone dir:/home/tomgon01/eco/topo/playground/topo-welcome ../newdir/topo-welcome
 ```
 
-Topo prompts for the configured template arguments. You should now see prompts for both `GREETING_NAME` and `GREETING_EMOJI`. Use the example values, do not accept the defaults. When cloning completes, Topo creates the new project in `../newdir/topo-welcome`:
+Topo prompts for the configured Template arguments. You should now see prompts for both `GREETING_NAME` and `GREETING_EMOJI`. Use the example values, do not accept the defaults. When cloning completes, Topo creates the new project in `../newdir/topo-welcome`:
 
 ```output
 ┌─ Copy files ──────────────────────────────────────────

content/learning-paths/cross-platform/create-your-own-topo-templates/overview.md

@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## Get started
 
-Before getting started, you should complete the Learning Path [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/) to learn about Topo, why to use it, how to install it and how to use it for target inspection, listing templates and deployment.
+Before getting started, you should complete the Learning Path [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/) to learn about Topo, why to use it, how to install it and how to use it for target inspection, listing Templates and deployment.
 
 ## What is Topo?
 
@@ -28,8 +28,8 @@ Because the Topo Templates specification is an open one, anyone can publish thei
 
 A curated list of example Templates can be found either via:
 
-1. the [topo templates](https://github.com/arm/topo?tab=readme-ov-file#3-find-a-template) command or
-2. the [topo catalog](https://github.com/arm/topo/blob/main/internal/catalog/data/templates.json).
+1. the [Topo Templates](https://github.com/arm/topo?tab=readme-ov-file#3-find-a-template) command or
+2. the [Topo catalog](https://github.com/arm/topo/blob/main/internal/catalog/data/templates.json).
 
 If you create your own Template, you can [Propose Your Template to Topo](https://github.com/arm/topo-template-format#propose-your-template-to-topo)
 
@@ -47,4 +47,4 @@ You can then share your Topo Template with the community, who will be able to de
 
 You have now installed Topo on your host and confirmed it is available.
 You have got an understanding of what a Topo Template is and what its purpose is.
-Next, you'll clone your first template and modify it.
+Next, you'll clone your first Template and modify it.