- removing mention of "the rule" from label-in-name-algorithm.md . replacing it with a new idea: the algorithm 'return value' eg. 'returns "is contained"'.

- rewording rule expectation.  I think that 'For the target element' is better than 'For each target element' because for this rule, the computation of the expecation for each applicable target element is done in isolation from the other applicable targets on the page.  It's simpler if the "for loop" over all applicable targets is done by the tool, not the rule.

Author: dan-tripp-siteimprove

_rules/visible-label-in-accessible-name-2ee8b8.md

@@ -39,7 +39,7 @@ This rule applies to any element for which all the following is true:
 
 ## Expectation
 
-For each target element, the [visible inner text][] is contained within the [accessible name][] of the target element according to the [label in name algorithm][].
+For the target element, the [visible inner text][] is contained within the [accessible name][] according to the [label in name algorithm][].
 
 ## Assumptions
 

pages/glossary/label-in-name-algorithm.md

@@ -28,7 +28,7 @@ Then do the check: is the tokenized 'label' a sublist of the tokenized 'name'?
     - It checks whether elements are consecutive or not. i.e. it checks for a substring, in the computer science sense of the term. Not a subsequence.
     - An empty list is a sublist of any list.
 
-If the answer is "yes" (i.e. the tokenized 'label' a sublist of the tokenized 'name'), then the target element passes the rule.  Otherwise, it fails the rule.
+If the answer is "yes" (that is: the tokenized 'label' is a sublist of the tokenized 'name'), then this algorithm returns "is contained".  Otherwise, it returns "is not contained".
 
 [accessible name]: #accessible-name 'Definition of accessible name'
 [visible inner text]: #visible-inner-text 'Definition of Visible inner text'