Clarify TCK challenge process as required by the Specification Committee

README.md

diff --git a/README.md b/README.md
index 6b581a0..cae96d5 100644
--- a/README.md
+++ b/README.md
@@ -36,4 +36,9 @@
 
 ## About Jakarta Expression Language
 
-Jakarta Expression Language defines an expression language for Java applications.
\ No newline at end of file
+Jakarta Expression Language defines an expression language for Java applications.
+
+## TCK Challenges
+
+All test challenges for Jakarta Expression Language must be resolved by Active Resolution.
+Please see the TCK Users guide for more details.
\ No newline at end of file

tck/docs/userguide/src/main/jbake/content/rules.adoc

diff --git a/tck/docs/userguide/src/main/jbake/content/rules.adoc b/tck/docs/userguide/src/main/jbake/content/rules.adoc
index f6b08ce..105d67a 100644
--- a/tck/docs/userguide/src/main/jbake/content/rules.adoc
+++ b/tck/docs/userguide/src/main/jbake/content/rules.adoc
@@ -355,9 +355,8 @@
 * A full description of why the test is invalid and what the correct behavior is believed to be
 * Any supporting material; debug logs, test output, test logs, run scripts, etc.
 
-
-
 2. Specification project evaluates the challenge. +
+This specification requires that all test challenges follow the "Active Resolution" process as described in the https://jakarta.ee/committees/specification/tckprocess/[Jakarta EE TCK Process Guide]. This team will attempt to take timely action in response to your challenge.
 Challenges can be resolved by a specification project lead, or a project challenge triage team, after a consensus of the specification project committers is reached or attempts to gain consensus fails.
 Specification projects may exercise lazy consensus, voting or any practice that follows the principles of Eclipse Foundation Development Process.
 The expected timeframe for a response is two weeks or less.