diff --git a/README.md b/README.md
index 35ef5de..afd8a4d 100644
--- a/README.md
+++ b/README.md
@@ -7,14 +7,13 @@ attributes used across various components of the TAP portfolio and higher educat
 normative documentation of the TAP Attribute Dictionary is abstract -- it is designed to be used only when mapped to specific formats and protocols. It is
 best thought of as an *attribute library* that can be drawn from to construct other documents, specifications, and software artifacts.
 
-When discussing schema, TAP uses two terms, formatting and protocol, in quite specific ways.
+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 form, such as
+* **Formatting**: Mappings of the TAP Attribute Dictionary entries to a specific markup form, such as
   JSON, XML, or YAML.
   * [TAP Attribute Dictionary: How to Create a JSON Representation](tap-core-person-schema-create-json-representation.adoc) (CS-JSON)
 
-* **Protocols**: A specification for implementation, based on a Representation
-  and perhaps a Profile. Of all the Core Schema documents, only Protocols are
-  actually implementable in software.
+* **Protocols**: A formal specification defining the way two entities interoperate to accomplish a specific action. Protocols are
+  designed to be implementable in software.
 
-As an example, **eduPerson LDAP** would be the eduPerson schema expressed in the **format** specified in RFC4519 LDAP Schema for User Applications for use with the LDAPv3 **Protocol** 
+As an example, **eduPerson LDIF** would refer to the eduPerson schema expressed in the **format** defined in _RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification_