diff --git a/tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ScriptAnalysis/ScriptTagCatalogTests.cs b/tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ScriptAnalysis/ScriptTagCatalogTests.cs
index c47b3323..10259d21 100644
--- a/tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ScriptAnalysis/ScriptTagCatalogTests.cs
+++ b/tests/Server/ZB.MOM.WW.OtOpcUa.AdminUI.Tests/ScriptAnalysis/ScriptTagCatalogTests.cs
@@ -16,8 +16,8 @@ namespace ZB.MOM.WW.OtOpcUa.AdminUI.Tests.ScriptAnalysis;
 /// Fidelity finding (see <see cref="ScriptTagCatalog"/> doc comment): the runtime Akka path resolves
 /// a <c>ctx.GetTag</c> literal against the driver <b>FullName</b> (the wire reference in
 /// <c>Tag.TagConfig.FullName</c>), NOT the UNS browse path — the UNS-path engine is dormant. The
-/// catalog therefore emits the FullName for equipment tags, the MXAccess dot-ref for SystemPlatform
-/// tags, and the leaf Name for virtual tags, and deliberately omits UNS browse paths. These
+/// catalog therefore emits the FullName for equipment tags, the MXAccess dot-ref for FolderPath-scoped
+/// tags (EquipmentId null), and the leaf Name for virtual tags, and deliberately omits UNS browse paths. These
 /// assertions check the resolvable key is present AND that the UNS browse paths are absent.
 /// </remarks>
 [Trait("Category", "Unit")]