From b4551c26de7f9f04132b72d6010d61e33b0b8ee4 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 19 Feb 2026 12:18:54 +0000
Subject: [PATCH] Address code review feedback for PR validator workflow

Co-authored-by: marcelscruz <12413903+marcelscruz@users.noreply.github.com>
---
 .github/workflows/pr-resource-validator.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/pr-resource-validator.md b/.github/workflows/pr-resource-validator.md
index e5c2c2a7..e6a693f1 100644
--- a/.github/workflows/pr-resource-validator.md
+++ b/.github/workflows/pr-resource-validator.md
@@ -49,7 +49,7 @@ Where:
 - Should be clear and concise
 
 ### 4. API Name Rules
-- Must NOT include the TLD (Top Level Domain) - e.g., ❌ "Gmail.com" ✔ "Gmail"
+- Must NOT include the TLD (top-level domain) - e.g., ❌ "Gmail.com" ✔ "Gmail"
 - Must NOT end with "API" - e.g., ❌ "Gmail API" ✔ "Gmail"
 
 ### 5. Alphabetical Ordering
@@ -58,7 +58,7 @@ Where:
 
 ### 6. PR Title Format
 - Must follow the pattern: "Add [API-name] API"
-- Example: "Add Blockchain API"
+- Example: "Add Blockchain API" (Note: The word "API" in the title is required by convention, even though API names themselves should not end with "API")
 
 ### 7. Commit Message
 - Should be descriptive, not generic
@@ -111,7 +111,7 @@ This pull request does not fully comply with the contributing guidelines. Please
 ...
 
 **Guidelines Reference:**
-Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) for detailed guidelines.
+Please review the [CONTRIBUTING.md](../../CONTRIBUTING.md) for detailed guidelines.
 
 **Need Help?**
 If you have questions, please comment on this PR and a maintainer will assist you.