From 510b3d9491ba47c518816161ad12e0ff412efcb8 Mon Sep 17 00:00:00 2001 From: landonMutch Date: Fri, 3 Mar 2023 13:27:12 +0900 Subject: [PATCH] spell check --- 69.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/69.md b/69.md index 943ac4de..f7fc31d0 100644 --- a/69.md +++ b/69.md @@ -20,7 +20,7 @@ A poll event: ```json { - "id": <32-bytes lowercase hex-encoded sha256 of the the serialized event data> + "id": <32-bytes lowercase hex-encoded sha256 of the serialized event data> "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>, "created_at": , "kind": 6969, @@ -33,7 +33,7 @@ A poll event: ["n", ], ], ["tally_method", "value"||"count"], - ["consensus_threshold", ], + ["consensus_threshold", ], ["closed_at", ], ], "content": , @@ -47,7 +47,7 @@ Poll options are voted on by sending [zap events](57.md) (to the original poll e Zap vote events (kind `9734` and `9735`): * MUST include exactly 1 `poll_option` tag -* MUST reference the vote option by its corresponding integar `n`, chosen from the original poll event's list of predefined `polling_options` +* MUST reference the vote option by its corresponding integer `n`, chosen from the original poll event's list of predefined `polling_options` * MUST transmit the exact `poll_option` between kind `9734` and `9735` ```json @@ -74,8 +74,8 @@ A tallying client: * MUST NOT count votes from anonymous users * MUST treat the vote option with the most unique votes as the winning option * when a `closed_at` time is specified, clients: - * MUST NOT include late votes recieved after `closed_at` time - * SHOULD publicly blind results until after a user's vote has been recieved + * MUST NOT include late votes received after `closed_at` time + * SHOULD publicly blind results until after a user's vote has been received * SHOULD publicly display results after the `closed_at` time has passed * when a `closed_at` time is NOT specified (is less than or equal to `created_at`), clients: * SHOULD include all votes in tallies @@ -87,7 +87,7 @@ After the above rules are applied and clearly rendered, a tallying client: * MUST indicate the state of consensus by displaying its value relative to the final percentage of the winning vote * MAY display the secondary tally method result, for statistical purposes, along with other associated poll metrics and comments -Strict adherence to these requirements should enable a standardized means of quantitatively assessing the distribution of opinion regarding a poll's content amongst poll participants, determining a winning outcome, and possibly acheiving consensus. However, until this protocol is further tested, refined, and proven robust, polls should probably not be considered authoritative nor binding. +Strict adherence to these requirements should enable a standardized means of quantitatively assessing the distribution of opinion regarding a poll's content amongst poll participants, determining a winning outcome, and possibly achieving consensus. However, until this protocol is further tested, refined, and proven robust, polls should probably not be considered authoritative nor binding. ## TODO