From 650af06a191b59b2b4739ac9a0400ef93ba04722 Mon Sep 17 00:00:00 2001
From: Noisy <125606576+donatik27@users.noreply.github.com>
Date: Tue, 12 Nov 2024 11:07:15 +0100
Subject: [PATCH 1/4] Update index.mdx
---
docs/pages/index.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx
index 8e1ce0b65..ef8759e70 100644
--- a/docs/pages/index.mdx
+++ b/docs/pages/index.mdx
@@ -10,7 +10,7 @@ import { HomePageLogo } from "../components/HomePageLogo";
Explore our guides and examples to integrate Zora
-Build your project using the Zora Protocol and plug into over $25m of rewards out of the box. We’ve created a series of tools that makes it easy to get started building on Zora.
+Build your project using the Zora Protocol and plug into over $25m of rewards out of the box. We’ve created a series of tools that make it easy to get started building on Zora.
From c5e95fdebf00edebba487e55bb085aa6c0ebb1e4 Mon Sep 17 00:00:00 2001
From: Noisy <125606576+donatik27@users.noreply.github.com>
Date: Tue, 12 Nov 2024 11:10:33 +0100
Subject: [PATCH 2/4] Update README.md
---
packages/sparks/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/packages/sparks/README.md b/packages/sparks/README.md
index cfa507090..8d7c74fa6 100644
--- a/packages/sparks/README.md
+++ b/packages/sparks/README.md
@@ -26,7 +26,7 @@ set of recipients in the form of fees and rewards, with the percentage split
configured in the creator contract. When a SPARK is redeemed, the underlying
value is distributed to a desired recipient, and the SPARK is burned.
-The `ZoraSparksManager` is an administrated and upgradeble that contract controls which SPARK token id can be minted for each currency type,
+The `ZoraSparksManager` is an administrated and upgradeable that contract controls which SPARK token id can be minted for each currency type,
thus defining the current price for collecting a SPARK in that currency type.
While it controls the logic around which SPARKs can be minted, once a SPARK is minted, the corresponding value is deposited into the
immutable `ZoraSparks1155` contract; only the owner of the SPARKs can access the underlying deposited funds by redeming the SPARKs or choose to do with their SPARKs, and since that contract is immutable these rules could never change.
From 2f949aa64edc30e0efcd927ae57e2b30498cf0de Mon Sep 17 00:00:00 2001
From: Noisy <125606576+donatik27@users.noreply.github.com>
Date: Tue, 12 Nov 2024 12:04:00 +0100
Subject: [PATCH 3/4] Update README.md
---
packages/1155-deployments/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/packages/1155-deployments/README.md b/packages/1155-deployments/README.md
index 4fd19240e..b7c3d96a2 100644
--- a/packages/1155-deployments/README.md
+++ b/packages/1155-deployments/README.md
@@ -4,5 +4,5 @@ Contains deployment scripts, deployed addresses and versions for the Zora 1155 C
## Package contents
-- [Deployment scripts](./script/) for deployment Zora Protocol Contracts
+- [Deployment scripts](./script/) for deploying Zora Protocol Contracts
- [Deployed addresses](./addresses/) containing deployed addresses and contract versions by chain.
From 6f7ac99df846650721f2cea557eb5633a2cfa2d8 Mon Sep 17 00:00:00 2001
From: Noisy <125606576+donatik27@users.noreply.github.com>
Date: Tue, 12 Nov 2024 12:07:22 +0100
Subject: [PATCH 4/4] Update README.md
---
packages/protocol-rewards/README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/packages/protocol-rewards/README.md b/packages/protocol-rewards/README.md
index fccf47e53..69a06f9c4 100644
--- a/packages/protocol-rewards/README.md
+++ b/packages/protocol-rewards/README.md
@@ -10,7 +10,7 @@ Documentation is available at [docs.zora.co](https://docs.zora.co).
## Implementation Caveats
-The `ProtocolRewards` contract has a implementation caveat. If you send any value to a zero (`address(0)`) address in `depositRewards`, that value is implicitly burnt by being locked in the contract at the zero address. The function will not revert or redirect those funds as currently designed. We may re-visit this design in the future but for the release of v1.1 this is the current and expected behavior.
+The `ProtocolRewards` contract has an implementation caveat. If you send any value to a zero (`address(0)`) address in `depositRewards`, that value is implicitly burned by being locked in the contract at the zero address. The function will not revert or redirect those funds as currently designed. We may re-visit this design in the future but for the release of v1.1 this is the current and expected behavior.
## Deployed Addresses