diff --git a/docs/build/get-started/developer-quickstart.md b/docs/build/get-started/developer-quickstart.md
index 0827f3615d..9bb6102567 100644
--- a/docs/build/get-started/developer-quickstart.md
+++ b/docs/build/get-started/developer-quickstart.md
@@ -212,7 +212,7 @@ You'll notice in the `CONTRACT_OWNER` constant that `tx-sender` is set in place
 
 We'll then need to define some data storage:
 
-* A map to store key-value pairs of the message id and it's related metadata
+* A map to store key-value pairs of the message id and its related metadata
 * A data variable to count the total number of messages added
 
 <pre class="language-clarity" data-title="message-board.clar"><code class="lang-clarity">;; Define a map to store messages
diff --git a/docs/build/more-guides/verify-bitcoin-transactions-clarity/README.md b/docs/build/more-guides/verify-bitcoin-transactions-clarity/README.md
index 9994640475..9d4d1af906 100644
--- a/docs/build/more-guides/verify-bitcoin-transactions-clarity/README.md
+++ b/docs/build/more-guides/verify-bitcoin-transactions-clarity/README.md
@@ -369,7 +369,7 @@ The current version of the `clarity-bitcoin-lib` is version 7. Click [here](http
 ```
 {% endcode %}
 
-So after you've fetched the bitcoin tx metadata and have removed the witness data from the original transaction hex, let's go ahead and prepare the metadata into it's Clarity parameter values.
+So after you've fetched the bitcoin tx metadata and have removed the witness data from the original transaction hex, let's go ahead and prepare the metadata into its Clarity parameter values.
 
 {% code expandable="true" %}
 ```typescript
diff --git a/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md b/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md
index 936ed7e905..80cc9c3fe2 100644
--- a/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md
+++ b/docs/build/more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md
@@ -2,7 +2,7 @@
 
 For usage with the `clarity-bitcoin-lib` contract or if you just want to learn how to invoke a bitcoin transaction from your wallet on the front end, check out this guide.
 
-Using Stacks Connect and with a Stacks-supported wallet, you can initiate a simple Bitcoin transaction from a frontend app in a few lines of code. With this Bitcoin transaction, you can then use to verify it's inclusion in a Bitcoin block through Clarity.
+Using Stacks Connect and with a Stacks-supported wallet, you can initiate a simple Bitcoin transaction from a frontend app in a few lines of code. With this Bitcoin transaction, you can then use it to verify its inclusion in a Bitcoin block through Clarity.
 
 {% hint style="info" %}
 Check out the [Stacks Connect](../../stacks-connect/connect-wallet.md) guides for more info on setup and wallet connection.
diff --git a/docs/learn/transactions/post-conditions.md b/docs/learn/transactions/post-conditions.md
index 1d4ffe0e64..0df1309ed0 100644
--- a/docs/learn/transactions/post-conditions.md
+++ b/docs/learn/transactions/post-conditions.md
@@ -32,6 +32,6 @@ Here's what that looks like:
 
 <figure><img src="../.gitbook/assets/image (43).png" alt=""><figcaption></figcaption></figure>
 
-In this example, if the smart contract does not transfer one fabulous-frog NFT and and take 50 STX from the user, the transaction will abort.
+In this example, if the smart contract does not transfer one fabulous-frog NFT and take 50 STX from the user, the transaction will abort.
 
 You can learn more about how post conditions work in [SIP-005](https://github.com/stacksgov/sips/blob/main/sips/sip-005/sip-005-blocks-and-transactions.md#transaction-post-conditions) and how to utilize them in your applications in Hiro's excellent [post conditions tutorial](https://docs.hiro.so/stacks/stacks.js/guides/post-conditions).