better example of weights.

1 files changed, 4 insertions, 4 deletions

diff --git a/57.md b/57.md
index a221481..cb6a290 100644
--- a/57.md
+++ b/57.md
@@ -170,12 +170,12 @@ A client can retrieve `zap receipt`s on events and pubkeys using a NIP-01 filter
 
 When an event includes one or more `zap` tags, clients SHOULD calculate the lnurl pay request based on their value instead of the profile's field. The tag's second argument is a `lud06` address, a `lud16` identifier or a `hex` string of the receiver's pub key. An optional third argument specifies the type of the previous value: `lud06`, `lud16` or `pubkey`. An optional fourth parameter specifies the weight (a generalization of a percentage) assigned to the respective receiver. Clients should parse all weights, calculate a sum, and then a percentage to each receiver. If weights are not present, CLIENTS should equally divide the zap amount to all receivers. If weights are only partially present, receivers without a weight should not be zapped (`weight = 0`).
 
-```json
+```js
 {
     "tags": [
-        [ "zap", "LNURL..", "lud06", "10" ],  // 10%
-        [ "zap", "pablo@f7z.io", "lud16", "65" ], // 65%
-        [ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c", "pubkey", "25" ] // 25%
+        [ "zap", "LNURL..", "lud06", "1" ],  // 25%
+        [ "zap", "pablo@f7z.io", "lud16", "1" ], // 25%
+        [ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c", "pubkey", "2" ] // 50%
     ]
 }
 ```