diff --git a/README.md b/README.md
index 6e7f9dc..293bdc7 100644
--- a/README.md
+++ b/README.md
@@ -9,14 +9,14 @@ The normative specification of the TAP Attribute Dictionary is an abstract data
 
 TAP uses the word "schema" as a rather broad and loose term for data models generally. However, beyond that, TAP provides careful definitions of two specific schema-related terms, "format" and "protocol".
 
-* **Formatting**: Mappings of the TAP Attribute Dictionary entries to a specific markup form, such as
+* **Representation**: Mappings of the TAP Attribute Dictionary entries to a specific markup form, such as
   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
+* **Protocol**: A formal specification defining the specific ways two entities interoperate to accomplish a set of actions. Protocols are
   designed to be implementable in software.
 
-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 1: "eduPerson LDIF" would refer to eduPerson attributes expressed in the LDIF **Representation** 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_