Fixed a bunch of typos

LAYOUT.md

@@ -5,7 +5,7 @@ Everything curl
  2. the cURL project
  3. curl and open source
  4. The curl source code
- 5. Network prototocols
+ 5. Network protocols
  6. The curl command line tool
  7. Using the curl tool
  8. Building and installing libcurl

building-binary.md

@@ -18,7 +18,7 @@ The most common ones are described below.
 
 ### apt-get
 
-`apt-get` is a tool to install pre-built packages on Debian Linux and Ubuntu
+`apt-get` is a tool to install prebuilt packages on Debian Linux and Ubuntu
 Linux distributions and derivates.
 
 To install the curl command line tool, you usually just

building-source.md

@@ -30,14 +30,14 @@ So, if you want to build curl from git you need to generate some of those
 files yourself before you can build. On Linux and unix systems, do this by
 running `./buildconf` and on Windows you run `buildconf.bat`.
 
-## On Linux and unixlike systems
+## 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 cmake
-approach.
+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
+cmake approach.
 
 There are two different build environments to cater for people's different
-opinons and tastes. The configure based build is arguably the more mature and
+opinions and tastes. The configure based build is arguably the more mature and
 more complete build system and should probably be considered the default one.
 
 ### Autotools
@@ -61,8 +61,8 @@ who wants to build curl and it does a whole bunch of things:
 
 In the most basic usage, just running `./configure` in the source directory is
 enough. When the script completes, it outputs a summary of what options it has
