diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index c8851a8dd09..43ac9c5e43f 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -730,7 +730,7 @@ General Bitcoin Core
 
 - Make sure pull requests pass CI before merging.
 
-  - *Rationale*: Makes sure that they pass thorough testing, and that the tester will keep passing
+  - *Rationale*: Make sure that they pass thorough testing, and that the tester will keep passing
      on the master branch. Otherwise, all new pull requests will start failing the tests, resulting in
      confusion and mayhem.
 
@@ -1415,7 +1415,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
     convert a plaintext command line to JSON. If the types don't match, the method can be unusable
     from there.
 
-- A RPC method must either be a wallet method or a non-wallet method. Do not
+- An RPC method must either be a wallet method or a non-wallet method. Do not
   introduce new methods that differ in behavior based on the presence of a wallet.
 
   - *Rationale*: As well as complicating the implementation and interfering
@@ -1424,7 +1424,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
 
 - Try to make the RPC response a JSON object.
 
-  - *Rationale*: If a RPC response is not a JSON object, then it is harder to avoid API breakage if
+  - *Rationale*: If an RPC response is not a JSON object, then it is harder to avoid API breakage if
     new data in the response is needed.
 
 - Wallet RPCs call BlockUntilSyncedToCurrentChain to maintain consistency with
diff --git a/doc/files.md b/doc/files.md
index b738d6055a2..4036669c1af 100644
--- a/doc/files.md
+++ b/doc/files.md
@@ -83,7 +83,7 @@ Wallets are Berkeley DB (BDB) or SQLite databases.
 
 3. A wallet database path can be specified with the `-wallet` option.
 
-4. `wallet.dat` files must not be shared across different node instances, as that can result in key-reuse and double-spends due the lack of synchronization between instances.
+4. `wallet.dat` files must not be shared across different node instances, as that can result in key-reuse and double-spends due to the lack of synchronization between instances.
 
 5. Any copy or backup of the wallet should be done through a `backupwallet` call in order to update and lock the wallet, preventing any file corruption caused by updates during the copy.