diff options
| author | Andrei Muresan <andreix64@users.noreply.github.com> | 2017-04-11 22:09:37 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-11 22:09:37 +0300 |
| commit | 35755a91a0485650739d02fb0e87f8c84bd1908f (patch) | |
| tree | e0508cbbebfc6617794ba995532a54181246780a /README.md | |
| parent | Merge pull request #1956 (diff) | |
| download | monero-35755a91a0485650739d02fb0e87f8c84bd1908f.tar.xz | |
Spelling mistake in About this project paragraph
I corrected a spelling mistake in the About this project paragraph.
Diffstat (limited to '')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -50,7 +50,7 @@ This is the core implementation of Monero. It is open source and completely free As with many development projects, the repository on Github is considered to be the "staging" area for the latest changes. Before changes are merged into that branch on the main repository, they are tested by individual developers in their own branches, submitted as a pull request, and then subsequently tested by contributors who focus on testing and code reviews. That having been said, the repository should be carefully considered before using it in a production environment, unless there is a patch in the repository for a particular show-stopping issue you are experiencing. It is generally a better idea to use a tagged release for stability. -**Anyone is welcome to contribute to Monero's codebase!** If you have a fix or code change, feel free to submit is as a pull request directly to the "master" branch. In cases where the change is relatively small or does not affect other parts of the codebase it may be merged in immediately by any one of the collaborators. On the other hand, if the change is particularly large or complex, it is expected that it will be discussed at length either well in advance of the pull request being submitted, or even directly on the pull request. +**Anyone is welcome to contribute to Monero's codebase!** If you have a fix or code change, feel free to submit it as a pull request directly to the "master" branch. In cases where the change is relatively small or does not affect other parts of the codebase it may be merged in immediately by any one of the collaborators. On the other hand, if the change is particularly large or complex, it is expected that it will be discussed at length either well in advance of the pull request being submitted, or even directly on the pull request. ## Supporting the Project |