Topo template tech review 2

Author: matt-cossins

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

@@ -10,6 +10,8 @@ layout: learningpathall
 
 If you already have a Docker Compose project and want to convert it to a Topo Template, or you want to create your own Topo Template from scratch, you can do so with an Agent Skill.
 
+These skills are optional authoring aids. The Template you created in this Learning Path works with Topo without them.
+
 Visit [Topo Skills](https://github.com/arm/topo-template-format#authoring-skills) for the most up-to-date list of the available Topo Template skills and instructions on how to install them.
 
 At the time of writing, the [Topo Template Format Specification](https://github.com/arm/topo-template-format) provides the following skills:

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

@@ -111,6 +111,8 @@ RUN sed -i "s|__ACCENT_COLOR__|${ACCENT_COLOR}|g" /usr/share/nginx/html/index.ht
 
 Topo passes configuration values to Templates through Docker build arguments. The `ARG` lines define the values consumed during the image build.
 
+`sed` is a command-line text replacement tool. The `sed` commands replace placeholder text in `index.html` during the image build, so each cloned project can customize the web page without manually editing the source file.
+
 ### Create the compose file
 
 Create `compose.yaml`:
@@ -168,6 +170,8 @@ The `x-topo` section is the Topo metadata block:
 
 The argument names in `x-topo.args` match the keys under `services.message-card.build.args`. When Topo resolves the arguments, it writes the selected values into the build arguments.
 
+The same argument name appears in three places: `x-topo.args` defines what Topo asks for, `build.args` passes the value to Docker, and the Dockerfile `ARG` consumes it.
+
 ### Clone the local Template
 
 Clone your local Template into a new project directory. You can choose to answer interactive prompts for the arguments (using the first command below), or you can opt to include the arguments in the command (using the second command).
@@ -208,6 +212,12 @@ services:
 
 ### Deploy the new project
 
+Check that your target is ready:
+
+```bash
+topo health --target user@my-target
+```
+
 Deploy the cloned project to your target:
 
 ```bash

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

@@ -6,7 +6,7 @@ weight: 3
 layout: learningpathall
 ---
 
-This section quickly runs through the deployment of the `Hello World` Template, similar to the LLM on CPU Template in the [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/) Learning Path.
+This section quickly runs through the deployment of the `Hello World` Template, similar to the `CPU LLM Chat` Template in the [Deploy containerized workloads to Arm-based Linux targets with Topo](/learning-paths/cross-platform/deploy-containerized-workloads-with-topo/) Learning Path.
 
 ## Clone the 'Hello World' Topo Template
 

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

@@ -56,8 +56,6 @@ To create a Topo Template, start with a Docker Compose project and add `x-topo`
 2. Hardware requirements (features like SVE or Neon, or required RAM).
 3. Project configuration at Topo clone time.
 
-We will achieve this by the end of this Learning Path.
-
 ## What you've accomplished and what's next
 
 You should now understand what a Topo Template is, and why you might create one. Next we will take an existing Template and customize it, before moving onto creating a Template from scratch.