do not start sentences with "So "

badwords.txt

@@ -25,3 +25,4 @@ it's:it is
 there's:there is
 \. And: Rewrite it somehow?
 file name :filename
+\. So : Rewrite without "so" ?

cmdline/configfile.md

@@ -62,8 +62,8 @@ 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
-everything that is not an option is assumed to be a URL. So you provide a URL
-for curl like this:
+everything that is not an option is assumed to be a URL. You provide a URL for
+curl like this:
 
     url = "http://example.com"
 

libcurl-http/requests.md

@@ -103,8 +103,8 @@ with no contents on the right side of the colon, it will be treated as a
 removal instruction and it will instead completely inhibit that header from
 being sent. If you instead *truly* want to send a header with zero contents on
 the right side, you need to use a special marker. You must provide the header
-with a semicolon instead of a proper colon. Like `Header;`. So if you want to
-add a header to the outgoing HTTP request that is just `Moo:` with nothing
+with a semicolon instead of a proper colon. Like `Header;`. If you want to add
+a header to the outgoing HTTP request that is just `Moo:` with nothing
 following the colon, you could write it like:
 
     struct curl_slist *list = NULL;

libcurl/drive/multi-socket.md

@@ -41,13 +41,13 @@ completed.
 ## multi_socket callbacks
 
 As explained above, this event-based mechanism relies on the application to
-know which sockets are used by libcurl and what libcurl waits for on
-those sockets: if it waits for the socket to become readable, writable or
-both!
+know which sockets that are used by libcurl and what activities libcurl waits
+for on those sockets: if it waits for the socket to become readable, writable
+or both.
 
-It also needs to tell libcurl when its timeout time has expired, as it is
-control of driving everything libcurl cannot do it itself. So libcurl must tell
-the application an updated timeout value, too.
+The application also needs to tell libcurl when the timeout time has expired,
+as it is control of driving everything libcurl cannot do it itself. libcurl
+informs the application updated timeout values as soon as it needs to.
 
 ### socket_callback
 

libcurl/options/num.md

@@ -2,11 +2,11 @@
 
 Since `curl_easy_setopt()` is a vararg function where the 3rd argument can use
 different types depending on the situation, normal C language type conversion
-cannot be done. So you **must** make sure that you truly pass a `long` and not
-an `int` if the documentation tells you so. On architectures where they are
-the same size, you may not get any problems but not all work like
-that. Similarly, for options that accept a `curl_off_t` type, it is
-**crucial** that you pass in an argument using that type and no other.
+cannot be done. You **must** make sure that you truly pass a `long` and not an
+`int` if the documentation tells you so. On architectures where they are the
+same size, you may not get any problems but not all work like that. Similarly,
+for options that accept a `curl_off_t` type, it is **crucial** that you pass
+in an argument using that type and no other.
 
 Enforce a `long`:
 

libcurl/proxies.md

@@ -80,7 +80,7 @@ specially named environment variables before it performs its transfer to see
 if a proxy is requested to get used.
 
 You can specify the proxy by setting a variable named `[scheme]_proxy` to hold
-the proxy host name (the same way you would specify the host with `-x`). So if
+the proxy host name (the same way you would specify the host with `-x`). If
 you want to tell curl to use a proxy when accessing an HTTP server, you set
 the `http_proxy` environment variable. Like this:
 

project/name.md

@@ -2,8 +2,10 @@
 
 Naming things is hard.
 
-The tool was about uploading and downloading data specified with a URL. It was a client-side
-program (the 'c'), a URL client, and would show the data (by default). So 'c' for Client and URL: **cURL**.
+The tool was about uploading and downloading data specified with a URL. It was
+a client-side program (the 'c'), a URL client, and would show the data (by
+default). 'c' stands for Client and URL: **cURL**. The fact that it could also
+be read as "see URL" helped.
 
 Nothing more was needed so the name was selected and we never looked back
 again.

usingcurl/downloads/url-named.md

@@ -2,7 +2,7 @@
 
 Many URLs, however, already contain the filename part in the rightmost
 end. curl lets you use that as a shortcut so you do not have to repeat it with
-`-o`. So instead of:
+`-o`. Instead of:
 
     curl -o file.html http://example.com/file.html
 

usingcurl/proxies/env.md

@@ -4,7 +4,7 @@ curl checks for the existence of specially named environment variables before
 it runs to see if a proxy is requested to get used.
 
 You specify the proxy by setting a variable named `[scheme]_proxy` to hold the
-proxy host name (the same way you would specify the host with `-x`). So if you
+proxy host name (the same way you would specify the host with `-x`). If you
 want to tell curl to use a proxy when access an HTTP server, you set the
 `http_proxy` environment variable. Like this:
 

usingcurl/verbose.md

@@ -102,7 +102,7 @@ exact file length (it will not always be present in responses).
 ## HTTP/2 and HTTP/3
 
 When doing file transfers using version two or three of the HTTP protocol,
-curl sends and receives **compressed** headers. So to display outgoing and
+curl sends and receives **compressed** headers. To display outgoing and
 incoming HTTP/2 and HTTP/3 headers in a readable and understandable way, curl
 will actually show the uncompressed versions in a style similar to how they
 appear with HTTP/1.1.