[Chore] (Config): point the two stale comments at the renamed feature fields

MobileGL/MG_IntegrationTest/Scenarios/IterationRPFirstReductionScenario.cpp

@@ -137,7 +137,7 @@ namespace MGITest {
             // invocations, i.e. an advertised subgroup width in [16, 256]. A device
             // outside that window (lavapipe's 8-lane subgroups give 64 subgroups) cannot
             // run the fixture's verbatim reduction at all, so the scenario SKIPS there -
-            // the pack itself replays through the FixIterationRPSubgroupScratch patch, which
+            // the pack itself replays through the MagmaFixIterationRPSubgroupScratch patch, which
             // this probe deliberately does not model. The width only gates the domain;
             // lane placement and group counts still come from observed values alone.
             bool SubgroupWidthInSourceDomain() const {

MobileGL/MG_Util/ShaderTranspiler/TranslationCache.h

@@ -631,7 +631,7 @@ namespace MobileGL::MG_Util::ShaderTranspiler {
         // --- driver capability bits that arm or steer a pass ---
         // Whether LowerViewportIndexForEssl runs on this module. NOT the raw
         // GL_OES_viewport_array bit any more: the routing emulation arms the pass even where the
-        // extension exists (Config.h, ViewportArrayEmulation), so the extension alone no longer
+        // extension exists (Config.h, EsprytViewportArrayEmulation), so the extension alone no longer
         // decides, and a key carrying only it would serve a module lowered under one setting to a
         // link made under the other.
         Bool viewportIndexLoweringArmed = false;