From: Ayushman Singh Chauhan Date: Tue, 27 Apr 2021 17:53:43 +0000 (+0530) Subject: docs: camelcase it like GitHub everywhere X-Git-Tag: curl-7_77_0~117 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6aae7b1761c02a63d4b4154867c5f7853f74bb14;p=thirdparty%2Fcurl.git docs: camelcase it like GitHub everywhere Closes #6979 --- diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index e9a66ec6e1..48c2ba0a5b 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -4,7 +4,7 @@ How to contribute to curl Join the community ------------------ - 1. Click 'watch' on the github repo + 1. Click 'watch' on the GitHub repo 2. Subscribe to the suitable [mailing lists](https://curl.se/mail/) diff --git a/docs/CONTRIBUTE.md b/docs/CONTRIBUTE.md index 6b86b25c47..8b97009825 100644 --- a/docs/CONTRIBUTE.md +++ b/docs/CONTRIBUTE.md @@ -20,7 +20,7 @@ Before posting to one of the curl mailing lists, please read up on the We also hang out on IRC in #curl on irc.freenode.net If you're at all interested in the code side of things, consider clicking -'watch' on the [curl repo on github](https://github.com/curl/curl) to be +'watch' on the [curl repo on GitHub](https://github.com/curl/curl) to be notified of pull requests and new issues posted there. ### License and copyright @@ -129,7 +129,7 @@ verified your changes. ### How to get your changes into the main sources Ideally you file a [pull request on -github](https://github.com/curl/curl/pulls), but you can also send your plain +GitHub](https://github.com/curl/curl/pulls), but you can also send your plain patch to [the curl-library mailing list](https://curl.se/mail/list.cgi?list=curl-library). diff --git a/docs/GOVERNANCE.md b/docs/GOVERNANCE.md index a4c006fbef..5abd848c34 100644 --- a/docs/GOVERNANCE.md +++ b/docs/GOVERNANCE.md @@ -131,7 +131,7 @@ within the area of personal expertise and experience. ### Recommendations -- we require two-factor authentication enabled on your github account to +- we require two-factor authentication enabled on your GitHub account to reduce risk of malicious source code tampering - consider enabling signed git commits for additional verification of changes @@ -142,7 +142,7 @@ When you're merging patches/PRs... - make sure the commit messages follow our template - squash patch sets into a few logical commits even if the PR didn't, if necessary -- avoid the "merge" button on github, do it "manually" instead to get full +- avoid the "merge" button on GitHub, do it "manually" instead to get full control and full audit trail (github leaves out you as "Committer:") - remember to credit the reporter and the helpers! diff --git a/docs/HISTORY.md b/docs/HISTORY.md index 6210e902ab..373741c586 100644 --- a/docs/HISTORY.md +++ b/docs/HISTORY.md @@ -257,7 +257,7 @@ January: Added support for RTSP February: security vulnerability: libcurl data callback excessive length -March: The project switched over to use git (hosted by github) instead of CVS +March: The project switched over to use git (hosted by GitHub) instead of CVS for source code control May: Added support for RTMP diff --git a/docs/RELEASE-PROCEDURE.md b/docs/RELEASE-PROCEDURE.md index c41dafa63c..3faad65117 100644 --- a/docs/RELEASE-PROCEDURE.md +++ b/docs/RELEASE-PROCEDURE.md @@ -44,7 +44,7 @@ in the curl-www repo (the website then updates its contents automatically) -on github +on GitHub --------- - edit the newly made release tag so that it is listed as the latest release