diff --git a/docs/pages/bug-bounty/bug-bounty-program.mdx b/docs/pages/bug-bounty/bug-bounty-program.mdx
index 2a8e393e..1ad9b8e6 100644
--- a/docs/pages/bug-bounty/bug-bounty-program.mdx
+++ b/docs/pages/bug-bounty/bug-bounty-program.mdx
@@ -55,7 +55,7 @@ The assets listed below are considered in-scope within our bug bounty program. I
 ### Program Rules
 
 - Only submit one vulnerability per report.
-- When duplicates occur, we will only accept the first report that was received, as long as it fulfils our submission criteria and can be fully reproduced.
+- When duplicates occur, we will only accept the first report that was received, as long as it fulfills our submission criteria and can be fully reproduced.
 - Social engineering targeted to Zora employees is prohibited.
 - Publishing sensitive information discovered during security testing is prohibited.
 - Vulnerabilities that Zora is aware of will not be rewarded.
@@ -64,4 +64,4 @@ The assets listed below are considered in-scope within our bug bounty program. I
 
 ### Disclosure Policy
 
-For responsible management of vulnerability disclosures, keep all discussions related to these vulnerabilities, including resolved ones, strictly within the program. Additionally, do not disclose them externally within 90 days of remediation or without Zora's explicit consent. Failure to comply with the Disclosure Policy may result in the loss of any potential reward. Your adherence to this policy greatly enhances the program's safety and integrity.
\ No newline at end of file
+For responsible management of vulnerability disclosures, keep all discussions related to these vulnerabilities, including resolved ones, strictly within the program. Additionally, do not disclose them externally within 90 days of remediation or without Zora's explicit consent. Failure to comply with the Disclosure Policy may result in the loss of any potential reward. Your adherence to this policy greatly enhances the program's safety and integrity.
diff --git a/docs/pages/protocol-sdk/creator/premint.mdx b/docs/pages/protocol-sdk/creator/premint.mdx
index 2f37b0cb..acbd48dc 100644
--- a/docs/pages/protocol-sdk/creator/premint.mdx
+++ b/docs/pages/protocol-sdk/creator/premint.mdx
@@ -5,7 +5,7 @@
 The Zora Protocol allows creators to create 1155 contracts and tokens without needing to pay any gas or have eth in their wallet. This
 is done by creating what's called a `Premint` - a signed intent to create and setup an 1155 contract and/or token.
 It is then uploading it to an API, where it can be retrieved later to bring onchain and mint by an account willing to pay the gas to do so.  This can either be the first collector, or the
-the original creator of the Premint. The account that brings the Premint onchain will earn the first minter reward.
+original creator of the Premint. The account that brings the Premint onchain will earn the first minter reward.
 
 In order for the Premint to be discoverable in the Zora network, it must be signed by the creator's wallet and uploaded to the Zora Premint API.
 Before the Premint is brought onchain, the creator of the Premint can sign a message to update or delete it.
@@ -61,7 +61,7 @@ One of the items returned from `create` is `signAndSubmit` which must be called
 
 :::
 
-### Signing and Submitting Premint a Premint using Wagmi
+### Signing and Submitting Premint using Wagmi
 
 Sometimes it may be desirable to sign a premint with another library, and not using the sdk's `signAndSubmit` method.
 For this case, the `createPremint`, `updatePremint`, and `deletePremint` functions return a `typedDataDefinition` which is the typed data definition for the premint and must be signed.
@@ -132,7 +132,7 @@ This signature and deleted premint is then submitted to the Zora Premint API and
 :::
 
 
-### Earning Create Referral Referral Rewards
+### Earning Create Referral Rewards
 
 To earn a create referral reward, pass in the `createReferral` argument when creating a Premint: