More particular on updates

Author: felickz

.github/workflows/update-ghas-matrix.md

@@ -72,13 +72,9 @@ Look specifically for:
 ### Step 5: Evaluate Significance
 
 Apply the significance filter from the instructions file:
-- **INCLUDE:** New functionality, major gaps addressed, Preview→GA transitions, new CodeQL toolcache versions, partner pattern count changes, new versions, counts
+- **INCLUDE:** New functionality, new features, major gaps addressed, Preview→GA transitions, new CodeQL toolcache versions, partner pattern count changes, new versions, counts
 - **EXCLUDE:** Minor bug fixes, new language/framework version support (e.g., Go 1.25, Swift 6.2), simple renames, UI tweaks without functional impact
 
-Significant updates get a new row in the appropriate feature matrix.  The description should link to details when possible:
--  Favor a specific docs page (in case furture content is moved - https://docs.github.com/en/enterprise-server@latest is favored over a specific version to future proof EOL server versions in docs).  Review the https://docs.github.com/en/enterprise-server docs for that the given update to ensure the link is taking you a page where the appropriate feature is described. 
-- Otherwise, point to a specific changelog link (under https://github.blog/changelog/) that lists out which version of GHES the feature will belong to.
-- Finally, if there is no appropriate link that mentions the feature, then fallback to just a text description without a hyperlink.
 
 If there are no significant changes found, **do not create a PR**. Simply note that the matrix is up to date and exit.
 
@@ -90,6 +86,12 @@ If significant changes were found, follow the matrix update rules from the instr
 2. **For minor version changes:** Update the relevant cells in existing columns (e.g., change ☑️ to ✅ when a feature goes GA in a patch release).
 3. **For new features:** Add new rows with descriptive names and deep-linked documentation URLs.
 
+Significant updates get a new row in the appropriate feature matrix.  The description should link to details when possible:
+-  Favor a specific docs page (in case furture content is moved - https://docs.github.com/en/enterprise-server@latest is favored over a specific version to future proof EOL server versions in docs).  Review the https://docs.github.com/en/enterprise-server docs for that the given update to ensure the link is taking you a page where the appropriate feature is described. Ensure the link is taking you to an actual docs page, not a table of contents for more docs pages.
+- Otherwise, point to a specific changelog link (under https://github.blog/changelog/) that lists out which version of GHES the feature will belong to.
+- Finally, if there is no appropriate link that mentions the feature, then fallback to just a text description without a hyperlink.
+
+
 For CodeQL toolcache versions, check: `https://docs.github.com/en/enterprise-server@<VERSION>/admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance`
 
 For secret scanning partner pattern counts, check: `https://docs.github.com/en/enterprise-server@<VERSION>/code-security/secret-scanning/introduction/supported-secret-scanning-patterns`