terminology updates

README.md

@@ -10,13 +10,13 @@ best thought of as an *attribute library* that can be drawn from to construct ot
 When discussing schema, TAP defines two terms, formatting and protocol, in quite specific ways.
 
 * **Formatting**: Mappings of the TAP Attribute Dictionary entries to a specific markup form, such as
-  JSON, XML, or YAML.
+  JSON, XML, LDAP, or YAML.
   * [TAP Attribute Dictionary: How to Create a JSON Representation](tap-core-person-schema-create-json-representation.adoc) (CS-JSON)
 
 * **Protocols**: A formal specification defining the way two entities interoperate to accomplish a specific action. Protocols are
   designed to be implementable in software.
 
-Example 1: "eduPerson LDIF" would refer to the eduPerson attributes expressed in the **format** defined in _RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification_
+Example 1: "eduPerson LDIF" would refer to eduPerson attributes expressed in the **format** defined in _RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification_
 
 Example 2: eduPerson attributes on an LDAP server can be queried by an LDAP client using the LDAP **protocol** defined in _RFC4519 Lightweight Directory Access Protocol (LDAP) Schema for User Applications_