diff --git a/docs/padr/PADR-001_Dutch_Auctions.md b/docs/padr/PADR-001_Dutch_Auctions.md
index 68cf55b1b5..b3beb6af73 100644
--- a/docs/padr/PADR-001_Dutch_Auctions.md
+++ b/docs/padr/PADR-001_Dutch_Auctions.md
@@ -197,7 +197,7 @@ message ActionDutchAuctionScheduleView {
 #### `ActionDutchAuctionEnd`
 
 ```proto
-// Ends a Dutch auction using protocol-controlled liquiidty.
+// Ends a Dutch auction using protocol-controlled liquidity.
 message ActionDutchAuctionEnd {
     // The auction to end.
     AuctionId auction_id = 1;
diff --git a/docs/protocol/src/crypto/flow/ideal.md b/docs/protocol/src/crypto/flow/ideal.md
index 07221d6fa7..cc690dabf8 100644
--- a/docs/protocol/src/crypto/flow/ideal.md
+++ b/docs/protocol/src/crypto/flow/ideal.md
@@ -117,7 +117,7 @@ value integrity proceeds in a number of steps:
 1. Application-specific logic proves that each user's contribution value $v_i$ conserves value according to the application rules, by proving statements about the commitment $C_{i}$ to $v_{i}$.
 2. The encryption proof $\pi_{\operatorname{Enc}}$ extends integrity from $C_{i}$ to $E_{i}$.
 3. Integrity extends to the aggregation $E = \sum_i E_i$ automatically, since the aggregation can be publicly recomputed by anyone with access to the ledger.
-4. The decryption share integrity proofs extend integrity from $E$ to $w$.  This requires that, if $w$ is the result of decryption using valid decryption shares, than $E = \operatorname{Enc}(w)$.
+4. The decryption share integrity proofs extend integrity from $E$ to $w$.  This requires that, if $w$ is the result of decryption using valid decryption shares, then $E = \operatorname{Enc}(w)$.
 5. Publication of (any) decryption transcript allows any participant to check the end-to-end property that $w = \sum_i v_i$ for (application-)valid $v_i$.
 
 ###### Decryption Robustness
diff --git a/docs/protocol/src/crypto/fmd/system_mapping.md b/docs/protocol/src/crypto/fmd/system_mapping.md
index f9a4983554..6660489c0c 100644
--- a/docs/protocol/src/crypto/fmd/system_mapping.md
+++ b/docs/protocol/src/crypto/fmd/system_mapping.md
@@ -1,6 +1,6 @@
 # S-FMD in Penumbra
 
-In the secions that follow we describe how S-FMD clue keys, detection keys, and
+In the sections that follow we describe how S-FMD clue keys, detection keys, and
 clues are integrated into the Penumbra system.
 
 ## Clue Keys
diff --git a/docs/protocol/src/stake/action/undelegate_claim.md b/docs/protocol/src/stake/action/undelegate_claim.md
index 177bc1b81a..927b975051 100644
--- a/docs/protocol/src/stake/action/undelegate_claim.md
+++ b/docs/protocol/src/stake/action/undelegate_claim.md
@@ -15,7 +15,7 @@ The body of a `UndelegateClaim` has four parts:
 
 #### Local Invariants
 
-1. You cannot claim undelegations that have not finishing unbonding.
+1. You cannot claim undelegations that have not finished unbonding.
 
 2. Slashing penalties must be applied when unbonding.