AOs shouldn't be represented as tables #3645
Description
Two AOs in the specification are defined using tables instead of a sequence of steps. They are, namely:
This is problematic because, as confirmed by @jhnaldo in a previous conversation, ESMeta does not currently parse algorithms specified using the table format.
To fix that, and to improve the overall consistency of the specification text, I suggest an editorial change to turn those AOs to a sequence of steps surrounded by an emu-alg tag.