-detected/enabled and what featurs that are still disabled, some of them
-possibly because it failed to detect the prensence of necesary third party
+detected/enabled and what features that are still disabled, some of them
+possibly because it failed to detect the presence of necessary third party
 dependencies that are needed for those functions to work.
 
 Then you invoke `make` to build the entire thing and then you can invoke `make

building.md

@@ -18,12 +18,12 @@ different options will be explored below.
 ## The latest version?
 
 Looking at the curl web site at https://curl.haxx.se you can see the latest
-curl and libcurl version relased from the project. That's the latest source
+curl and libcurl version released from the project. That's the latest source
 code package you can get.
 
 When you opt for a prebuilt and prepackaged version for your operating system
 or distribution of choice, you may not always find the latest version but you
-might have to either be satisfied with the latest version somone has packaged
+might have to either be satisfied with the latest version someone has packaged
 for your environment, or you need to build it yourself from source.
 
 The curl project also provides info about the latest version in a somewhat

cmdline-configfile.md

@@ -1,12 +1,12 @@
 ## Config file
 
-You can easily end up with curl command lines that use a very lage amount of
+You can easily end up with curl command lines that use a very large amount of
 command line options, make it rather hard to work with. Sometimes the length
 of the command line you want to enter even hits the maximum length your
 command line system allows. The Microsoft windows command prompt being an
 example of something that has a fairly small maximum line length.
 
-To aid such sitations, curl offers a feature we call "config file". It
+To aid such situations, curl offers a feature we call "config file". It
 basically allows you to write command line options in a text file instead and
 then tell curl to read options from that file in addition to the command line.
 
@@ -58,7 +58,7 @@ therefore it can also be provided without the quotes like:
 
 Finally, if you want to provide a URL in a config file, you must do that the
 `--url` way, or just with `url`, and not like on the command line where
-basicaly everything that isn't an option is assumed to be a URL. So you
+basically everything that isn't an option is assumed to be a URL. So you
 provide a URL for curl like this:
 
     url = "http://example.com"

cmdline-globbing.md

@@ -5,7 +5,7 @@ small portion of it changing between the requests. Maybe it is a numeric range
 or maybe a set of names. curl offers "globbing" as a way to specify many URLs
 like that easily.
 
-The globbing uses the resevered symbols [] and {} for this, symbols that
+The globbing uses the reserved symbols [] and {} for this, symbols that
 normally cannot be part of a legal URL (except for numerical IPv6 addresses
 but curl handles them fine anyway). If the globbing gets in your way, disable
 it with `-g, --globoff`.

cmdline-progressmeter.md

@@ -7,7 +7,7 @@ how long it has been going on and how long it thinks it might be left until
 completion.
 
 The progress meter is inhibited if curl deems that there is output going to
-the terminal, as then would the progress meter interfer with that output and
+the terminal, as then would the progress meter interfere with that output and
 just mess out what gets displayed. A user can also forcibly switch off the
 progress meter with the `-s / --silent` option, which tells curl to hush.
 
@@ -35,7 +35,7 @@ system so 1024 is one kilobyte (1K), 2048 is 2K etc. curl supports these:
 | K       | 2^10    | kilobyte  |
 | M       | 2^20    | megabyte  |
 | G       | 2^30    | gigabyte  |
-| T       | 2^40    | terrabyte |
+| T       | 2^40    | terabyte  |
 | P       | 2^50    | petabyte  |
 
 The times are displayed using H:MM:SS for hours, minutes and seconds.

cmdline-urls.md

@@ -110,10 +110,10 @@ This is not a feature that is widely used.
 
 URLs that identify files on FTP servers have a special feature that allows you
 to also tell the client (curl in this case) which file type the resource
-is. This is becase FTP is a little special and can change mode for a transfer
+is. This is because FTP is a little special and can change mode for a transfer
 and thus handle the file differently than if it would use another mode.
 
-You tell curl that the FTP resource is an ASCIII type by appending ";type=A"
+You tell curl that the FTP resource is an ASCII type by appending ";type=A"
 to the URL. Getting the 'foo' file from example.com's root dir using ASCII
 could then be made with:
 

curl-comm.md

@@ -18,7 +18,7 @@ debugging or whatever.
 
 In this day and age, mailing lists may be considered sort of the old style of
 communication - no fancy web forum or similar. Using a mailing list is
-therefore becoming an art that isn't practiced everywhere and may be a bit
+therefore becoming an art that isn't practised everywhere and may be a bit
 strange and unusual to you. But fear not. It is just about sending emails to
 an address that then sends that email out to all the subscribers. Our mailing
 lists have at most a few thousand subscribers. If you're mailing for the first

curl-does.md

@@ -23,7 +23,7 @@ scripts and applications for an Internet connected world, but they're also
 widely used for server testing, protocol fiddling and trying out new things.
 
 The library is used in every imaginable sort of embedded device where Internet
-transfers are needed: car infotainment, televisions, blurayplayers, settop
+transfers are needed: car infotainment, televisions, blurayplayers, set-top
 boxes, printers, routers, game systems etc.
 
 ### Command line tool

curl-users.md

@@ -55,7 +55,7 @@ libcurl being written in C with no or just a few required dependencies also
 help to get it used in embedded systems.
 
 libcurl is popularly used in smartphone operating systems, in car infotainment
-setups, in television sets, in settop boxes, in audio and video equipment such
+setups, in television sets, in set-top boxes, in audio and video equipment such
 as bluray players and higher end receivers. It is often used in home routers
 and printers.
 
@@ -95,4 +95,4 @@ Chevrolet, Cisco, Comcast, Facebook, Google, Hitachi, Honeywell, HP, Huawei,
 HTC, IBM, Intel, LG, Mazda, Mercedes-Benz, Motorola, Netflix, Nintendo,
 Oracle, Panasonic, Philips, Pioneer, RBS, Samsung, SanDisk, SAP, SAS
 Institute, SEB, Sharp, Siemens, Sony, Spotify, Sun, Swisscom, Tomtom, Toshiba,
-Vmware, Xilinx, Yahoo, Yamaha
+VMware, Xilinx, Yahoo, Yamaha

ftp-traversedir.md

@@ -9,7 +9,7 @@ wants to transfers.
 curl can do one change-directory (CWD) command for every individual directory
 down the file tree hierarchy. If the full path is `one/two/three/file.txt`,
 that method means doing three `CWD` commands before asking for the `file.txt`
-file to get transfered. This method thus creates quite a large number of
+file to get transferred. This method thus creates quite a large number of
 commands if the path is many levels deep. This method is mandated by an early
 spec (RFC 1738) and is how curl acts by default.
 
@@ -40,7 +40,7 @@ This then equals this FTP command/response sequence (simplified)
 
 ### singlecwd
 
-This is the inbetween the other two FTP methods. This makes a single `CWD`
+This is the in-between the other two FTP methods. This makes a single `CWD`
 command to the target directory and then it asks for the given file.
 
     curl --ftp-method singlecwd ftp://example.com/one/two/three/file.txt

ftp-twoconnections.md

@@ -2,10 +2,10 @@
 
 FTP uses two TCP connections! The first connection is setup by the client when
 it connects to an FTP server, and is called the *control connection*. As the
-intial connection, it gets to handle authentication and changing to the
+initial connection, it gets to handle authentication and changing to the
 correct directory on the remote server etc. When the client then is ready to
 transfer a file, a second TCP connection is established and the data is
-transfered over that.
+transferred over that.
 
 This setting up of a second connection causes nuisances and headaches for
 several reasons.

http-basics.md

@@ -60,7 +60,7 @@ request to the server. Let's take the an example URL:
    the `Host:` header.
 
  - **/path/to/file** is used in the HTTP request to tell the server which exact
-   doucment/resources curl wants to fetch
+   document/resources curl wants to fetch
 
 ### --path-as-is
 

http-cookies.md

@@ -15,7 +15,7 @@ The expiry of a cookie is either set to a fixed time in the future (or to live
 a number of seconds) or it gets no expiry at all. A cookie without an expire
 time is called a "session cookie" and is meant to live for the duration of the
 "session" but not longer. A session in this aspect is typically thought to be
-the life time of the browser used to maneuver a site. When you close the
+the life time of the browser used to manoeuvre a site. When you close the
 browser you end your session. Doing HTTP operations with a command line client
 that supports cookies of course then begs the question when a session really
 ends...

http-post.md

@@ -139,7 +139,7 @@ to "waste" such a small chunk of data is not considered much of a problem.
 
 When talking to a HTTP 1.1 server, you can tell curl to send the request body
 without a `Content-Length:` header upfront that specifies exactly how big the
-POST is. By insisting on curl using chunked Tranfer-Encoding, curl will send
+POST is. By insisting on curl using chunked Transfer-Encoding, curl will send
 the POST "chunked" piece by piece in a special style that also sends the size
 for each such chunk as it goes along.
 

http-postvspost.md

@@ -31,8 +31,8 @@ and you do with curl's `-d` and friends.
 
 ## POST outside of HTML
 
-POST is a regular HTTP method and there's really no requirent it was
-triggrered or originated by HTML or ever involving a browser. Lots of
+POST is a regular HTTP method and there's really no requirement it was
+triggered or originated by HTML or ever involving a browser. Lots of
 services, APIs and similar these days allow you to pass in data to get things
 done.
 

http-put.md

@@ -1,7 +1,7 @@
 ## PUT
 
 The difference between a PUT and a POST is subtle. They're virtually identical
-over the wire except for the differnt method strings. Where POST is meant to
+over the wire except for the different method strings. Where POST is meant to
 pass on data to a remote resource, PUT is supposed to be the new version of
 that resource.
 

http-redirects.md

@@ -4,7 +4,7 @@ The “redirect” is a fundamental part of the HTTP protocol. The concept was
 present and is documented already in the first spec (RFC 1945), published in
 1996, and it has remained well used ever since.
 
-A redirect is exactly what it sounds like. It is the snerver sending back an
+A redirect is exactly what it sounds like. It is the server sending back an
 instruction to the client - instead of giving back the contents the client
 wanted. The server basically says “go look over *here* instead for that thing
 you asked for“.
@@ -23,7 +23,7 @@ back a 301. It also means that the user-agent (browser) is meant to cache this
 and keep going to the new URI from now on when the original URI is requested.
 
 The temporary alternative is 302. Right now the server wants the client to
-send a GET request to B, but it shouldn’t cache this but keep trying the
+send a GET request to B, but it shouldn't cache this but keep trying the
 original URI when directed to it.
 
 Note that both 301 and 302 will make browsers do a GET in the next request,
@@ -56,9 +56,9 @@ amount of redirects to follow with the `--max-redirs` option.
 ## GET or POST?
 
 All three of these response codes, 301 and 302/303, will assume that the
-client sends a GET to get the new URI, even if the client might’ve sent a POST
+client sends a GET to get the new URI, even if the client might've sent a POST
 in the first request. This is very important, at least if you do something
-that doesn’t use GET.
+that doesn't use GET.
 
 If the server instead wants to redirect the client to a new URI and wants it
 to send the same method in the second request as it did in the first, like if
@@ -102,7 +102,7 @@ control that behavior with the `CURLOPT_POSTREDIR` option.
 
 ## Redirecting to other host names
 
-When you use curl you may provide credentials like user namd and password for
+When you use curl you may provide credentials like user name and password for
 a particular site, but since a HTTP redirect might very well move away to a
 different host curl limits what it sends away to other hosts than the original
 within the same "transfer".
@@ -130,7 +130,7 @@ of these kinds of redirects.
 ## Javascript redirects
 
 The modern web is full of javascript and as you know, javascript is a
-languauge and a full run time that allows code to execute in the browser when
+language and a full run time that allows code to execute in the browser when
 visiting web sites.
 
 Javascript also provides means for it to instruct the browser to move on to

libcurl-api.md

@@ -24,7 +24,7 @@ The version numbering is always built up using the same system:
 
 ### Bumping numbers
 
-One of thes X.Y.Z numbers will get bumped in every new release. The numbers to
+One of these X.Y.Z numbers will get bumped in every new release. The numbers to
 the right of a bumped number will be reset to zero.
 
 The main version number X is bumped when *really* big, world colliding changes

libcurl-cleanup.md

@@ -19,7 +19,7 @@ transfers going on, you can close the multi handle like this:
 ### easy handle
 
 When the easy handle is done serving its purpose, you can close it. If you
-intend to do another transfer you are however adviced to rather reuse the
+intend to do another transfer you are however advised to rather reuse the
 handle for the next transfer rather than to close it and create a new one.
 
 If you don't intend to do another transfer with the easy handle, you simply

libcurl-connectionreuse.md

@@ -4,7 +4,7 @@ libcurl keeps a pool of old connections alive. When one transfer has completed
 it will keep N connections alive in a "connection pool" so that a subsequent
 transfer that happens to be able to reuse one of the existing connections can
 use that one instead of creating a new. Reusing a connection instead of
-creating a new offers significant benefits in speed and requiredresources.
+creating a new offers significant benefits in speed and required resources.
 
 ### Easy API pool
 

libcurl-drive-multi.md

@@ -16,7 +16,7 @@ A multi handle can also get certain options set in it, which you do with
 set there.
 
 To drive a multi interface transfer, you first need to add all the individual
-easy handles to the multi handle that should be transfered. You can add them
+easy handles to the multi handle that should be transferred. You can add them
 to the multi handle at any point and you can remove them again whenever you
 like.  Removing an easy handle from a multi handle will of course remove the
 association and that particular transfer would stop immediately.

libcurl-http-download.md

@@ -18,7 +18,7 @@ there's the CURLOPT_HTTPGET option:
 ### Download headers too
 
 A HTTP transfer also includes a set of response headers. Reponse headers are
-meta data associated with the actual pyload, called the response body. All
+meta data associated with the actual payload, called the response body. All
 downloads will get a set of headers too, but when using libcurl you can select
 whether you want to have them downloaded (seen) or not.
 
@@ -42,7 +42,7 @@ callbacks](callback-header.md).
     fclose(file);
 
 If you only want to casually browse the headers, you may even be happy enough
-with just setting verbose mode while developing as that will show both ougoing
+with just setting verbose mode while developing as that will show both outgoing
 and incoming headers sent to stderr:
 
     curl_easy_setopt(easy, CURLOPT_VERBOSE, 1L);

libcurlexamples.md

@@ -3,7 +3,7 @@
 The native API for libcurl is in C so this chapter is focus on examples
 written in C. But since many language bindings for libcurl are thin they
 usually expose more or less the same functions and thus they can still be
-intersting and educational for users of other languages too.
+interesting and educational for users of other languages too.
 
 ## Get a simple HTML page
 

opensource-copyright.md

@@ -22,7 +22,7 @@ follow any umbrella organization's guidelines.
 ## Legal
 
 The curl project obeys to national laws in which it works. It being a highly
-international project visible, downloadble and usable in effectively every
+international project visible, downloadable and usable in effectively every
 single country on earth may of course imply that some local laws can be
 circumvented when using curl. That's just the nature of it and if uncertain,
 you should check your own local situation.

protocols.md

@@ -4,7 +4,7 @@ Before diving in and talking about how to use curl to get things done, let's
 take a look at what all this networking is and how it works. Using
 simplifications and some minor shortcuts to give an easy overview.
 
-The basics are in the [networking simplied](protocols-network.md) chapter that
+The basics are in the [networking simplified](protocols-network.md) chapter that
 tries to just draw a simple picture of what networking is from a curl
 perspective, and the [protocols](protocols-protocols.md) section explains more
 on what exactly a "protocol" is and how that works.