docs: minor grammar fixes

Closes #9609

diff --git a/README b/README
index 62ea95fe07eb6305d0e664e364a10947e88c9cf3..f5efbd70a69decce435bacce9f0da0702edecb6e 100644 (file)
--- 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 472dc4443c6349609fff6cb0da2be3ea637ff24a..c4728f9b1e11377bfc4ba62d17cce98131242577 100644 (file)
--- 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 d347f6e1991df9cb416e5909da8cc7ecc77bb480..560b43748ac066b210065be93147bfb2cc2db73a 100644 (file)
--- 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 df6e302b2f4374192fffe5da36579b462bccf500..9d18ffe9fa1e4e79f20cf1e93b41e81e2641f104 100644 (file)
--- 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 43016e22cea6500fbca031da5d58c40fed6d2159..a8b227d3c0b010e92160df1c5b5c025799641e28 100644 (file)
--- 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 806122c8b21c92281e552c29eaa926df4f6d8eab..96d6bec42e8466fb281269bcb2952831962f4be6 100644 (file)
--- 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.