Browse Source

PIP-0028: typo corrections

Herman Schoenfeld 6 years ago
parent
commit
2a8155cc9b
1 changed files with 5 additions and 5 deletions
  1. 5 5
      PIP/PIP-0028.md

+ 5 - 5
PIP/PIP-0028.md

@@ -11,17 +11,17 @@
 
 ## Summary
 
-This PIP proposes an operation encoding scheme to simplify integration into Layer-1 by Layer-2 Smart Contracts and also 3rd party infrastructure such as exchanges and wallet providers.
+This PIP proposes an operation encoding scheme to simplify integration into Layer-1 by Layer-2 Smart Contracts and 3rd party infrastructure providers such as exchanges and wallets.
 
 ## Motivation
 
-PascalCoin currently allows external software to send/receive operations via a JSON API. This requires the 3rd party systems conenct to a live trusted node and interact programmatically.  
+PascalCoin currently allows external software to send/receive operations via a JSON API. This requires that the 3rd party systems maintain and connect to local trusted node, for programmatic interaction.
 
-This can be undesirable since 3rd parties may which to provide separation between their systems and node as well require ability for offline operation creation (cold-signing). Layer-2 smart-contracts also need a concise and simple method to submit Layer-1 operations between nodes.
+This can be undesirable since 3rd parties may which to integrate into PascalCoin in decoupled manner as well as create operations when node is offline (cold-signing, or operation batching). Layer-2 smart-contracts fall into this catagory and need a concise and simple method to integrate into Layer-1 without heavy burdeon of maintaining a live node.
 
-In combination with [E-PASA][1], this PIP allows external software to trivially integrate into PascalCoin by sending single E-OP's to either a JSON API or a In folder which is picked up by the node.
+In combination with [E-PASA][1], this PIP allows external software to trivially integrate into PascalCoin by creating one-line text-bsaed E-Operations (Extended Operations) which can be submitted for processing by dumping them into an **IN** folder for pickup by the node. They can also be submitted using simplified JSON API and for logging/auditing purposes.
 
-This proposal will greatly simplify exchange and wallet integrations as well as allow Layer-2 applications to submit Layer-1 operations with great ease.
+This proposal, if implemented, will also greatly simplify exchange and wallet integrations as well as allow Layer-2 applications to submit Layer-1 operations with great ease.
 
 ## Specification