aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormoneromooo-monero <moneromooo-monero@users.noreply.github.com>2019-09-06 12:29:21 +0000
committermoneromooo-monero <moneromooo-monero@users.noreply.github.com>2019-09-06 12:30:31 +0000
commitae32862604c8d38270256ed6e6a22278a1d55045 (patch)
tree0cc04e5ef569c1ea35cee530bfcd443cb0a50204
parentMerge pull request #5824 (diff)
downloadmonero-ae32862604c8d38270256ed6e6a22278a1d55045.tar.xz
README: fix master branch spelling, it is not Master
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 4af4c7764..29b7d79d7 100644
--- a/README.md
+++ b/README.md
@@ -156,7 +156,7 @@ X's indicate that these details have not been determined as of commit date.
## Release staging schedule and protocol
-Approximately three months prior to a scheduled software upgrade, a branch from Master will be created with the new release version tag. Pull requests that address bugs should then be made to both Master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should *not* be made to the release branch.
+Approximately three months prior to a scheduled software upgrade, a branch from master will be created with the new release version tag. Pull requests that address bugs should then be made to both master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should *not* be made to the release branch.
## Compiling Monero from source