aboutsummaryrefslogtreecommitdiff
path: root/docs/HTTP-COOKIES.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/HTTP-COOKIES.md')
-rw-r--r--docs/HTTP-COOKIES.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/HTTP-COOKIES.md b/docs/HTTP-COOKIES.md
index 9d1e099d1..c7c116b10 100644
--- a/docs/HTTP-COOKIES.md
+++ b/docs/HTTP-COOKIES.md
@@ -8,13 +8,13 @@
Cookies are either "session cookies" which typically are forgotten when the
session is over which is often translated to equal when browser quits, or
- the cookies aren't session cookies they have expiration dates after which
+ the cookies are not session cookies they have expiration dates after which
the client will throw them away.
Cookies are set to the client with the Set-Cookie: header and are sent to
servers with the Cookie: header.
- For a very long time, the only spec explaining how to use cookies was the
+ For a long time, the only spec explaining how to use cookies was the
original [Netscape spec from 1994](https://curl.se/rfc/cookie_spec.html).
In 2011, [RFC6265](https://www.ietf.org/rfc/rfc6265.txt) was finally
@@ -48,7 +48,7 @@
The cookie file format is text based and stores one cookie per line. Lines
that start with `#` are treated as comments.
- Each line that each specifies a single cookie consists of seven text fields
+ Each line that specifies a single cookie consists of seven text fields
separated with TAB characters. A valid line must end with a newline
character.
@@ -74,7 +74,7 @@
`-b, --cookie`
tell curl a file to read cookies from and start the cookie engine, or if it
- isn't a file it will pass on the given string. -b name=var works and so does
+ is not a file it will pass on the given string. -b name=var works and so does
-b cookiefile.
`-j, --junk-session-cookies`