diff --git a/docs/content/concepts/cryptography/zklogin.mdx b/docs/content/concepts/cryptography/zklogin.mdx index 8b8f65b32bca7..6de1622836f58 100644 --- a/docs/content/concepts/cryptography/zklogin.mdx +++ b/docs/content/concepts/cryptography/zklogin.mdx @@ -527,7 +527,7 @@ You might want to cache the ephemeral key pair along with the ZKP for future use However, the ephemeral key pair needs to be treated as a secret akin to a key pair in a traditional wallet. This is because if both the ephemeral private key and ZK proof are revealed to an attacker, then they can typically sign any transaction on behalf of the user (using the same process described previously). -Consequently, you should not store them persistently in an unsecure storage location, on any platform. For example, on browsers, use session storage instead of local storage to store the ephemeral key pair and the ZK proof. +Consequently, you should choose the storage of the ephemeral key pair and the ZK proof carefully. For example, a web browser provides both session and local storage. Data in local storage persists until you explicitly clear your browser cache (remains across browser sessions), whereas session storage persists only until you close the tab or bowser. Using local storage for this data is preferable to safeguard against the loss of funds should the session end unexpectedly. ## How zkLogin Works {#how-zklogin-works} diff --git a/docs/content/concepts/sui-architecture/epochs.mdx b/docs/content/concepts/sui-architecture/epochs.mdx index 7c406f8359bf8..379807da2fc96 100644 --- a/docs/content/concepts/sui-architecture/epochs.mdx +++ b/docs/content/concepts/sui-architecture/epochs.mdx @@ -23,6 +23,6 @@ Reconfiguration is a critical process occurring at the end of each epoch. It inv - Storage fees are allocated to a storage fund, playing a vital role in the Sui tokenomics, as explaiend in [Tokenomics](../tokenomics.mdx). 1. **Validator set change** - Any pending staking and unstaking requests during the epoch are finalized and reflected in validators stake distribution. - - Any pending validator change requests are also processed, including adding new validators and removing exixting validators. This is the sole opportunity for altering the validator set and stake distribution. + - Any pending validator change requests are also processed, including adding new validators and removing existing validators. This is the sole opportunity for altering the validator set and stake distribution. 1. **Protocol upgrade** - If agreed upon by 2f+1 validators, the network might upgrade to a new protocol version, encompassing new features, bug fixes, and updates to Move framework libraries. diff --git a/docs/content/standards/deepbook/design.mdx b/docs/content/standards/deepbook/design.mdx index 25811758ae227..f087c73f3012c 100644 --- a/docs/content/standards/deepbook/design.mdx +++ b/docs/content/standards/deepbook/design.mdx @@ -8,7 +8,7 @@ slug: /deepbook-design At the center of DeepBook is a hyper-efficient per-current pair shared-object Pool structure. This architecture maximally utilizes Sui's Narwhal and Bullshark engine to minimize contention and achieve high throughput. -For each base and quote asset trading pair, a globally shared Pool is created to 1) bookkeep open orders on the order book and 2) handle placement, cancelation, and settlement of orders. Under this architecture, transactions involving different trading pairs can be easily parallelized to maximize throughput. +For each base and quote asset trading pair, a globally shared Pool is created to 1) bookkeep open orders on the order book and 2) handle placement, cancellation, and settlement of orders. Under this architecture, transactions involving different trading pairs can be easily parallelized to maximize throughput. ```move struct Pool has key { diff --git a/docs/content/standards/deepbook/pools.mdx b/docs/content/standards/deepbook/pools.mdx index 52a3a0a0b7331..2b5ee40c36bba 100644 --- a/docs/content/standards/deepbook/pools.mdx +++ b/docs/content/standards/deepbook/pools.mdx @@ -5,7 +5,7 @@ slug: /deepbook-pools At the center of DeepBook is a hyper-efficient per-current pair shared-object Pool structure. This architecture maximally utilizes Sui's Narwhal and Bullshark engine to minimize contention and achieve high throughput. -For each base and quote asset trading pair, a globally shared Pool is created to 1) bookkeep open orders on the order book and 2) handle placement, cancelation, and settlement of orders. Under this architecture, transactions involving different trading pairs can be easily parallelized to maximize throughput. +For each base and quote asset trading pair, a globally shared Pool is created to 1) bookkeep open orders on the order book and 2) handle placement, cancellation, and settlement of orders. Under this architecture, transactions involving different trading pairs can be easily parallelized to maximize throughput. ```move struct Pool has key { diff --git a/sui_programmability/examples/crypto/sources/ec_ops.move b/sui_programmability/examples/crypto/sources/ec_ops.move index 61c5909737a36..bc8c0b18706f3 100644 --- a/sui_programmability/examples/crypto/sources/ec_ops.move +++ b/sui_programmability/examples/crypto/sources/ec_ops.move @@ -1,7 +1,7 @@ // Copyright (c) Mysten Labs, Inc. // SPDX-License-Identifier: Apache-2.0 -// Examples of cryptographic primitives that can be implemented in Move using group opeartions. +// Examples of cryptographic primitives that can be implemented in Move using group operations. // // Functions with the prefix "insecure" are here for testing, but should be called off-chain (probably implemented in // other languages) to avoid leaking secrets. @@ -357,7 +357,7 @@ module crypto::ec_ops { vector::reverse(&mut round_bytes); let target = sha2_256(round_bytes); - // Retreived with 'curl https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/public/1234'. + // Retrieved with 'curl https://api.drand.sh/52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971/public/1234'. let sig_bytes = x"a81d4aad15461a0a02b43da857be1d782a2232a3c7bb370a2763e95ce1f2628460b24de2cee7453cd12e43c197ea2f23"; let target_key = bls12381::g1_from_bytes(&sig_bytes); assert!(bls12381::bls12381_min_sig_verify(&sig_bytes, &pk_bytes, &target), 0); diff --git a/sui_programmability/examples/games/sources/drand_based_lottery.move b/sui_programmability/examples/games/sources/drand_based_lottery.move index d301a104bb8af..5224f5e67e4ed 100644 --- a/sui_programmability/examples/games/sources/drand_based_lottery.move +++ b/sui_programmability/examples/games/sources/drand_based_lottery.move @@ -34,7 +34,7 @@ /// As long as someone is closing the game in time (or at least before round N) we have the guarantee that the winner is /// selected using unpredictable and unbiasable randomness. Otherwise, someone could wait until the randomness of round N /// is public, see if it could win the game and if so, join the game and drive it to completion. Therefore, honest users -/// are encourged to close the game in time. +/// are encouraged to close the game in time. /// /// All the external inputs needed for the following APIs can be retrieved from one of drand's public APIs, e.g. using /// the above curl commands.