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.

Sign up for GitHub

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

Jump to bottom

Update Guide on How to PIP.md - Correct Typos #392

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Guide on How to PIP.md - Correct Typos #392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Guide on How to PIP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ A Polygon Improvement Proposal (PIP) is a design document that proposes new feat

3. **Write the PIP**: Write the PIP using a template provided by the Polygon community. The template includes sections for introduction, motivation, specification, and rationale.

4. Gather feedback: Share your PIP with the Polygon community and get feedback from experts, developers, and users. You can do this by sharing the PIP on forums, social media, or by reaching out to relevant individuals.
4. **Gather feedback:** Share your PIP with the Polygon community and get feedback from experts, developers, and users. You can do this by sharing the PIP on forums, social media, or by reaching out to relevant individuals.

5. **Revise and finalize**: Revise your PIP based on the feedback you receive and finalize it.

Expand All @@ -48,7 +48,7 @@ PIPs are broader in scope and can encompass proposals for improvements to the Po

PRC, on the other hand, is focused specifically on proposals for standardizing smart contracts on the Polygon products. PRCs outline proposed standards fro smart contracts development and deployment, such as token standards, and provide a common framework for developers to build upon.

In summary, PIPs are for proposals that aim to improve the Polygon products as a whole, while PRCs are for proposals that aim sto standardize smart contract development on Polygon products.
In summary, PIPs are for proposals that aim to improve the Polygon products as a whole, while PRCs are for proposals that aim to standardize smart contract development on Polygon products.

#### !Remember! The PIP Editors will work with you to make sure that your proposal meets the PIP standard and that is formatted correctly.

Expand All @@ -59,5 +59,5 @@ Note: The Polygon community has a rigorous review process for PIPs and not all p
* Use the Polygon Forum to engage with the Community.
* Reach out to projects that are relevant to your proposal and ask them for feedback and ideas!
* Tip: Under the Verified Group in the Polygon Forum you will find a wide range of Ecosystem Partners and Dapps.
* White an article about the relevance of the PIP, explain your rational, inspiration and how it can be used to improve the protocol/community.
* Write an article about the relevance of the PIP, explain your rational, inspiration and how it can be used to improve the protocol/community.
* Engage in the discussion taking place in the Forum- Great minds work better together!