update tags.yaml instructions

Signed-off-by: Riaan Kleinhans <[email protected]>

Author: riaankleinhans

README.md

@@ -110,4 +110,4 @@ The current Technical Advisory Groups will be spun down during 2025 and replaced
 
 ### Updating TAG or SubProject README files
 
-To modify the README files for individual TAGs or subprojects, please **do not edit them directly**. Instead, the source of truth for these files is the [`tags.yaml`](https://github.com/cncf/toc/blob/main/tags.yaml) file. To understand the process for updating these READMEs by modifying `tags.yaml`, please refer to the [Updating TOC TAG and Subproject README Files document](./generator/updating-tag-and-toc=subproject-readme-files.md).
+To modify the README files for individual TAGs or TOC SubProjects, please **do not edit them directly**. Instead, the source of truth for these files is the [`tags.yaml`](https://github.com/cncf/toc/blob/main/tags.yaml) file. To understand the process for updating these READMEs by modifying `tags.yaml`, please refer to the [Updating TOC TAG and SubProject README Files document](./generator/updating-tag-and-toc=subproject-readme-files.md).

generator/updating-tag-and-toc=subproject-readme-files.md

@@ -1,16 +1,16 @@
-# Updating TOC TAG and Subproject README Files
+# Updating TOC TAG and TOC SubProject README Files
 
 This document outlines the process for updating the README files located in the [tags](https://github.com/cncf/toc/tree/main/tags) and [toc_subprojects](https://github.com/cncf/toc/tree/main/toc_subprojects) directories. These README files are automatically generated and updated based on the content of the [`tags.yaml`](https://github.com/cncf/toc/blob/main/tags.yaml) file.
 
-**The Single Source of Truth: `tags.yaml`**
+## **The Single Source of Truth: `tags.yaml`**
 
-The `tags.yaml` file serves as the central source of information for generating and updating the README files for both TAGs and subprojects. To modify the content of these READMEs, you **must** update the `tags.yaml` file directly.
+The `tags.yaml` file serves as the central source of information for generating and updating the README files for both TAGs and TOC SubProjects. To modify the content of these READMEs, you **must** update the `tags.yaml` file directly.
 
-**Who can Update:**
+## **Who can Update:**
 
 Anyone can create a pull request in the `cncf/toc` repository, only TOC members can review and merge changes to the `tags.yaml` file.
 
-**How to Update:**
+## **How to Update:**
 
 1.  **Locate the `tags.yaml` file:** This file is located at the root of the `cncf/toc` repository: [https://github.com/cncf/toc/blob/main/tags.yaml](https://github.com/cncf/toc/blob/main/tags.yaml).
 
@@ -19,7 +19,7 @@ Anyone can create a pull request in the `cncf/toc` repository, only TOC members
 3.  **Create a Pull Request (PR):**
     * **Important:** A PR that aims to update the TAG and subproject README files **must only contain changes to the `tags.yaml` file.** Any other changes in the PR will not trigger the automatic README updates.
 
-**Automation in Action:**
+## **Automation in Action:**
 
 The `github-project-automation` and `cncf-automation-bot` handle the automatic updates of the README files based on your changes to `tags.yaml`:
 
@@ -34,6 +34,6 @@ The `github-project-automation` and `cncf-automation-bot` handle the automatic u
         * This new PR will contain both your changes to the `tags.yaml` file and the automatically generated updates to the relevant README files.
         * The `cncf-automation-bot` will automatically close the original PR from your fork and add comments to both the original and the new PR to link them.
 
-**Key Takeaway:**
+## **Key Takeaway:**
 
 To update the README files in the `tags` and `toc_subprojects` directories, your PR **must only include modifications to the `tags.yaml` file**. The automation will then take care of generating and updating the corresponding README files.