diff --git a/art-blocks-engine-onboarding/art-blocks-engine-101/README.md b/art-blocks-engine-onboarding/art-blocks-engine-101/README.md
index 4e15e779..bfb00ad2 100644
--- a/art-blocks-engine-onboarding/art-blocks-engine-101/README.md
+++ b/art-blocks-engine-onboarding/art-blocks-engine-101/README.md
@@ -57,7 +57,7 @@ A high-level process map for Art Blocks Engine onboarding.
     // Check that the user has the required amount of ERC-20
     const balance = await erc20.balanceOf(userAddress)
     if (balance.lt(pricePerTokenInWei)) {
-      // Show insufficent funds error
+      // Show insufficient funds error
       return
     }
     
diff --git a/core-contract-v3/overview.md b/core-contract-v3/overview.md
index 1475f519..c5302ddf 100644
--- a/core-contract-v3/overview.md
+++ b/core-contract-v3/overview.md
@@ -15,6 +15,6 @@ The V3 Core Contract comes in two variants:
 
 Both of these implementations are available for use by Art Blocks Studio artists and Engine partners.
 
-The V3 Engine contract offers the same functionality as the original Art Blocks contract, with an artist's script being fully defined only on the blockchain. The V3 Engine Flex extends the ways artists may store additional metadata, with options of using re-usable on-chain assets, using decentralized storage networks such as IPFS or Arweave, or pointing to assets defined on the Art Blocks Dependency Registry (some of which are fully defined on-chain, some of which are defined on preferred CDN services).
+The V3 Engine contract offers the same functionality as the original Art Blocks contract, with an artist's script being fully defined only on the blockchain. The V3 Engine Flex extends the ways artists may store additional metadata, with options of using reusable on-chain assets, using decentralized storage networks such as IPFS or Arweave, or pointing to assets defined on the Art Blocks Dependency Registry (some of which are fully defined on-chain, some of which are defined on preferred CDN services).
 
 For more discussion about different NFT metadata storage mechanisms, see the [NFT Metadata Storage at Art Blocks](/art-blocks-101/on-chain.md) page.
diff --git a/minter-suite/minting-philosophy.md b/minter-suite/minting-philosophy.md
index 233cf713..f370b9f7 100644
--- a/minter-suite/minting-philosophy.md
+++ b/minter-suite/minting-philosophy.md
@@ -27,7 +27,7 @@ The following principles, when used together, are important ideals that we belie
 
 #### 1. Transparency
 
-We believe that minting should be transparent and easy to understand for collectors. Verified source code is provided for all minter smart contracts, and we develop our minters publically in our open source [GitHub repository](https://github.com/ArtBlocks/artblocks-contracts).
+We believe that minting should be transparent and easy to understand for collectors. Verified source code is provided for all minter smart contracts, and we develop our minters publicly in our open source [GitHub repository](https://github.com/ArtBlocks/artblocks-contracts).
 
 #### 2. Decentralized & Trust-Minimized
 
diff --git a/public-api-docs/index.html b/public-api-docs/index.html
index 81c1cc45..c8161c1f 100644
--- a/public-api-docs/index.html
+++ b/public-api-docs/index.html
@@ -29123,7 +29123,7 @@ <h2 class="definition-heading">receipt_metadata</h2>
               <div class="doc-copy">
                 <div class="definition-description doc-copy-section">
                   <h5>Description</h5>
-                  <p>indexed data from subgraph Receipt entity, used by settlment minters</p>
+                  <p>indexed data from subgraph Receipt entity, used by settlement minters</p>
                 </div>
                 <div class="definition-properties doc-copy-section">
                   <h5>Fields</h5>