diff --git a/.github/ISSUE_TEMPLATE/usability_testing_plan.md b/.github/ISSUE_TEMPLATE/usability_testing_plan.md
index c93f413b605..570f1393d1f 100644
--- a/.github/ISSUE_TEMPLATE/usability_testing_plan.md
+++ b/.github/ISSUE_TEMPLATE/usability_testing_plan.md
@@ -31,7 +31,7 @@ assignees: ''
 
 ### Method
 
-<!-- Explain whether the tests will be co-located or reomte, moderated or unmoderated, and who will attend the sessions (e.g a moderator and a note-taker) -->
+<!-- Explain whether the tests will be co-located or remote, moderated or unmoderated, and who will attend the sessions (e.g a moderator and a note-taker) -->
 
 ### Test environment, equipment and logistics
 
@@ -56,7 +56,7 @@ assignees: ''
 
 ## Session Outline and timing
 
-<!-- The following sections provide some space to plan out the script and and tasks for your participants -->
+<!-- The following sections provide some space to plan out the script and tasks for your participants -->
 
 ### 1.Introduction to the session (5\')
 
diff --git a/book/src/dev/rfcs/0000-template.md b/book/src/dev/rfcs/0000-template.md
index 72bcd9affcf..cdf4022bc24 100644
--- a/book/src/dev/rfcs/0000-template.md
+++ b/book/src/dev/rfcs/0000-template.md
@@ -122,7 +122,7 @@ Think about what the natural extension and evolution of your proposal would
 be and how it would affect Zebra and Zcash as a whole. Try to use this
 section as a tool to more fully consider all possible
 interactions with the project and cryptocurrency ecosystem in your proposal.
-Also consider how the this all fits into the roadmap for the project
+Also consider how this all fits into the roadmap for the project
 and of the relevant sub-team.
 
 This is also a good place to "dump ideas", if they are out of scope for the
diff --git a/book/src/dev/rfcs/0009-zebra-client.md b/book/src/dev/rfcs/0009-zebra-client.md
index 3aa153daea6..771aa7d3a2d 100644
--- a/book/src/dev/rfcs/0009-zebra-client.md
+++ b/book/src/dev/rfcs/0009-zebra-client.md
@@ -341,7 +341,7 @@ endpoint
 <!-- be and how it would affect Zebra and Zcash as a whole. Try to use this -->
 <!-- section as a tool to more fully consider all possible -->
 <!-- interactions with the project and cryptocurrency ecosystem in your proposal. -->
-<!-- Also consider how the this all fits into the roadmap for the project -->
+<!-- Also consider how this all fits into the roadmap for the project -->
 <!-- and of the relevant sub-team. -->
 
 <!-- This is also a good place to "dump ideas", if they are out of scope for the -->
diff --git a/book/src/dev/rfcs/drafts/xxxx-basic-integration-testing.md b/book/src/dev/rfcs/drafts/xxxx-basic-integration-testing.md
index 7f9c0594e3c..dd77cc14cdc 100644
--- a/book/src/dev/rfcs/drafts/xxxx-basic-integration-testing.md
+++ b/book/src/dev/rfcs/drafts/xxxx-basic-integration-testing.md
@@ -124,7 +124,7 @@ Think about what the natural extension and evolution of your proposal would
 be and how it would affect Zebra and Zcash as a whole. Try to use this
 section as a tool to more fully consider all possible
 interactions with the project and cryptocurrency ecosystem in your proposal.
-Also consider how the this all fits into the roadmap for the project
+Also consider how this all fits into the roadmap for the project
 and of the relevant sub-team.
 
 This is also a good place to "dump ideas", if they are out of scope for the
diff --git a/zebra-network/src/address_book.rs b/zebra-network/src/address_book.rs
index 9ecf5aa24b0..aee8629f3bc 100644
--- a/zebra-network/src/address_book.rs
+++ b/zebra-network/src/address_book.rs
@@ -265,7 +265,7 @@ impl AddressBook {
     /// Get the active addresses in `self` in random order with sanitized timestamps,
     /// including our local listener address.
     ///
-    /// Limited to a the number of peer addresses Zebra should give out per `GetAddr` request.
+    /// Limited to the number of peer addresses Zebra should give out per `GetAddr` request.
     pub fn fresh_get_addr_response(&self) -> Vec<MetaAddr> {
         let now = Utc::now();
         let mut peers = self.sanitized(now);