avoid it's, use it is

http/cookies.md

@@ -46,9 +46,8 @@ The file format curl uses for cookies is called the Netscape cookie format
 because it was once the file format used by browsers and then you could easily
 tell curl to use the browser's cookies!
 
-As a convenience, curl also supports a cookie file being a set of HTTP
-headers that set cookies. It's an inferior format but may be the only thing
-you have.
+As a convenience, curl also supports a cookie file being a set of HTTP headers
+that set cookies. It is an inferior format but may be the only thing you have.
 
 Tell curl which file to read the initial cookies from:
 

http/modify/user-agent.md

@@ -8,7 +8,7 @@ The default header value is 'curl/[version]', as in `User-Agent: curl/7.54.1`
 for curl version 7.54.1.
 
 You can set any value you like, using the option `-A` or `--user-agent` plus
-the string to use or, as it's just a header, `-H "User-Agent: foobar/2000"`.
+the string to use or, as it is just a header, `-H "User-Agent: foobar/2000"`.
 
 As comparison, a test version of Firefox on a Linux machine once sent this
 User-Agent header:

internals/content-encoding.md

@@ -15,7 +15,7 @@
  `Content-Encoding` header indicates which encodings were used to encode the
  data, in the order in which they were applied.
 
- It's also possible for a client to attach priorities to different schemes so
+ It is also possible for a client to attach priorities to different schemes so
  that the server knows which it prefers. See sec 14.3 of RFC 2616 for more
  information on the `Accept-Encoding` header. See sec [3.1.2.2 of RFC
  7231](https://datatracker.ietf.org/doc/html/rfc7231#section-3.1.2.2) for more

project/etiquette.md

@@ -15,7 +15,7 @@ no way to read the reply but to ask the one person the question. The one
 person consequently gets overloaded with mail.
 
 If you really want to contact an individual and perhaps pay for his or her
-services, by all means go ahead, but if it's just another curl question, take
+services, by all means go ahead, but if it is just another curl question, take
 it to a suitable list instead.
 
 ## Reply or new mail

project/users.md

@@ -33,7 +33,7 @@ the Internet, the occasional "about box" or license agreement mentioning curl
 or that authors ask for help and tell us about their use.
 
 The curl license says users need to repeat it somewhere, like in the
-documentation, but that is not easy for us to find in many cases and it's also
+documentation, but that is not easy for us to find in many cases and it is also
 not easy for us to do anything about should they decide not to follow the
 small license requirement.
 

source/layout.md

@@ -177,7 +177,7 @@ Handy scripts.
 - `contrithanks.sh`: extracts contributors from the git repository since a
   given hash/tag, filters out all the names that are already mentioned in
   `THANKS`, and then outputs `THANKS` to stdout with the list of new
-  contributors appended at the end; it's meant to allow easier updates of the
+  contributors appended at the end; it is meant to allow easier updates of the
   THANKS document. The script uses the `THANKS-filter` file to rewrite some
   names.
 - `log2changes.pl`: generates the `CHANGES` file for releases, as used by the

source/style.md

@@ -216,7 +216,7 @@ too long, the statement too hard to read, or due to other style guidelines
 above. In such a case the statement will span multiple lines.
 
 If a continuation line is part of an expression or sub-expression then you
-should align on the appropriate column so that it's easy to tell what part of
+should align on the appropriate column so that it is easy to tell what part of
 the statement it is. Operators should not start continuation lines. In other
 cases follow the 2-space indent guideline. Here are some examples from
 libcurl:

usingcurl/proxies/type.md

@@ -4,7 +4,7 @@ curl supports several different types of proxies.
 
 The default proxy type is HTTP so if you specify a proxy host name (or IP
 address) without a scheme part (the part that is often written as `http://`)
-curl goes with assuming it's an HTTP proxy.
+curl goes with assuming it is an HTTP proxy.
 
 curl provides a number of options to set the proxy type instead of using the
 scheme prefix. See the [SOCKS](socks.md) section.

usingcurl/verbose/writeout.md

@@ -64,7 +64,7 @@ Some of these variables are not available in really old curl versions.
 | `content_type`            | Content-Type of the requested document, if there was any.                                                                                                                                                                        |
 | `errormsg`                | Error message from the transfer. Empty if no error occurred. (Introduced in 7.75.0)                                                                                                                                              |
 | `exitcode`                | Numerical exit code from the transfer. 0 if no error occurred. (Introduced in 7.75.0)                                                                                                                                            |
-| `filename_effective`      | The ultimate filename that curl writes out to. Practical if curl is told to write to a file with the `--remote-name` or `--output` option. It's most useful in combination with the `--remote-header-name` option.               |
+| `filename_effective`      | The ultimate filename that curl writes out to. Practical if curl is told to write to a file with the `--remote-name` or `--output` option. It is most useful in combination with the `--remote-header-name` option.               |
 | `ftp_entry_path`          | The initial path curl ended up in when logging on to the remote FTP server.                                                                                                                                                      |
 | `http_code`               | The former variable name for what is now known as `response_code`.                                                                                                                                                               |
 | `http_connect`            | the numerical code that was found in the last response (from a proxy) to a curl CONNECT request.                                                                                                                                 |