Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos and grammatical errors across multiple documentation files #470

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

Dimitrolito
Copy link

This pull request fixes several typographical and grammatical issues across various documentation files in the project. Changes include the correction of articles ("a" vs. "an") and clarification of phrases for improved readability and accuracy.

Motivation and Context:

These changes were made to address typos and ensure consistency in grammar, which helps improve the clarity and professionalism of the documentation. Some issues included the incorrect use of articles and repetitive phrases, which could confuse readers.

Changes:

  • Fixed the use of "a" vs. "an" where appropriate (e.g., "a Uniswap V3 Pool" → "an Uniswap V3 Pool").
  • Removed repetitive phrases (e.g., "when users when users" → "when users").
  • Corrected other minor typographical errors for clarity.

Impact:

These changes are purely grammatical and will not affect the functionality of the codebase. They help improve the documentation and ensure consistency throughout.

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I added a changeset to account for this change.

Reviewer Checklist:

  • My review includes a synopsis of the changes and potential issues.
  • The code style is enforced.
  • There are no risky or concerning changes in the PR.

@Dimitrolito
Copy link
Author

Hi @oveddan ,

Just a friendly reminder about pull request #470, which fixes several typographical and grammatical issues across various documentation files in the project. The PR is ready for review, and I’d appreciate it if you could take a look when you have a chance.

Thank you!

Copy link
Collaborator

@oveddan oveddan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for catching and fixing all these. please undo the changes where instructed and then LGTM

docs/pages/bug-bounty/bug-bounty-program.mdx Outdated Show resolved Hide resolved
@@ -53,7 +53,7 @@ _Please note: All bounty rewards will be denoted as USD and will be paid out as
### 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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good fix

@@ -62,7 +62,7 @@

### Minor Changes

- [d460e79c](https://github.com/ourzora/zora-protocol/commit/d460e79c): - Introduced a `reduceSupply` function allowing an approved minter or admin to reduce the supply for a given token id. New supply must be less than the current maxSupply, and greater than or equal to the total minted so far.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good fix thank you

@@ -251,7 +251,7 @@

#### New ability to do premints against existing contracts

Executing premint against contracts not created via premint can be done with by passing a `premintCollection` argument to the new `premint` function:
Executing premint against contracts not created via premint can be done by passing a `premintCollection` argument to the new `premint` function:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for catching this

@@ -339,7 +339,7 @@
- remove `ZoraCreator1155Impl.adminMintBatch` to save contract size
- 50a4e09: - To support the MINTs contract passing the first minter as an argument to `premintV2WithSignerContract` - we add the field `firstMinter` to `premintV2WithSignerContract`, and then in the 1155 check that the firstMinter argument is not address(0) since it now can be passed in manually.

### ZoraCreator1155Impl rewards splits are percentage based instead of a fixed value.
### ZoraCreator1155Impl rewards splits are percentage-based instead of a fixed value.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch

@@ -128,7 +128,7 @@ with the 1155 contract address and the token creation parameters.

## Setting a price per token

A price per token can be optionally set to earn eth additional on the primary sale when each token is minted, by setting `token.salesConfig.pricePerToken`.
A price per token can be optionally set to earn additional ETH on the primary sale when each token is minted, by setting `token.salesConfig.pricePerToken`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -1,6 +1,6 @@
# `getTokensOfContract`

**Both onchain** and **premint (gaslessly created)** tokens of a Zora 1155 contract can be retrieved using the the Collector Client function
**Both onchain** and **premint (gaslessly created)** tokens of a Zora 1155 contract can be retrieved using the Collector Client function
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -139,7 +138,7 @@ The logic for launching the secondary market is designed with a few requirements

- The secondary market starting price should be 0.000111 eth per token
- There should be an equal amount of ERC20 to ERC1155 tokens minted/total supply
- Each owned ERC1155 should be backed and unwrappable by 1 ERC20, and visa versa.
- Each owned ERC1155 should be backed and unwrappable by 1 ERC20, and vice versa.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -26,8 +26,7 @@ As soon as the secondary market is launched the mint fees earned by the market w
The ZoraTimedSaleStrategy contract is used to create a timed sale for a Zora 1155 token. When it is configured for an 1155 contract and token via the `setSale` function,
specifying the `saleStart` and `saleEnd` of the sale, it creates a new ERC20z token and corresponding Uniswap V3 pool for a WETH pair with the ERC20z with a 1% fee.

To mint an 1155 token, the `mint` function is called on the ZoraTimedSaleStrategy contract with the mint fee of 0.000111 eth x quantity to mint sent with the call. In the `mint` call, 0.0000111 eth x quantity is held in escrow to bootstrap liquidity for the Uniswap V3 pool, the rest is distributed as rewards.
via the [ProtocolRewards](./rewards) contract, and x quantity of 1155s is minted to the `recipient`.
To mint an 1155 token, the `mint` function is called on the ZoraTimedSaleStrategy contract with the mint fee of 0.000111 eth x quantity to mint sent with the call. In the `mint` call, 0.0000111 eth x quantity is held in escrow to bootstrap liquidity for the Uniswap V3 pool, the rest is distributed as rewards via the [ProtocolRewards](./rewards) contract, and x quantity of 1155s is minted to the `recipient`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice fix

docs/pages/contracts/ZoraTimedSaleStrategy.mdx Outdated Show resolved Hide resolved
@Dimitrolito
Copy link
Author

Hi @oveddan ,

Thanks for the feedback! I’ve reverted the changes as requested and undone the modifications.

Let me know if anything else needs to be adjusted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants