Move DNS-SD TXT record info out of RAML into new 3.1 (as recently done for IS-04, etc.)
Use 'global configuration resource' and 'global configuration parameters' consistently
Specify that the System ID MUST be assigned 'uniquely' rather than 'randomly'
Sync 2.2 with IS-04 (adds Empty Request Bodies clarification)
Sync 2.3 with IS-04 (adds clarification on CORS/OPTIONS requests)
Use api.example.com rather than example.api.com, since api.com is registered to GE Healthcare Life Sciences, now Cytiva, whereas example.com is provided for this purpose.
Fix several typos.
Tweak "tags" example since a System API for a particular recording seems unlikely, so it was a bit confusing?
I will base a PR to clarify the Node interaction with the System API at start-up on top of this.
I will base a PR to clarify the Node interaction with the System API at start-up on top of this.