Skip to content

Commit

Permalink
Readme_proofread
Browse files Browse the repository at this point in the history
  • Loading branch information
reveloper authored Feb 7, 2025
1 parent 54e34c7 commit 3441bcc
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/v3/contribute/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,20 @@

### Who can submit content to docs.ton.org

TON Documentation is entirely open source. Community enthusiasts and early TON contributors have played a key role in creating our open source TON Documentation by turning their personal notes into detailed pages.
TON Documentation is entirely open source. Community enthusiasts and early TON contributors have played a key role in creating our open-source TON Documentation by turning their notes into detailed pages.

It is originally written by TON [contributors](/v3/contribute/maintainers) and supported by [TON Studio](https://tonstudio.io/).
We aim to educate users about TON through clear, easily searchable content that appeals to both technical experts and casual readers.
It was initially written by TON [contributors](/v3/contribute/maintainers) and supported by [TON Studio](https://tonstudio.io/).
We aim to educate users about TON through explicit, easily searchable content that appeals to technical experts and casual readers.


### How to contribute

:::info
This documentation is written in English. For other languages, please refer to [localization program](/v3/contribute/localization-program/overview/).
This documentation is written in English. Please refer to [localization program](/v3/contribute/localization-program/overview/) for other languages.
:::

1. Clone a current version from the [ton-docs](https://github.com/ton-community/ton-docs) GitHub repository.
1. Identify area for contribution according to [Style guide](/v3/contribute/style-guide/) and open a related [issue](https://github.com/ton-community/ton-docs/issues).
1. Determinate an area for contribution according to [Style guide](/v3/contribute/style-guide/) and open a related [issue](https://github.com/ton-community/ton-docs/issues).
2. Familiarize yourself with [Content standardization](/v3/contribute/content-standardization/) and [Typography](/v3/contribute/typography/).
3. Open a pull request against the `main` branch with a clear description and concise updates according to the template.

Expand All @@ -37,10 +37,10 @@ Please provide a brief description of the changes introduced in this pull reques
- [ ] I have reviewed and formatted the text in the article according to [Typography](https://docs.ton.org/v3/contribute/typography/).

```
4. Ensure you complete and verify each milestone in the description checklist before submitting your pull request.
4. Before submitting your pull request, complete and verify each milestone in the description checklist.

:::info
Make sure you've read the contribution guidelines on the Style Guide, Content Standardization, and Typography before contributing to avoid unnecessary rework. Don't worry about minor issuesmaintainers will help you fix them during the review process.
To avoid excessive rework, read the contribution guidelines in the Style guide, Content standardization, and Typography before contributing. Don't worry about minor issues; maintainers will help you fix them during the review process.
:::

### Development
Expand Down

0 comments on commit 3441bcc

Please sign in to comment.