Legal documentation has its own conventions which I am not remotely qualified to advise upon. In the event of uncertainty in legal documentation, it seems prudent to consult someone with a background in law.
(Law is an area I'm both quite interested in and very ignorant about, but I've yet to find a good on-ramp for learning about how to practically interact with legal institutions and processes. It seems like legal texts should be extremely unambiguous, because they are produced by institutions who are presumably aware of the problem of linguistic ambiguity, and otherwise how are legal documents supposed to do their job? Then I remember that the same argument can be made of technical documentation, and people who product that for a living can do a spectacularly poor job of it. Other fields presumably also have people who are bad at their jobs.)
It seems like legal texts should be extremely unambiguous, because they are produced by institutions who are presumably aware of the problem of linguistic ambiguity, and otherwise how are legal documents supposed to do their job?
That assumes that the linguistic ambiguity is bad for enough stakeholders.
A lobbyist who writes an amendment for a law doesn't always want that the politicians who vote on the amendment understand what it does.
An ambiguous version might also be a compromise that allows both sides of a conflict to avoid losing.
If it's worth saying, but not worth its own post (even in Discussion), then it goes here.
Notes for future OT posters:
1. Please add the 'open_thread' tag.
2. Check if there is an active Open Thread before posting a new one. (Immediately before; refresh the list-of-threads page before posting.)
3. Open Threads should be posted in Discussion, and not Main.
4. Open Threads should start on Monday, and end on Sunday.