📝 Add proper header in README.md (#44)

README.md

@@ -1,4 +1,6 @@
-# Niquests
+<div align="center">
+    <img src="https://user-images.githubusercontent.com/9326700/282852138-160f32e9-e6cf-495f-b39d-99891602acf9.png" alt="Niquests Logo"/>
+</div>
 
 **Niquests** is a simple, yet elegant, HTTP library. It is a drop-in replacement for **Requests** that is no longer under
 feature freeze.
@@ -77,4 +79,4 @@ We intend to keep it that way. As long as we can, long live Niquests!
 
 ---
 
-[![Kenneth Reitz](https://raw.githubusercontent.com/jawah/niquests/main/ext/kr.png)](https://kennethreitz.org) [![Python Software Foundation](https://raw.githubusercontent.com/psf/requests/main/ext/psf.png)](https://www.python.org/psf)
+[![Kenneth Reitz](https://raw.githubusercontent.com/jawah/niquests/main/ext/kr.png)](https://kennethreitz.org)

docs/user/advanced.rst

@@ -286,6 +286,12 @@ You may specify the private key passphrase using the following example::
     >>> niquests.get('https://kennethreitz.org', cert=('/path/client.cert', '/path/client.key', 'my_key_password'))
     <Response HTTP/2 [200]>
 
+In-memory Certificates
+----------------------
+
+The ``cert=...`` and ``verify=...`` can actually take the certificates themselves. Niquests support
+in-memory certificates instead of file paths.
+
 .. _ca-certificates:
 
 CA Certificates

docs/user/authentication.rst

@@ -37,7 +37,7 @@ netrc Authentication
 ~~~~~~~~~~~~~~~~~~~~
 
 If no authentication method is given with the ``auth`` argument and the
-Authorization header has not been set, Requests will attempt to get the
+Authorization header has not been set, Niquests will attempt to get the
 authentication credentials for the URL's hostname from the user's netrc file.
 
 If credentials for the hostname are found, the request is sent with HTTP Basic