--- a/latest/payment-agent/index.html	Sat Apr 11 17:46:12 2015 -0400
+++ b/latest/payment-agent/index.html	Sun Apr 12 23:06:01 2015 -0500
@@ -127,19 +127,19 @@
   <section> 
     <h3>Elements of a Unified Web Payments Architecture</h3> 
    This section outlines a higher level, easy to understand description of elements needed to support payments on the web in a manner which acheives above listed goals.  This section may also list known  available or in process standards that can help to leverage corresponding standards that have already been created.
-   <section><h4>Towards a unified Web Payments Architecture - Simple example and core components</h4></section>
+   <section><h4>Towards a unified Web Payments Architecture - Simple example and core functionality</h4></section>
    <section><h4>User Agent</h4></section>
-   <section><h4>Identity and Authentication API</h4></section>
-   <section><h4>Credential API</h4></section>
-   <section><h4>Digital Signature API</h4></section>
-   <section><h4>Loyalty API</h4></section>
-   <section><h4>Ledger and Accounting API</h4></section>
-   <section><h4>Taxation API</h4></section>
-   <section><h4>Receipts and Invoicing API</h4></section>
-   <section><h4>Payment Messaging, Clearing and Settlement API</h4></section>
-   <section><h4>Delivery and Shipping API</h4></section>
+   <section><h4>Identity and Authentication Functionality</h4></section>
+   <section><h4>Credential Functionality</h4></section>
+   <section><h4>Digital Signature Functionality</h4></section>
+   <section><h4>Loyalty Functionality</h4></section>
+   <section><h4>Ledger and Accounting Functionality</h4></section>
+   <section><h4>Taxation Functionality</h4></section>
+   <section><h4>Receipts and Invoicing Functionality</h4></section>
+   <section><h4>Payment Messaging, Clearing and Settlement Functionality</h4></section>
+   <section><h4>Delivery and Shipping Functionality</h4></section>
    <section><h4>Payment Scheduling and Calendering</h4></section>
-   <section><h4>Receipts and Invoicing API</h4></section>
+   <section><h4>Receipts and Invoicing Functionality</h4></section>
    <section><h4>Regulatory and Reporting</h4></section>
    <section><h4>Wallet and Instrument provisioning and administration</h4></section>
    <section><h4>Security and Auditing</h4></section>
@@ -193,7 +193,7 @@
 			<h3>Required (core) Capabilities</h3> 
 	    	<p>This section outlines the required capabilities that all User Agents involved with the payments process and associated communication protocols must provide to meet minimal viable 				requirements:
 				<ul>
-					<li>Ability to receive and reply with standard formatted messages following payment agent API/protocol specifications</li>
+					<li>Ability to receive and reply with standard formatted messages following payment agent functional/protocol specifications</li>
 					<li>Abiltiy to interact with user agent Display Services for displaying payment related information</li>
 					<li>Ability support synchornization between multiple payment agents operating on behalf of a single user agent</li>
 					<li>Ability to support user agents running locally and remotely from payment agent</li>
@@ -226,7 +226,7 @@
 	  <section>
 	  	<h2>API Reference</h2>
 		<p>
-			The Payment Agent API is a standard protocol and set of API's which facilitate exchange of payment related data in a standard manner with user agents.  The following is a list of the API's that the Payment Agent protocol will support:
+			The Payment Agent Protocol is a standard protocol and set of capabilities's which facilitate exchange of payment related data in a standard manner with user agents.  The following is a list of the capabilities's that the Payment Agent protocol will support:
 			<ul>
 				<li>Identification and Authentication of Payment Participants</li>
 				<li>Payment Scheme/Instrument selection, clearing and settlement</li>