Update website. Add InnerPipe section

Cargo.toml

@@ -20,7 +20,7 @@ default-run = "dtp-server"
 #
 # This make sure that your localnet, DTP and your app are all 
 # built and tested using the *same* binaries, saving you from chasing
-# unecessary problems of unmatching versions.
+# unnecessary problems of unmatching versions.
 #
 # The local version is initialized by the script:
 #   dtp/script/init-localnet

docs/src/.vuepress/theme.ts

@@ -66,6 +66,7 @@ export default hopeTheme({
       component: true,
       // demo: true,
       figure: false,
+      footnote: true,
       // flowchart: true, Needed?
       imgLazyload: true,
       imgSize: true,

docs/src/README.md

@@ -37,11 +37,11 @@ tagline: ""
 <a class="route-link vp-feature-item link" href="/" aria-label="Create Hybrid dApps" style="text-decoration: none">
   <h3 class="vp-feature-title">    
     <HopeIcon icon="star-half-stroke" color="light-blue"/>    
-    <span style="position: relative; top: 3px">Create hybrid dApps</span>
+    <span style="position: relative; top: 3px">Create Hybrid dApps</span>
   </h3>
   <p class="vp-feature-details">
     Decentralized connection control, metering and crypto-economics<br>
-    <b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+</b>
+    <b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+</b>
     <br>Your existing off-chain services and data.
   </p>
 </a>
@@ -64,9 +64,9 @@ tagline: ""
     <span style="position: relative; top: 3px">Privacy & Authenticity</span>
   </h3>
   <p class="vp-feature-details">
-    &bull; On-chain secret exchanges with end-to-end encryption.<br>
+    &bull; End-to-end encryption for on-chain secret exchanges.<br>
     &bull; Secured key/certificate installation from centralized servers.<br>
-    &bull; Authenticity with signed data transfer.<br> 
+    &bull; Signed data transfer for authenticity.<br> 
   </p>
 </a>
 
@@ -76,8 +76,8 @@ tagline: ""
     <span style="position: relative; top: 3px">Open-Source</span>
   </h3>
   <p class="vp-feature-details">    
-    &bull; Only code from developers for developers.<br>
-    &bull; No Token, middlemen, commission or dev fee.<br>
+    &bull; Code from developers for developers.<br>
+    &bull; No "DTP" Tokens, middlemen or dev fee.<br>
     &bull; Only requires smart contracts execution costs (gas fee for Sui transactions).<br>
   </p>
 </a>
@@ -111,19 +111,25 @@ tagline: ""
 
 <img src="/assets/images/total_vs_partial_order_small.PNG?url" style="float: left; padding-right: 20px;"/>
 
+
 <b> Why Sui and not blockchain 'x' ?</b><br>
 SUI has good finality latency stability (low jitter) and network scalability (maintains per connection throughput regardless of total load).<br>
 
-Sui architecture provides two type of transactions:
+Sui provides two type of processing:
 
-  * Simple Transaction with sub-second finality for data plane transfer (See 'partial ordering' illustration). This allows fast async/parallel transmission.
+<p>
+<ul style="padding-left: 40px;">
+  <li>Fast path transactions with sub-second finality for data plane transfer (See 'partial ordering' illustration). This facilitate async/parallel/scalable transmission.</li>
 
-  * Narwhal/Bullshark consensus with 2-3 seconds finality used for slower control plane synchronization, like escrow services, reconfiguration, connection creation,etc...
+  <li>Narwhal/Bullshark consensus with 2-3 seconds finality used for slower control plane synchronization, like connection creations, services and firewall reconfiguration etc...
+  </li>
+</ul>
+</p>
 
 
-With its flexible dual-type of transactions, Sui makes practical the implementation of common data + control plane design found in IP networks ( [Cloudflare explains it well](https://www.cloudflare.com/learning/network-layer/what-is-the-control-plane/) ).
+With its flexible dual-type transactions, Sui makes practical implementing the typical data + control plane design found in IP networks ( [Cloudflare explains it well](https://www.cloudflare.com/learning/network-layer/what-is-the-control-plane/) ).
 
-See [How Sui Differs from Other Blockchains?](https://docs.sui.io/learn/sui-compared)
+See [How Sui Differs from Other Blockchains?](https://docs.sui.io)
 
 Why not simply use the good old, faster and free internet?
 

docs/src/docs/README.md

@@ -21,9 +21,9 @@ The typical ```<IP address>:<Port>``` becomes a ```<Host Object ID>:<Port>```
 
 For security reason, each Host Object are by default created "completely closed". Using the DTP API, an application can choose to open ports of its Host object to progressively add services.
 
-Other application will be able to observe what other Host allow/block even before attempting to use their service. Even if an attacker try to use a service when they should not, it will be rejected by the DTP Move package on-chain, therefore have no impact on the destination.
+End-users will be able to observe what an Host allows (or blocks) even before attempting to use the service. An attacker trying to use a non-authorized service will be rejected by the DTP Move package on-chain (no impact on the server at all).
 
-The DTP API allows fine grain control of allowance/blocking of particular requester, connection count or bandwidth limit. Configuration are kept and applied 24/7 on-chain.
+The DTP API supports white/black listing of sender sui address and various traffic policies. Configuration are kept and applied 24/7 on-chain.
 
 ## Service Level Agreements (SLA)
 
@@ -33,20 +33,22 @@ When configuring a service for your Host, you must choose a "Service Level Agree
 
 An example is to require the requester to pay for the cost of the response that your server will have to provide.
 
-::: tip This is a good example where adding Web3 qualities to an existing Web2 service creates API monetization without requiring huge security/edge infrastructure investments
+::: tip Side Note
+This is a good example where adding Web3 qualities to an existing Web2 service creates API monetization without requiring huge security/edge infrastructure investments
 :::
 
 DTP defines a set of "Typical" service level agreement to help minimize market confusion. 
 
-| Service Level Agreement | Who Pays                                                 |
-| ----------------------- | -------------------------------------------------------- |
-| OpenDataStream          | Everyone pay for their own transactions (txns).          |
-| AudioStream-Free        | Broadcaster only.                                        |
-| JSON-RPC-BestEffort     | Everyone pay for their own txns. No response guaranteed. |
-| JSON-RPC-RequesterPaid  | RPC Requester pays. Responder refunded through escrow.   |
-| Ping-RequesterPaid      | RPC Requester pays. Responder refunded through escrow.   |
+| Service Level Agreement     | Who Pays                                                   |
+| --------------------------- | ---------------------------------------------------------- |
+| DataStream-Balanced         | Everyone pay for their own transactions (txns).            |
+| AudioStream-Free            | Broadcaster pays all transaction costs.                    |
+| JSON-RPC-Balanced           | Everyone pay for their own txns. Best-effort service.      |
+| JSON-RPC-RequesterPaid      | RPC Requester pays. Escrow for success/failure.            |
+| JSON-RPC-RequesterPaidPlus  | Same as above, plus the server charges additional fee.     |
+| Ping-RequesterPaid          | Ping Requester pays. Escrow for success/failure.           |
 
-The requester agree to the SLA upon creation of the connection and is enforced through DTP escrow for the connection duration. DTP handles the fund redistribution fairly with consideration of various success/failure criteria (more refinement will follow in ~2024).
+The requester agree to the SLA upon creation of the connection and is enforced through DTP escrow for the connection duration. DTP handles the fund redistribution fairly with consideration of various success/failure criteria (more refinement will follow in ~2025).