tidy-up: one comment and EOF newlines

Reviewed-by: Daniel Stenberg
Closes #13108

docs/CLIENT-WRITERS.md

@@ -115,4 +115,3 @@ That is why transfer decoding writers are added for phase `CURL_CW_TRANSFER_DECO
 By adding the common behavior of all protocols into `Curl_client_write()` we make sure that they do apply everywhere. Protocol handler have less to worry about. Changes to default behavior can be done without affecting handler implementations.
 
 Having a writer chain as implementation allows protocol handlers with extra needs, like HTTP, to add to this for special behavior. The common way of writing the actual response data stays the same.
-

docs/CONNECTION-FILTERS.md

@@ -300,4 +300,3 @@ conn[curl.se] --> HTTPS-CONNECT --> NULL
 conn[curl.se] --> HTTPS-CONNECT --> SETUP[QUIC] --> HAPPY-EYEBALLS --> HTTP/3[151.101.1.91]:443
 * transfer
 ```
-

docs/libcurl/opts/CURLOPT_SEEKDATA.md

@@ -68,4 +68,3 @@ int main(void)
 Added in 7.18.0
 
 # RETURN VALUE
-

lib/vtls/mbedtls_threadlock.h

@@ -43,7 +43,7 @@ int Curl_mbedtlsthreadlock_unlock_function(int n);
 #define Curl_mbedtlsthreadlock_lock_function(x) 1
 #define Curl_mbedtlsthreadlock_unlock_function(x) 1
 
-#endif /* USE_THREADS_POSIX || USE_THREADS_WIN32 */
+#endif /* (USE_THREADS_POSIX && HAVE_PTHREAD_H) || _WIN32 */
 
 #endif /* USE_MBEDTLS */
 

scripts/nroff2cd

@@ -190,4 +190,3 @@ HEAD
 }
 
 exit single($ARGV[0]);
-