From 75670e457367515dc88cf43f7a4b9ddb9c5ab59e Mon Sep 17 00:00:00 2001 From: Thiago Suchorski Date: Tue, 27 Sep 2022 13:53:54 -0300 Subject: [PATCH] docs: minor grammar fixes Closes #9609 --- README | 2 +- README.md | 2 +- docs/ALTSVC.md | 2 +- docs/BUGS.md | 4 ++-- docs/NEW-PROTOCOL.md | 2 +- docs/SECURITY-PROCESS.md | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README b/README index 62ea95fe07eb..f5efbd70a69d 100644 --- a/README +++ b/README @@ -36,7 +36,7 @@ WEBSITE GIT - To download the latest source code off the GIT server do this: + To download the latest source code off the GIT server, do this: git clone https://github.com/curl/curl.git diff --git a/README.md b/README.md index 472dc4443c63..c4728f9b1e11 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,7 @@ downloads. ## Git -To download the latest source from the Git server do this: +To download the latest source from the Git server, do this: git clone https://github.com/curl/curl.git diff --git a/docs/ALTSVC.md b/docs/ALTSVC.md index d347f6e1991d..560b43748ac0 100644 --- a/docs/ALTSVC.md +++ b/docs/ALTSVC.md @@ -14,7 +14,7 @@ curl features support for the Alt-Svc: HTTP header. # Alt-Svc cache file format -This a text based file with one line per entry and each line consists of nine +This is a text based file with one line per entry and each line consists of nine space separated fields. ## Example diff --git a/docs/BUGS.md b/docs/BUGS.md index df6e302b2f43..9d18ffe9fa1e 100644 --- a/docs/BUGS.md +++ b/docs/BUGS.md @@ -162,7 +162,7 @@ experimental build or similar, to get this confirmed or not. At times people insist that they cannot upgrade to a modern curl version, but - instead they "just want the bug fixed". That is fine, just do not count on us + instead, they "just want the bug fixed". That is fine, just do not count on us spending many cycles on trying to identify which single commit, if that is even possible, that at some point in the past fixed the problem you are now experiencing. @@ -181,7 +181,7 @@ maybe they are off in the woods hunting. Have patience. Allow at least a few days before expecting someone to have responded. - In the issue tracker you can expect that some labels will be set on the issue + In the issue tracker, you can expect that some labels will be set on the issue to help categorize it. ## First response diff --git a/docs/NEW-PROTOCOL.md b/docs/NEW-PROTOCOL.md index 43016e22cea6..a8b227d3c0b0 100644 --- a/docs/NEW-PROTOCOL.md +++ b/docs/NEW-PROTOCOL.md @@ -1,6 +1,6 @@ # Adding a new protocol? -Every once in a while someone comes up with the idea of adding support for yet +Every once in a while, someone comes up with the idea of adding support for yet another protocol to curl. After all, curl already supports 25 something protocols and it is the Internet transfer machine for the world. diff --git a/docs/SECURITY-PROCESS.md b/docs/SECURITY-PROCESS.md index 806122c8b21c..96d6bec42e84 100644 --- a/docs/SECURITY-PROCESS.md +++ b/docs/SECURITY-PROCESS.md @@ -19,7 +19,7 @@ No information should be made public about a vulnerability until it is formally announced at the end of this process. That means, for example, that a bug tracker entry must NOT be created to track the issue since that will make the issue public and it should not be discussed on any of the project's public -mailing lists. Also messages associated with any commits should not make any +mailing lists. Messages associated with any commits should not make any reference to the security nature of the commit if done prior to the public announcement.