do not start sentences with And

badwords.txt

@@ -23,3 +23,4 @@ internet=Internet
 isation:ization
 it's:it is
 there's:there is
+\. And: Rewrite it somehow?

http/redirects.md

@@ -67,7 +67,7 @@ server would use different response codes.
 
 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. And to complicate matters, the 308 code is only recently
+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,
 then the only response code left for you is…

internals/memory-debugging.md

@@ -13,7 +13,7 @@ allocated but never freed and other kinds of errors related to resource
 management.
 
 Internally, the definition of the preprocessor symbol `DEBUGBUILD` restricts
-code which is only compiled for debug enabled builds. And symbol `CURLDEBUG`
+code which is only compiled for debug enabled builds. The symbol `CURLDEBUG`
 is used to differentiate code which is _only_ used for memory
 tracking/debugging.
 

libcurl-http/requests.md

@@ -5,7 +5,7 @@ to do. When it wants to get data or send data. All transfers involving HTTP
 start with an HTTP request.
 
 An HTTP request contains a method, a path, HTTP version and a set of request
-headers. And of course a libcurl using application can tweak all those fields.
+headers. A libcurl-using application can tweak all those fields.
 
 ## Request method
 

libcurl/url/get-part.md

@@ -79,5 +79,4 @@ For this URL, curl extracts:
 | `eth0`               | `CURLUPART_ZONEID` |
 | `/`                  | `CURLUPART_PATH`   |
 
-... and asking for any other component will then return non-zero as they are
-missing.
+Asking for any other component will return non-zero as they are missing.

usingcurl/copyas.md

@@ -34,6 +34,6 @@ If this is something you would like to get done more often, you probably find us
 
 These methods all give you a command line to reproduce their HTTP transfers. You will also learn they are still often not the perfect solution to your problems. Why? Well mostly because these tools are written to rerun the _exact_ same request that you copied, while you often want to rerun the same logic but not sending an exact copy of the same cookies and file contents etc.
 
-These tools will give you command lines with static and fixed cookie contents to send in the request, because that is the contents of the cookies that were sent in the browser's requests. You will most likely want to rewrite the command line to dynamically adapt to whatever the content is in the cookie that the server told you in a previous response. And so on.
+These tools will give you command lines with static and fixed cookie contents to send in the request, because that is the contents of the cookies that were sent in the browser's requests. You will most likely want to rewrite the command line to dynamically adapt to whatever the content is in the cookie that the server told you in a previous response. Etc.
 
 The copy as curl functionality is also often notoriously bad at using `-F` and instead they provide handcrafted `--data-binary` solutions including the mime separator strings etc.

usingcurl/scpsftp.md

@@ -79,8 +79,8 @@ host that it thinks it is communicating with. With TLS based protocols, it is
 done by the client verifying the server's certificate.
 
 With SSH protocols there are no server certificates, but instead each server
-can provide its unique key. And unlike TLS, SSH has no certificate authorities
-or anything so the client simply has to make sure that the host's key matches
+can provide its unique key. Unlike TLS, SSH has no certificate authorities or
+anything so the client simply has to make sure that the host's key matches
 what it already knows (via other means) it should look like.
 
 The matching of keys is typically done using hashes of the key and the file

usingcurl/tls/stapling.md

@@ -6,8 +6,7 @@ certificate that it returns is still valid. This is a way to make really sure
 the server's certificate has not been revoked.
 
 If the server does not support this extension, the test will fail and curl
-returns an error. And it is still far too common that servers do not support
-this.
+returns an error. It is still common that servers do not support this.
 
 Ask for the handshake to use the status request like this:
 

usingcurl/transfers/rate-limiting.md

@@ -4,9 +4,9 @@ When curl transfers data, it will attempt to do that as fast as possible. It
 goes for both uploads and downloads. Exactly how fast that will be depends on
 several factors, including your computer's ability, your own network
 connection's bandwidth, the load on the remote server you are transferring
-to/from and the latency to that server. And your curl transfers are also
-likely to compete with other transfers on the networks the data travels
-over, from other users or just other apps by the same user.
+to/from and the latency to that server. Your curl transfers are also likely to
+compete with other transfers on the networks the data travels over, from other
+users or just other apps by the same user.
 
 In many setups, however, you will find that you can more or less saturate your
 own network connection with a single curl command line. If you have a 10