there's => there is

cmdline.md

@@ -38,7 +38,7 @@ One way that command-line systems differ, for example, is how you can put
 quotes around arguments such as to embed spaces or special symbols. In
 most Unix-like shells you use double quotes (") and single quotes (')
 depending if you want to allow variable expansions or not within the quoted
-string, but on Windows there's no support for the single quote version.
+string, but on Windows there is no support for the single quote version.
 
 In some environments, like PowerShell on Windows, the authors of the command
 line system decided they know better and "help" the user to use another tool

cmdline/urls/options.md

@@ -2,7 +2,7 @@
 
 As mentioned above, curl supports hundreds of command-line options and it also
 supports an unlimited number of URLs. If your shell or command-line system
-supports it, there's really no limit to how long a command line you can pass
+supports it, there is really no limit to how long a command line you can pass
 to curl.
 
 curl will parse the entire command line first, apply the wishes from the

cmdline/urls/path.md

@@ -1,6 +1,6 @@
 # Path
 
-Every URL contains a path. If there's none given, `/` is implied. For example
+Every URL contains a path. If there is none given, `/` is implied. For example
 when you use just the host name like in:
 
     curl https://example.com

ftp/twoconnections.md

@@ -15,7 +15,7 @@ several reasons.
 The client can opt to ask the server to connect to the client to set it up, a
 so-called "active" connection. This is done with the PORT or EPRT
 commands. Allowing a remote host to connect back to a client on a port that
-the client opens up requires that there's no firewall or other network
+the client opens up requires that there is no firewall or other network
 appliance in between that refuses that to go through and that is far from
 always the case. You ask for an active transfer using `curl -P [arg]` (also
 known as `--ftp-port` in long form) and while the option allows you to specify

http.md

@@ -11,7 +11,7 @@ the specific [HTTPS](#https) section below.
 
 ## HTTP methods
 
-In every HTTP request, there's a method. Sometimes called a verb. The most
+In every HTTP request, there is a method. Sometimes called a verb. The most
 commonly used ones are GET, POST, HEAD and PUT.
 
 Normally however you do not specify the method in the command line, but

http/modify/target.md

@@ -11,7 +11,7 @@ In some rare circumstances, user may want to go creative and change this
 request target in ways that the URL does not really allow. For example, the
 HTTP OPTIONS method has a specially define request target for magic that
 concerns *the server* and not a specific path, and it uses `*` for that. Yes,
-a single asterisk. There's no way to specify a URL for this, so if you want to
+a single asterisk. There is no way to specify a URL for this, so if you want to
 pass a single asterisk in the request target to a server, like for OPTIONS,
 you have to do it like this:
 

http/post/javascript.md

@@ -2,7 +2,7 @@
 
 A common mitigation against automated agents or scripts using curl is to have
 the page with the HTML form use JavaScript to set values of some input fields,
-usually one of the hidden ones. Often, there's some JavaScript code that
+usually one of the hidden ones. Often, there is some JavaScript code that
 executes on page load or when the submit button is pressed which sets a magic
 value that the server then can verify before it considers the submission to be
 valid.

http/redirects.md

@@ -40,7 +40,7 @@ response” to the original request rather than just a redirect.
 These three codes were the only redirect codes in the HTTP/1.0 spec.
 
 curl however, does not remember or cache any redirects at all so to it,
-there's really no difference between permanent and temporary redirects.
+there is really no difference between permanent and temporary redirects.
 
 ## Tell curl to follow redirects
 
@@ -49,7 +49,7 @@ it does not follow HTTP redirects by default. Use the `-L, --location` option
 to tell it to do that.
 
 When following redirects is enabled, curl will follow up to 50 redirects by
-default. There's a maximum limit mostly to avoid the risk of getting caught in
+default. There is a maximum limit mostly to avoid the risk of getting caught in
 endless loops. If 50 is not sufficient for you, you can change the maximum
 number of redirects to follow with the `--max-redirs` option.
 
@@ -109,7 +109,7 @@ the same transfer.
 
 So if you want the credentials to also get sent to the following host names
 even though they are not the same as the original—presumably because you
-trust them and know that there's no harm in doing that—you can tell curl that
+trust them and know that there is no harm in doing that—you can tell curl that
 it is fine to do so by using the `--location-trusted` option.
 
 # Non-HTTP redirects

http/response.md

@@ -35,7 +35,7 @@ The first digit of the HTTP response code is a kind of "error class":
  - 2xx: success
  - 3xx: a redirect
  - 4xx: the client asked for something the server could not or would not deliver
- - 5xx: there's a problem in the server
+ - 5xx: there is a problem in the server
 
 Remember that you can use curl's `--write-out` option to extract the response
 code. See the [--write-out](../usingcurl/verbose/writeout.md) section.
@@ -58,9 +58,9 @@ numeric range and you can use `--write-out` to extract that code as well.
 An HTTP 1.1 server can decide to respond with a "chunked" encoded response, a
 feature that was not present in HTTP 1.0.
 
-When receiving a chunked response, there's no Content-Length: for the response
-to indicate its size. Instead, there's a `Transfer-Encoding: chunked` header
-that tells curl there's chunked data coming and then in the response body, the
+When receiving a chunked response, there is no Content-Length: for the response
+to indicate its size. Instead, there is a `Transfer-Encoding: chunked` header
+that tells curl there is chunked data coming and then in the response body, the
 data comes in a series of "chunks". Every individual chunk starts with the
 size of that particular chunk (in hexadecimal), then a newline and then the
 contents of the chunk. This is repeated over and over until the end of the
@@ -79,7 +79,7 @@ Responses over HTTP can be sent in compressed format. This is most commonly
 done by the server when it includes a `Content-Encoding: gzip` in the response
 as a hint to the client. Compressed responses make a lot of sense when either
 static resources are sent (that were compressed previously) or even in
-run-time when there's more CPU power available than bandwidth. Sending a much
+run-time when there is more CPU power available than bandwidth. Sending a much
 smaller amount of data is often preferred.
 
 You can ask curl to both ask for compressed content *and* automatically and

internals/easy.md

@@ -7,7 +7,7 @@ know and keep in mind:
    (`struct Curl_easy`) for the transfer being worked on. No other name should
    be used for this and nothing else should use this name. The easy handle is
    the main object identifying a transfer. A transfer typically uses a
-   connection at some point and typically only one at a time. There's a
+   connection at some point and typically only one at a time. There is a
    `data->conn` pointer that identifies the connection that is currently used
    by this transfer. A single connection can be used over time and even
    concurrently by several transfers (and thus easy handles) when multiplexed

internals/handler.md

@@ -10,7 +10,7 @@ However, each different protocol libcurl speaks also has its unique
 particularities and specialties. In order to not have the code littered with
 conditions in the style "if the protocol is XYZ, then do…", we instead have
 the concept of `Curl_handler`. Each supported protocol defines one of those in
-`lib/url.c` there's an array of pointers to such handlers called
+`lib/url.c` there is an array of pointers to such handlers called
 `protocols[]`.
 
 When a transfer is about to be done, libcurl parses the URL it is about to

libcurl-http/download.md

@@ -11,7 +11,7 @@ particular resource—the standard HTTP download request:
 Since options set in an easy handle are sticky and remain until changed, there
 may be times when you have asked for another request method than GET and then
 want to switch back to GET again for a subsequent request. For this purpose,
-there's the `CURLOPT_HTTPGET` option:
+there is the `CURLOPT_HTTPGET` option:
 
     curl_easy_setopt(easy, CURLOPT_HTTPGET, 1L);
 

libcurl-http/upload.md

@@ -31,7 +31,7 @@ application/x-www-form-urlencoded`.
 
 A multipart formpost is still using the same HTTP method POST; the difference
 is only in the formatting of the request body. A multipart formpost is a
-series of separate "parts", separated by MIME-style boundary strings. There's
+series of separate "parts", separated by MIME-style boundary strings. There is
 no limit to how many parts you can send.
 
 Each such part has a name, a set of headers and a few other properties.

libcurl/connectionreuse.md

@@ -8,10 +8,10 @@ one. Reusing a connection instead of creating a new one offers significant
 benefits in speed and required resources.
 
 When libcurl is about to make a new connection for the purposes of doing a
-transfer, it will first check to see if there's an existing connection in the
+transfer, it will first check to see if there is an existing connection in the
 pool that it can reuse instead. The connection re-use check is done before any
 DNS or other name resolving mechanism is used, so it is purely host name
-based. If there's an existing live connection to the right host name, a lot of
+based. If there is an existing live connection to the right host name, a lot of
 other properties (port number, protocol, etc) are also checked to see that it
 can be used.
 

libcurl/names.md

@@ -37,7 +37,7 @@ there will be no blocking calls involved.
 functions. They unfortunately make all transfers within a multi handle block
 during its operation and it is much harder to time out nicely.
 
-3. There's also support for resolving with the c-ares third party library,
+3. There is also support for resolving with the c-ares third party library,
 which supports asynchronous name resolving without the use of threads. This
 scales better to huge number of parallel transfers but it is not always 100%
 compatible with the native name resolver functionality.
@@ -94,7 +94,7 @@ following redirects etc.
 
 ## Name server options
 
-For libcurl built to use c-ares, there's a few options available that offer
+For libcurl built to use c-ares, there is a few options available that offer
 fine-grained control of what DNS servers to use and how. This is limited to
 c-ares build purely because these are powers that are not available when the
 standard system calls for name resolving are used.

libcurl/options.md

@@ -50,7 +50,7 @@ Enforce a curl_off_t:
 
 ## Get handle options
 
-No, there's no general method to extract the same information you previously
+No, there is no general method to extract the same information you previously
 set with `curl_easy_setopt()`! If you need to be able to extract the
 information again that you set earlier, then we encourage you to keep track of
 that data yourself in your application.

project/future.md

@@ -2,7 +2,7 @@
 
 ![curl future](devgraph-800.png)
 
-There's no slowdown in sight in curl's future, bugs reported, development
+There is no slowdown in sight in curl's future, bugs reported, development
 pace or how Internet protocols are being developed or updated.
 
 We are looking forward to support for more protocols, support for more features
@@ -14,8 +14,9 @@ file holding a bunch of ideas that we could work on in the future. It also
 keeps a [KNOWN_BUGS](https://curl.se/docs/knownbugs.html) document with
 a list of known problems we would like to fix.
 
-There's a [ROADMAP](https://curl.se/dev/roadmap.html) document that
+There is a [ROADMAP](https://curl.se/dev/roadmap.html) document that
 describes some plans for the short-term that some of the active developers
+
 thought they would work on next. Of course, we can not promise that we will
 always follow it perfectly.
 

project/users.md

@@ -39,7 +39,7 @@ small license requirement.
 ### Command-line tool users
 
 The command-line tool curl is widely used by programmers around the world in
-shell and batch scripts, to debug servers and to test out things. There's no
+shell and batch scripts, to debug servers and to test out things. There is no
 doubt it is used by millions every day.
 
 ### Embedded library

protocols/network.md

@@ -9,7 +9,7 @@ addresses. These computers are often called hosts.
 The computer, tablet or phone you sit in front of is usually called "the
 client" and the machine out there somewhere that you want to exchange data
 with is called "the server". The main difference between the client and the
-server is in the roles they play here. There's nothing that prevents the roles
+server is in the roles they play here. There is nothing that prevents the roles
 from being reversed in a subsequent operation.
 
 ### Which machine
@@ -76,7 +76,7 @@ will do a TLS handshake first and only continue further if that succeeds.
 ### Transfer data
 
 When the connecting "string" we call TCP is attached to the remote computer
-(and we have done the possible additional TLS handshake), there's an
+(and we have done the possible additional TLS handshake), there is an
 established connection between the two machines and that connection can then
 be used to exchange data. That communication is done using a "protocol", as
 discussed in the following chapter.

protocols/protocols.md

@@ -28,7 +28,7 @@ or flavors as well.
 ## What other protocols are there?
 
 The world is full of protocols, both old and new. Old protocols get abandoned
-and dropped and new ones get introduced. There's never a state of stability but
+and dropped and new ones get introduced. There is never a state of stability but
 the situation changes from day to day and year to year. You can rest assured
 that there will be new protocols added in the list above in the future and that
 there will be new versions of the protocols already listed.

source/build/boringssl.md

@@ -15,7 +15,7 @@ like.
 
 ## set up the build tree to get detected by curl's configure
 
-In the boringssl source tree root, make sure there's a `lib` and an `include`
+In the boringssl source tree root, make sure there is a `lib` and an `include`
 dir. The `lib` dir should contain the two libs (I made them symlinks into the
 build dir). The `include` dir is already present by default. Make and populate
 `lib` like this (commands issued in the source tree root, not in the `build/`

source/build/fromsource.md

@@ -33,7 +33,7 @@ running `./buildconf` and on Windows, run `buildconf.bat`.
 ## On Linux and Unix-like systems
 
 There are two distinctly different ways to build curl on Linux and other
-Unix-like systems; there's the one using the configure script and there's the
+Unix-like systems; there is the one using the configure script and there is the
 CMake approach.
 
 There are two different build environments to cater to people's different

source/style.md

@@ -40,7 +40,7 @@ Source code in curl may never be wider than 80 columns. There are two reasons
 for maintaining this even in the modern era of large and high resolution
 screens:
 
-1. Narrower columns are easier to read than wide ones. There's a reason
+1. Narrower columns are easier to read than wide ones. There is a reason
    newspapers have used columns for decades or centuries.
 
 2. Narrower columns allow developers to more easily view multiple pieces of code

usingcurl/connections/name.md

@@ -32,7 +32,7 @@ When setting a custom `Host:` header and using cookies, curl will extract the
 custom name and use that as host when matching cookies to send off.
 
 The `Host:` header is not enough when communicating with an HTTPS server. With
-HTTPS there's a separate extension field in the TLS protocol called SNI
+HTTPS there is a separate extension field in the TLS protocol called SNI
 (Server Name Indication) that lets the client tell the server the name of the
 server it wants to talk to. curl will only extract the SNI name to send from
 the given URL.

usingcurl/downloads/browsers.md

@@ -31,7 +31,7 @@ The server that receives the request and delivers data is often setup to act in
 certain ways depending on what kind of client it thinks communicates with it.
 Sometimes it is as innocent as trying to deliver the best content for the
 client, sometimes it is to hide some content for some clients or even to try
-to work around known problems in specific browsers. Then there's also, of
+to work around known problems in specific browsers. Then there is also, of
 course, various kind of login systems that might rely on HTTP authentication or
 cookies or the client being from the pre-validated IP address range.
 

usingcurl/downloads/content-disp.md

@@ -5,7 +5,7 @@ in responses. That header may contain a suggested file name for the contents
 delivered, and curl can be told to use that hint to name its local file. The
 `-J / --remote-header-name` enables this. If you also use the `-O` option,
 it makes curl use the file name from the URL by default and only *if*
-there's actually a valid Content-Disposition header available, it switches to
+there is actually a valid Content-Disposition header available, it switches to
 saving using that name.
 
 `-J` has some problems and risks associated with it that users need to be

usingcurl/proxies/auth.md

@@ -22,7 +22,7 @@ the proxy:
 
     curl -U daniel:secr3t -x myproxy:80 http://example.com --proxy-ntlm
 
-There's also the option that asks curl to figure out which method the proxy
+There is also the option that asks curl to figure out which method the proxy
 wants and supports and then go with that (with the possible expense of extra
 roundtrips) using `--proxy-anyauth`. Asking curl to use any method the proxy
 wants is then like this:

usingcurl/proxies/env.md

@@ -25,7 +25,7 @@ separated list of host names that should not use a proxy when being
 accessed. You can set NO_PROXY to be a single asterisk ('\*') to match all
 hosts.
 
-As an alternative to the NO_PROXY variable, there's also a `--noproxy` command
+As an alternative to the NO_PROXY variable, there is also a `--noproxy` command
 line option that serves the same purpose and works the same way.
 
 ## `http_proxy` in lower case only

usingcurl/proxies/socks.md

@@ -28,7 +28,7 @@ resolving the host name locally:
     curl --socks5 proxy.example.com http://www.example.com/
 
 The SOCKS5-hostname versions. This sends the host name to the server so
-there's no name resolving done locally:
+there is no name resolving done locally:
 
     curl -x socks5h://proxy.example.com http://www.example.com/
 

usingcurl/timeouts.md

@@ -61,7 +61,7 @@ seconds, stop it:
 ## Keep connections alive
 
 curl enables TCP keep-alive by default. TCP keep-alive is a feature that makes
-the TCP stack send a probe to the other side when there's no traffic, to make
+the TCP stack send a probe to the other side when there is no traffic, to make
 sure that it is still there and "alive". By using keep-alive, curl is much
 more likely to discover that the TCP connection is dead.
 

usingcurl/tls/enable.md

@@ -32,7 +32,7 @@ The support table looks like this:
 The protocols that _can_ do `--ssl` all favor that method. Using `--ssl` means
 that curl will *attempt* to upgrade the connection to TLS but if that fails,
 it will still continue with the transfer using the plain-text version of the
-protocol. To make the `--ssl` option **require** TLS to continue, there's
+protocol. To make the `--ssl` option **require** TLS to continue, there is
 instead the `--ssl-reqd` option which will make the transfer fail if curl
 cannot successfully negotiate TLS.
 

usingcurl/uploads.md

@@ -35,7 +35,7 @@ with curl](../http/post.md) chapter.
 ### multipart formpost
 
 Multipart formposts are also used in HTML forms on websites; typically when
-there's a file upload involved. This type of upload is also an HTTP POST but
+there is a file upload involved. This type of upload is also an HTTP POST but
 it sends the data formatted according to some special rules, which is what the
 "multipart" name means.
 

usingcurl/verbose/trace.md

@@ -15,7 +15,7 @@ stdout. You would use it like this:
 
     $ curl --trace dump http://example.com
 
-When completed, there's a 'dump' file that can turn out pretty sizable. In
+When completed, there is a 'dump' file that can turn out pretty sizable. In
 this case, the 15 first lines of the dump file looks like:
 
     == Info: Rebuilt URL to: http://example.com/