From 5c2f721ab51227a735edcfad7ecf3cbc3b179f7a Mon Sep 17 00:00:00 2001 From: taozui472 Date: Wed, 25 Dec 2024 11:30:59 +0800 Subject: [PATCH] Fix quotation mark --- .../src/component/position_manager/base_liquidity_index.rs | 4 ++-- crates/custody/src/client.rs | 4 ++-- docs/protocol/src/sct/tct.md | 2 +- testnets/cometbft_config_template.toml | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/crates/core/component/dex/src/component/position_manager/base_liquidity_index.rs b/crates/core/component/dex/src/component/position_manager/base_liquidity_index.rs index 5e8b8ffaa3..73ce4565d1 100644 --- a/crates/core/component/dex/src/component/position_manager/base_liquidity_index.rs +++ b/crates/core/component/dex/src/component/position_manager/base_liquidity_index.rs @@ -33,8 +33,8 @@ pub(crate) trait AssetByLiquidityIndex: StateWrite { /// There are then two possible amounts to consider for an asset B: amount of A that /// can be sold for B and amount of A that can be bought with B /// - /// (1), amount that can be sold (“outbound”) is the wrong thing to use - /// (2), amount that can be bought, is intuitively the “opposite” of what we want, + /// (1), amount that can be sold ("outbound") is the wrong thing to use + /// (2), amount that can be bought, is intuitively the "opposite" of what we want, /// since it’s the reverse direction, but is actually the right thing to use as /// a rough proxy for liquidity /// diff --git a/crates/custody/src/client.rs b/crates/custody/src/client.rs index 10b014a9ef..30d9058e6b 100644 --- a/crates/custody/src/client.rs +++ b/crates/custody/src/client.rs @@ -14,8 +14,8 @@ use crate::AuthorizeRequest; /// a transaction they’ve constructed. /// /// Modeling transaction authorization as an asynchronous RPC call encourages -/// software to be written in a way that has a compatible data flow with a “soft -/// HSM”, threshold signing, a hardware wallet, etc. +/// software to be written in a way that has a compatible data flow with a "soft +/// HSM", threshold signing, a hardware wallet, etc. /// /// The custody protocol does not trust the client to authorize spends, so /// custody requests must contain sufficient information for the custodian to diff --git a/docs/protocol/src/sct/tct.md b/docs/protocol/src/sct/tct.md index 647e476966..3a0a81df84 100644 --- a/docs/protocol/src/sct/tct.md +++ b/docs/protocol/src/sct/tct.md @@ -15,7 +15,7 @@ means too many expensive hash operations, whereas an octal tree means too large proofs. * *Sparse:* A client’s version of the tree need only represent the state -commitments pertinent to that client’s state, with all other “forgotten” +commitments pertinent to that client’s state, with all other "forgotten" commitments and internal hashes related to them pruned to a single summary hash. * *Semi-Lazy:* The internal hashes along the frontier of the tree are only diff --git a/testnets/cometbft_config_template.toml b/testnets/cometbft_config_template.toml index 65f556a350..6ca2cd61d1 100644 --- a/testnets/cometbft_config_template.toml +++ b/testnets/cometbft_config_template.toml @@ -410,11 +410,11 @@ wal_file = "data/cs.wal/wal" timeout_propose = "3s" # How much timeout_propose increases with each round timeout_propose_delta = "500ms" -# How long we wait after receiving +2/3 prevotes for “anything” (ie. not a single block or nil) +# How long we wait after receiving +2/3 prevotes for "anything" (ie. not a single block or nil) timeout_prevote = "1s" # How much the timeout_prevote increases with each round timeout_prevote_delta = "500ms" -# How long we wait after receiving +2/3 precommits for “anything” (ie. not a single block or nil) +# How long we wait after receiving +2/3 precommits for "anything" (ie. not a single block or nil) timeout_precommit = "1s" # How much the timeout_precommit increases with each round timeout_precommit_delta = "500ms"