Teeny tiny documentation update to Sortlist feature [BUGS 42615]

From BUG ticket #42615 and Support ticket #10120

(This one is trivial to do by the way)

---

The sortlist statement can have multiple matching address match lists with corresponding sorts defined for them.

The question arose - what if the address match lists are not mutually exclusive but overlap - which sort definition is used - first, or last, or are they merged in some fashion?

For example:

acl acl_netlist_1 { 10.1/16; 10.2.2.2; };

acl acl_netlist_2 { 10.2/16; 10.1.1.1; };

sortlist {

{ acl_netlist_1; { acl_sort1; }; };

{ acl_netlist_2; { acl_sort2; }; };

};

What happens to queries from clients and 10.2.2.2, since they match both acl_netlist_1 and acl_netlist_2?

The answer is that 'first match wins' so they will both get acl_sort_1 - but this is not clear from the ARM. Please can we add a sentence just to make this clear.