Portage doesn't treat things listed in USE_EXPAND as incremental, and
nothing relies upon it behaving either way. Since that's the case, we
don't really want USE_EXPAND_VALUES_* vars being special either.
---
 profile-variables.tex |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/profile-variables.tex b/profile-variables.tex
index 76623e3..9ac607e 100644
--- a/profile-variables.tex
+++ b/profile-variables.tex
@@ -18,7 +18,6 @@ variables must be treated in this fashion:
 \item \t{USE\_EXPAND\_HIDDEN}
 \item \t{CONFIG\_PROTECT}
 \item \t{CONFIG\_PROTECT\_MASK}
-\item Any variable whose name is listed in \t{USE\_EXPAND}
 \end{compactitem}
 
 If the package manager supports any EAPI listed in table~\ref{tab:profile-iuse-injection-table} as
@@ -28,8 +27,6 @@ incrementally; otherwise, the following variables may or may not be treated incr
 \item \t{IUSE\_IMPLICIT}
 \item \t{USE\_EXPAND\_IMPLICIT}
 \item \t{USE\_EXPAND\_UNPREFIXED}
-\item Any variable whose name is \t{USE\_EXPAND\_VALUES\_\$\{value\}}, where \t{\$\{value\}} is any
-    value in \t{USE\_EXPAND\_IMPLICIT}.
 \end{compactitem}
 
 Other variables, except where they affect only package-manager-specific functionality (such as
-- 
1.6.2