From b5aa9a85774375ba982d5ec07ae8f781f859c7c2 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 10 Jan 2024 10:48:18 +0100 Subject: [PATCH] reduce/remove exclamation mark use --- GUIDELINES.md | 2 +- README.md | 2 +- build.md | 2 +- cmdline/globbing.md | 2 +- cmdline/urls/query.md | 2 +- ftp/cmds.md | 2 +- ftp/dirlist.md | 2 +- ftp/twoconnections.md | 2 +- get/win-msys2.md | 2 +- http/cookies.md | 2 +- http/modify/referer.md | 2 +- http/post/url-encode.md | 2 +- http/redirects.md | 2 +- internals/structs.md | 2 +- internals/tests/file-format.md | 2 +- libcurl-http/auth.md | 2 +- libcurl/callbacks/header.md | 2 +- libcurl/callbacks/seek.md | 2 +- libcurl/conn/reuse.md | 2 +- libcurl/examples/ftplist.md | 2 +- libcurl/examples/getinmem.md | 2 +- libcurl/examples/login.md | 2 +- libcurl/getinfo.md | 2 +- project/bugs.md | 4 ++-- project/etiquette.md | 10 +++++----- source/layout.md | 2 +- usingcurl/connections/name.md | 4 ++-- usingcurl/downloads/max-filesize.md | 2 +- usingcurl/downloads/storing.md | 2 +- usingcurl/proxies/http.md | 2 +- usingcurl/timeouts.md | 2 +- usingcurl/tls/sslkeylogfile.md | 2 +- usingcurl/verbose.md | 6 +++--- usingcurl/version.md | 2 +- 34 files changed, 42 insertions(+), 42 deletions(-) diff --git a/GUIDELINES.md b/GUIDELINES.md index 80b1cb32fe..5d694742cd 100644 --- a/GUIDELINES.md +++ b/GUIDELINES.md @@ -20,7 +20,7 @@ Spell them out as "it will" and "must have", etc. And ... vs … (typographical ellipses) -Let's try to use the correct UTF-8 characters! +Try to use the correct UTF-8 characters. ## Avoid the short forms of dir and repo diff --git a/README.md b/README.md index 2833aaf6a0..18002065e3 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ All there is to know about Daniel can be found on [daniel.haxx.se](https://danie If you find mistakes, omissions, errors or blatant lies in this document, please send us a refreshed version of the affected paragraph and we will amend -and update. We give credit to and recognize everyone who helps out! +and update. We give credit to and recognize everyone who helps out. Preferably, you could submit [errors](https://github.com/bagder/everything-curl/issues) or [pull diff --git a/build.md b/build.md index 179601f129..a1e1693e8e 100644 --- a/build.md +++ b/build.md @@ -48,7 +48,7 @@ yourself, chances are that building curl from source is the easiest or perhaps the only way to get curl. Making it easy to build curl is a priority to the curl project, although we do -not always necessarily succeed! +not always necessarily succeed. ## git vs release tarballs diff --git a/cmdline/globbing.md b/cmdline/globbing.md index b5045ddde4..73b6d277a8 100644 --- a/cmdline/globbing.md +++ b/cmdline/globbing.md @@ -16,7 +16,7 @@ interfering with it. This also goes for other characters treated special, like for example '&', '?' and '*'. While most transfer related functionality in curl is provided by the libcurl -library, the URL globbing feature is not! +library, the URL globbing feature is not. ## Numerical ranges diff --git a/cmdline/urls/query.md b/cmdline/urls/query.md index 8650859ef9..b79b77022e 100644 --- a/cmdline/urls/query.md +++ b/cmdline/urls/query.md @@ -20,7 +20,7 @@ the `+` prefix. See below. - `content`: URL encode the content and add that to the query. Just be careful so that the content does not contain any `=` or `@` symbols, as - that makes the syntax match one of the other cases below! + that makes the syntax match one of the other cases below. - `=content`: URL encode the content and add that to the query. The initial `=` symbol is not included in the data. diff --git a/ftp/cmds.md b/ftp/cmds.md index cd23b4f865..ad369119c9 100644 --- a/ftp/cmds.md +++ b/ftp/cmds.md @@ -19,7 +19,7 @@ To know what commands that are available and possible to send to a server, you need to know a little about the FTP protocol, and possibly read up a bit on RFC 959 on the details. -To send a simple `NOOP` to the server (which does nothing!) **before** the +To send a simple `NOOP` to the server (which does nothing) **before** the transfer starts, provide it to curl like this: curl -Q NOOP ftp://example.com/file diff --git a/ftp/dirlist.md b/ftp/dirlist.md index 043cb55dd8..2389ffc984 100644 --- a/ftp/dirlist.md +++ b/ftp/dirlist.md @@ -19,5 +19,5 @@ the special formatting of the regular directory listings is to tell curl to curl --list-only ftp://ftp.example.com/directory/ NLST has its own quirks though, as some FTP servers list only actual *files* -in their response to NLST; they do not include directories and symbolic links! +in their response to NLST; they do not include directories and symbolic links. diff --git a/ftp/twoconnections.md b/ftp/twoconnections.md index 5a29c73752..bcd296c7bf 100644 --- a/ftp/twoconnections.md +++ b/ftp/twoconnections.md @@ -1,6 +1,6 @@ # Two connections -FTP uses two TCP connections! The first connection is setup by the client when +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 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 diff --git a/get/win-msys2.md b/get/win-msys2.md index 443a1b5e36..02469003f1 100644 --- a/get/win-msys2.md +++ b/get/win-msys2.md @@ -64,6 +64,6 @@ Use the `pacman -u` command to install such a local package file: Have a look at the [msys2 docs](https://www.msys2.org/docs/package-management/) or join the [gitter](https://gitter.im/msys2/msys2) to learn more about building with -pacman and msys2! +pacman and msys2. \[^1]: Be careful not to confuse the [mingw-package](https://github.com/msys2/MINGW-packages) `mingw-w64-curl` with the [msys-packages](https://github.com/msys2/MSYS2-packages) `curl` and `curl-devel`. The latter are part of msys2 environment itself (e.g. to support pacman downloads), but not suitable for redistribution. To build redistributable software that does not depend on MSYS2 itself, you always need `mingw-w64-…` packages and toolchains. diff --git a/http/cookies.md b/http/cookies.md index aee750ff33..16313c686c 100644 --- a/http/cookies.md +++ b/http/cookies.md @@ -44,7 +44,7 @@ Starting off with a blank cookie store may not be desirable. Why not start off with cookies you stored in a previous fetch or that you otherwise acquired? 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! +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 is an inferior format but may be the only thing you have. diff --git a/http/modify/referer.md b/http/modify/referer.md index e44c474d1f..91770dd0e4 100644 --- a/http/modify/referer.md +++ b/http/modify/referer.md @@ -3,7 +3,7 @@ When a user clicks on a link on a webpage and the browser takes the user away to the next URL, it sends the new URL a `Referer:` header in the new request telling it where it came from. That is the referer header. The `Referer:` is -misspelled but that is how it is supposed to be! +misspelled but that is how it is supposed to be. With curl you set the referer header with `-e` or `--referer`, like this: diff --git a/http/post/url-encode.md b/http/post/url-encode.md index 6c8a92493c..db8580add4 100644 --- a/http/post/url-encode.md +++ b/http/post/url-encode.md @@ -20,7 +20,7 @@ passed to curl using one of the following syntaxes: - `content`: URL encode the content and pass that on. Just be careful so that the content does not contain any `=` or `@` symbols, as that then makes the - syntax match one of the other cases below! + syntax match one of the other cases below. - `=content`: URL encode the content and pass that on. The initial `=` symbol is not included in the data. diff --git a/http/redirects.md b/http/redirects.md index 676000df94..d94efa1b8b 100644 --- a/http/redirects.md +++ b/http/redirects.md @@ -69,7 +69,7 @@ To tell the client “the URI you sent a POST to, is permanently redirected to B where you should instead send your POST now and in the future”, the server responds with a 308. To complicate matters, the 308 code is only recently defined (the [spec](https://tools.ietf.org/html/rfc7238#section-3) was -published in June 2014) so older clients may not treat it correctly! If so, +published in June 2014) so older clients may not treat it correctly. If so, then the only response code left for you is… The (older) response code to tell a client to send a POST also in the next diff --git a/internals/structs.md b/internals/structs.md index 57c07577df..e1cde5967b 100644 --- a/internals/structs.md +++ b/internals/structs.md @@ -35,7 +35,7 @@ times. When doing multiplexed HTTP/2 transfers, each `Curl_easy` is associated with an individual stream, sharing the same connectdata struct. Multiplexing - makes it even more important to keep things associated with the right thing! + makes it even more important to keep things associated with the right thing. ## connectdata diff --git a/internals/tests/file-format.md b/internals/tests/file-format.md index 75cc13a868..0585bcdb20 100644 --- a/internals/tests/file-format.md +++ b/internals/tests/file-format.md @@ -523,7 +523,7 @@ If there is no test number found above, the HTTP test server uses the number following the last dot in the given hostname (made so that a CONNECT can still pass on test number) so that "foo.bar.123" gets treated as test case 123. Alternatively, if an IPv6 address is provided to CONNECT, the last -hexadecimal group in the address is used as the test number! For example the +hexadecimal group in the address is used as the test number. For example the address "[1234::ff]" would be treated as test case 255. Set `type="perl"` to write the test case as a perl script. It implies that diff --git a/libcurl-http/auth.md b/libcurl-http/auth.md index eee0a8d46d..092164990a 100644 --- a/libcurl-http/auth.md +++ b/libcurl-http/auth.md @@ -99,7 +99,7 @@ Some HTTP servers allow one out of several authentication methods, in some cases you find yourself in a position where you as a client does not want or is not able to select a single specific method before-hand and for yet another subset of cases your application does not know if the requested URL even -require authentication or not! +require authentication or not. libcurl covers all these situations as well. diff --git a/libcurl/callbacks/header.md b/libcurl/callbacks/header.md index d713784916..2862a4f431 100644 --- a/libcurl/callbacks/header.md +++ b/libcurl/callbacks/header.md @@ -13,7 +13,7 @@ received. *ptr* points to the delivered data, and the size of that data is *size* multiplied with *nmemb*. libcurl buffers headers and delivers only "full" headers, one by one, to this callback. -The data passed to this function is not be zero terminated! You cannot, for +The data passed to this function is not be zero terminated. You cannot, for example, use printf's `%s` operator to display the contents nor strcpy to copy it. diff --git a/libcurl/callbacks/seek.md b/libcurl/callbacks/seek.md index 77afa83ac0..b685af5a3e 100644 --- a/libcurl/callbacks/seek.md +++ b/libcurl/callbacks/seek.md @@ -23,4 +23,4 @@ by instead reading from the input or similar. If you forward the input arguments directly to fseek(3) or lseek(3), note that the data type for offset is not the same as defined for `curl_off_t` on many -systems! +systems. diff --git a/libcurl/conn/reuse.md b/libcurl/conn/reuse.md index 5f84ad193a..ecef63fa58 100644 --- a/libcurl/conn/reuse.md +++ b/libcurl/conn/reuse.md @@ -27,7 +27,7 @@ When you are using the multi API, the connection pool is instead kept associated with the multi handle. This allows you to cleanup and re-create easy handles freely without risking losing the connection pool, and it allows the connection used by one easy handle to get reused by a separate one in a -later transfer. Just reuse the multi handle! +later transfer. Just reuse the multi handle. ## Sharing the "connection cache" diff --git a/libcurl/examples/ftplist.md b/libcurl/examples/ftplist.md index 50810cec2f..97130089c0 100644 --- a/libcurl/examples/ftplist.md +++ b/libcurl/examples/ftplist.md @@ -16,7 +16,7 @@ it as a directory. curl = curl_easy_init(); if(curl) { /* - * Make the URL end with a trailing slash! + * Make the URL end with a trailing slash */ curl_easy_setopt(curl, CURLOPT_URL, "ftp://ftp.example.com/"); diff --git a/libcurl/examples/getinmem.md b/libcurl/examples/getinmem.md index 4cc4640d4a..3718e13ce4 100644 --- a/libcurl/examples/getinmem.md +++ b/libcurl/examples/getinmem.md @@ -84,7 +84,7 @@ from that instead. * Now, our chunk.memory points to a memory block that is chunk.size * bytes big and contains the remote file. * - * Do something nice with it! + * Do something nice with it */ printf("%lu bytes retrieved\n", (long)chunk.size); diff --git a/libcurl/examples/login.md b/libcurl/examples/login.md index 4d858289e6..2d995545dc 100644 --- a/libcurl/examples/login.md +++ b/libcurl/examples/login.md @@ -31,7 +31,7 @@ and prove to the server that we are in fact correctly logged in. if(curl) { curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/login.cgi"); curl_easy_setopt(curl, CURLOPT_POSTFIELDS, postthis); - curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L); /* redirects! */ + curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L); /* redirects */ curl_easy_setopt(curl, CURLOPT_COOKIEFILE, ""); /* no file */ res = curl_easy_perform(curl); /* Check for errors */ diff --git a/libcurl/getinfo.md b/libcurl/getinfo.md index 2feb8df626..eb13ff1bb1 100644 --- a/libcurl/getinfo.md +++ b/libcurl/getinfo.md @@ -1,6 +1,6 @@ # Post transfer info -Remember how libcurl transfers are associated with an "easy handle"! Each +Remember how libcurl transfers are associated with *easy handles*. Each transfer has such a handle and when a transfer is completed, before the handle is cleaned or reused for another transfer, it can be used to extract information from the previous operation. diff --git a/project/bugs.md b/project/bugs.md index 55626fa478..7546ad45af 100644 --- a/project/bugs.md +++ b/project/bugs.md @@ -44,10 +44,10 @@ can narrow down the "suspects" and make sure your problem is properly located. A bug report that is submitted then abandoned by the submitter risks getting closed if the developer fails to understand it, fails to reproduce it or faces -other problems when working on it. Do not abandon your report! +other problems when working on it. Do not abandon your report. Report curl bugs in the [curl bug tracker on -GitHub](https://github.com/curl/curl/issues)! +GitHub](https://github.com/curl/curl/issues). ## Testing diff --git a/project/etiquette.md b/project/etiquette.md index 5ba3c459f4..b0f0619087 100644 --- a/project/etiquette.md +++ b/project/etiquette.md @@ -101,11 +101,11 @@ Many people mail questions to the list, people spend some of their time and make an effort in providing good answers to these questions. If you are the one who asks, please consider responding once more in case one -of the hints was what solved your problems. Those who write answers feel -good to know that they provided a good answer and that you fixed the -problem. Far too often, the person who asked the question is never heard of -again, and we never get to know if he/she is gone because the problem was -solved or perhaps because the problem was unsolvable! +of the hints was what solved your problems. Those who write answers feel good +to know that they provided a good answer and that you fixed the problem. Far +too often, the person who asked the question is never heard of again, and we +never get to know if he/she is gone because the problem was solved or perhaps +because the problem was unsolvable. Getting the solution posted also helps other users that experience the same problem(s). They get to see (possibly in the web archives) that the suggested diff --git a/source/layout.md b/source/layout.md index 1d46192520..c791d4533a 100644 --- a/source/layout.md +++ b/source/layout.md @@ -127,7 +127,7 @@ converted from text to a web friendly format/look. - `SECURITY`: how we work on security vulnerabilities - `SSLCERTS`: TLS certificate handling documented - `SSL-PROBLEMS`: common SSL problems and their causes -- `THANKS`: thanks to this extensive list of friendly people, curl exists today! +- `THANKS`: thanks to this extensive list of friendly people, curl exists today. - `TheArtOfHttpScripting`: a tutorial into HTTP scripting with curl - `TODO`: things we or you can work on implementing - `VERSIONS`: how the version numbering of libcurl works diff --git a/usingcurl/connections/name.md b/usingcurl/connections/name.md index bf56188bae..faf6ae0ac1 100644 --- a/usingcurl/connections/name.md +++ b/usingcurl/connections/name.md @@ -40,8 +40,8 @@ given URL. ## Provide a custom IP address for a name Do you know better than the name resolver where curl should go? Then you can -give an IP address to curl yourself! If you want to redirect port 80 access for -`example.com` to instead reach your localhost: +give an IP address to curl yourself. If you want to redirect port 80 access +for `example.com` to instead reach your localhost: curl --resolve example.com:80:127.0.0.1 http://example.com/ diff --git a/usingcurl/downloads/max-filesize.md b/usingcurl/downloads/max-filesize.md index 136ad79b91..4a63a3cd79 100644 --- a/usingcurl/downloads/max-filesize.md +++ b/usingcurl/downloads/max-filesize.md @@ -2,7 +2,7 @@ When you want to make sure your curl command line does not download a too-large file, instruct curl to stop before doing that, if it knows the size -before the transfer starts! Maybe that would use too much bandwidth, take too +before the transfer starts. Maybe that would use too much bandwidth, take too long time or you do not have enough space on your hard drive: curl --max-filesize 100000 https://example.com/ diff --git a/usingcurl/downloads/storing.md b/usingcurl/downloads/storing.md index b5ca9de327..7599589047 100644 --- a/usingcurl/downloads/storing.md +++ b/usingcurl/downloads/storing.md @@ -63,4 +63,4 @@ up to the user to decide what to do with the leftovers. The `--remove-on-error` command line option changes this behavior. It tells curl to delete any partially saved file if curl exits with an error. No more -leftovers! +leftovers. diff --git a/usingcurl/proxies/http.md b/usingcurl/proxies/http.md index 0a312b604c..47d4f622e4 100644 --- a/usingcurl/proxies/http.md +++ b/usingcurl/proxies/http.md @@ -48,7 +48,7 @@ not work: curl -x http://proxy.example.com:80 ftp://ftp.example.com/file.txt -What you can do instead then, is to "tunnel through" the HTTP proxy! +What you can do instead then, is to "tunnel through" the HTTP proxy. ## HTTP proxy tunneling diff --git a/usingcurl/timeouts.md b/usingcurl/timeouts.md index 52a041861e..c78fec820d 100644 --- a/usingcurl/timeouts.md +++ b/usingcurl/timeouts.md @@ -10,7 +10,7 @@ an extended period of time without it necessarily getting noticed by the participants in the transfer. The result of this is that sometimes Internet transfers take a long -time. Further, most operations in curl have no time-out by default! +time. Further, most operations in curl have no time-out by default. ## Maximum time allowed to spend diff --git a/usingcurl/tls/sslkeylogfile.md b/usingcurl/tls/sslkeylogfile.md index c128a8800a..df79b72f60 100644 --- a/usingcurl/tls/sslkeylogfile.md +++ b/usingcurl/tls/sslkeylogfile.md @@ -17,7 +17,7 @@ Having done this simple operation, you can now inspect curl's or your browser's Just remember that if you record TLS traffic and want to save it for analyzing later, you need to also save the file with the secrets so that you can decrypt that traffic capture at a later time as well. -## libcurl-using applications too! +## libcurl-using applications too Support for `SSLKEYLOGFILE` is provided by libcurl itself - making it possible for you to trace and inspect the TLS network data for any application built to use libcurl - not just the curl command line tool. diff --git a/usingcurl/verbose.md b/usingcurl/verbose.md index aeba14a43e..cd75c78bf1 100644 --- a/usingcurl/verbose.md +++ b/usingcurl/verbose.md @@ -23,12 +23,12 @@ This tells us curl now tries to connect to this IP address. It means the name * Connected to example.com (93.184.216.34) port 80 (#0) -It worked! curl connected to the site and here it explains how the name maps +It worked. curl connected to the site and here it explains how the name maps to the IP address and on which port it has connected to. The '(#0)' part is which internal number curl has given this connection. If you try multiple URLs in the same command line you can see it use more connections or reuse -connections, so the connection counter may increase or not increase -depending on what curl decides it needs to do. +connections, so the connection counter may increase or not increase depending +on what curl decides it needs to do. If we use an `HTTPS://` URL instead of an HTTP one, there are also a whole bunch of lines explaining how curl uses CA certs to verify the server's diff --git a/usingcurl/version.md b/usingcurl/version.md index 13b3d28c15..859c2c22a3 100644 --- a/usingcurl/version.md +++ b/usingcurl/version.md @@ -90,7 +90,7 @@ Features that can be present there: - **CharConv** - curl was built with support for character set conversions (like EBCDIC) - **Debug** - This curl uses a libcurl built with Debug. This enables more - error-tracking and memory debugging etc. For curl-developers only! + error-tracking and memory debugging etc. For curl-developers only. - **GSS-API** - GSS-API authentication is enabled - **HTTP2** - HTTP/2 support has been built-in. - **HTTP3** - HTTP/3 support has been built-in.