diff --git a/contracts/ibc-reflect/README.md b/contracts/ibc-reflect/README.md
index 0a9aad788..459e89483 100644
--- a/contracts/ibc-reflect/README.md
+++ b/contracts/ibc-reflect/README.md
@@ -2,7 +2,7 @@
 
 This is a simple contract to demonstrate using contracts using IBC messages. The
 first case we build is to simulate the `reflect` contract on another chain. That
-is, you can send a message over IBC to the reflect contract and it will
+is, you can send a message over IBC to the `reflect` contract, and it will
 "reflect" that message on the remote chain as if it sent it.
 
 This is inspired by
@@ -25,7 +25,7 @@ point), it will create a new `reflect` contract instance. The reflect `code_id`
 must be set when initializing the factory. This `reflect` contract address will
 be saved and connected to the channel.
 
-Once the channel is fully established and the reflect contract instantiated it
+Once the channel is fully established and the `reflect` contract instantiated it
 will expect a `RunTx` message, which contains `Vec<CosmosMsg>`. When this
 message is received, it will execute it on the `reflect` contract, performing
 the requested action on behalf of the remote user.
diff --git a/contracts/reflect/README.md b/contracts/reflect/README.md
index 7930b2656..49897f012 100644
--- a/contracts/reflect/README.md
+++ b/contracts/reflect/README.md
@@ -29,7 +29,7 @@ cargo generate --git https://github.com/confio/cosmwasm-template.git --name YOUR
 ```
 
 You will now have a new folder called `YOUR_NAME_HERE` (I hope you changed that
-to something else) containing a simple working contract and build system that
+to something else) containing a simple working contract and a build system that
 you can customize.
 
 ## Create a Repo
@@ -49,7 +49,7 @@ git push -u origin main
 
 ## CI Support
 
-We have templates for both github actions and Circle CI in the generated
+We have templates for both GitHub actions and Circle CI in the generated
 project, so you can get up and running with CI right away. One note is that the
 CI runs all `cargo` commands with `--locked` to ensure it uses the exact same
 versions as you have locally. This also means you must have an up-to-date