penumbra: fix some typos (#5076)

Fix a couple typos in docs

crates/bin/pcli/src/command/validator.rs

@@ -225,7 +225,7 @@ impl ValidatorCmd {
                     );
                 } else {
                     println!(
-                        "Signed validator defintion #{} for {}\nTo upload the definition, use the below command with the exact same definition file:\n\n  $ pcli validator definition upload --file {:?} \\\n      --signature {}",
+                        "Signed validator definition #{} for {}\nTo upload the definition, use the below command with the exact same definition file:\n\n  $ pcli validator definition upload --file {:?} \\\n      --signature {}",
                         new_validator.sequence_number,
                         new_validator.identity_key,
                         input_file_name,

crates/bin/pcli/src/command/view/lps.rs

@@ -30,7 +30,7 @@ impl LiquidityPositionsCmd {
             })
             .await?
             .into_inner()
-            .map_err(|e| anyhow!("eror fetching liquidity positions: {}", e))
+            .map_err(|e| anyhow!("error fetching liquidity positions: {}", e))
             .and_then(|msg| async move {
                 msg.data
                     .ok_or_else(|| anyhow!("missing liquidity position in response"))

crates/util/cometindex/src/indexer/indexing_state.rs

@@ -232,7 +232,7 @@ ORDER BY
                         .into_iter()
                         .filter_map(|(k, v)| match v {
                             serde_json::Value::String(s) => Some((k, s)),
-                            // we never hit this becasue of how we constructed the query
+                            // we never hit this because of how we constructed the query
                             _ => None,
                         })
                         .map(Into::into)

crates/view/src/sync.rs

@@ -205,7 +205,7 @@ pub async fn scan_block(
         // End the block in the commitment tree
         state_commitment_tree
             .end_block()
-            .expect("ending the block must succed");
+            .expect("ending the block must succeed");
     }
 
     // If we've also reached the end of the epoch, end the epoch in the commitment tree

docs/protocol/src/SUMMARY.md

@@ -34,7 +34,7 @@
     - [Distributed Key Generation](./crypto/flow-encryption/dkg.md)
     - [Homomorphic Threshold Encryption](./crypto/flow-encryption/threshold-encryption.md)
     - [Flow Encryption and Consensus](./crypto/flow-encryption/flow-consensus.md)
-- [Groth 16 Setup Ceremony](./setup.md)
+[Groth 16 Setup Ceremony](./setup.md)
   - [Groth16 Recap](./setup/groth16_recap.md)
   - [Discrete Logarithm Proofs](./setup/dlog_proofs.md)
   - [Contributions](./setup/contributions.md)

docs/protocol/src/dex/swap.md

@@ -5,7 +5,7 @@ and AMM mechanism itself, and the batching procedure, which allows multiple
 users' swaps to be batched into a single trade executed against the trading
 function.  This section focuses on the batching procedure, leaving the mechanics of the trading function for later.
 
-Penumbra V1 provides swaps wherein the user publically burns their input assets, and privately mints the output assets. In a future upgrade, Penumbra will use sealed-bid batch swaps, protecting the privacy of the input assets to the trade, described further in the [section below](#sealed-bid-batch-swaps).
+Penumbra V1 provides swaps wherein the user publicly burns their input assets, and privately mints the output assets. In a future upgrade, Penumbra will use sealed-bid batch swaps, protecting the privacy of the input assets to the trade, described further in the [section below](#sealed-bid-batch-swaps).
 
 ### `Swap` actions