Inconsistent use of "authorized" and "authorised", which is especially problematic for the "status" value examples (unless we add both values)

[fordmadox]

The status example in all 3 tag libraries lists "authorised" whereas "authorized" is recorded in the EAS BPG markdown system of record (and used narratively elsewhere).

Creator of issue

1. Mark Custer

The issue relates to

• EAC-CPF schema issue
• [X ] EAC-CPF Tag Library issue
• EAC-F schema issue
• [ X] EAC-F Tag Library issue
• EAD schema issue
• [ x] EAD Tag Library issue
• Schema issue
• Tag Library issue
• Suggestions for all schemas
• Suggestions for all Tag Libraries
• Other

Wanted change/feature

• Text: all 4 examples in each of the 3 tag libraries should be updated from "authorised" to "authorized".

Reporting a bug

• Text:

Suggested Solution

• Text:

Steps to Reproduce (for bugs)

Context

• Text:

Your Environment can be a clue to a bug

• Version used:
• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):

[ailie-s]

Updated spelling in <agencyCode>, <referringString> and @standardDateTime. Changes are reflected in HTML and PDF files in PR #233

[ailie-s]

There are some further spelling issues in EAD-specifc text, which I have not edited:

• <label> - digitised
• <textualDate> - standardised
• <unitDate> - standardised