docs: Fix a few typos

There are small typos in:
- docs/usage/advanced_usage.rst
- docs/usage/basic_usage.rst
- docs/usage/special_functions.rst
- docs/usage/starting_out.rst
- tests/test_endpoints.py
- twython/endpoints.py
- twython/streaming/api.py

Fixes:
- Should read `received` rather than `recieved`.
- Should read `paginated` rather than `pagintated`.
- Should read `multiple` rather than `mutiple`.
- Should read `membership` rather than `memberhips`.
- Should read `manipulate` rather than `maninpulate`.
- Should read `explicitly` rather than `explicity`.
- Should read `destroy` rather than `destory`.
- Should read `authentication` rather than `autentication`.
- Should read `actual` rather than `acutal`.

Signed-off-by: Tim Gates <tim.gates@iress.com>

docs/usage/advanced_usage.rst

@@ -104,7 +104,7 @@ Manipulate the Request (headers, proxies, etc.)
 
 There are times when you may want to turn SSL verification off, send custom headers, or add proxies for the request to go through.
 
-Twython uses the `requests <http://python-requests.org>`_ library to make API calls to Twitter. ``requests`` accepts a few parameters to allow developers to manipulate the acutal HTTP request.
+Twython uses the `requests <http://python-requests.org>`_ library to make API calls to Twitter. ``requests`` accepts a few parameters to allow developers to manipulate the actual HTTP request.
 
 Here is an example of sending custom headers to a Twitter API request:
 

docs/usage/basic_usage.rst

@@ -80,7 +80,7 @@ Documentation: https://developer.twitter.com/en/docs/tweets/search/api-reference
 
 .. _dynamicargexplaination:
 
-.. important:: To help explain :ref:`dynamic function arguments <dynamicfunctionarguments>` a little more, you can see that the previous call used the keyword argument ``q``, that is because Twitter specifies in their `search documentation <https://developer.twitter.com/en/docs/tweets/search/api-reference/get-search-tweets>`_ that the search call accepts the parameter "q". You can pass mutiple keyword arguments. The search documentation also specifies that the call accepts the parameter "result_type"
+.. important:: To help explain :ref:`dynamic function arguments <dynamicfunctionarguments>` a little more, you can see that the previous call used the keyword argument ``q``, that is because Twitter specifies in their `search documentation <https://developer.twitter.com/en/docs/tweets/search/api-reference/get-search-tweets>`_ that the search call accepts the parameter "q". You can pass multiple keyword arguments. The search documentation also specifies that the call accepts the parameter "result_type"
 
 .. code-block:: python
 

docs/usage/special_functions.rst

@@ -10,7 +10,7 @@ This section covers methods to are part of Twython but not necessarily connected
 Cursor
 ------
 
-This function returns a generator for Twitter API endpoints that are able to be pagintated in some way (either by cursor or since_id parameter)
+This function returns a generator for Twitter API endpoints that are able to be paginated in some way (either by cursor or since_id parameter)
 
 The Old Way
 ^^^^^^^^^^^
@@ -91,7 +91,7 @@ will be replaced with:
 
     <a href="http://t.co/FCmXyI6VHd" class="twython-url">google.com</a> is <a href="https://twitter.com/search?q=%23cool" class="twython-hashtag">#cool</a>, lol! <a href="https://twitter.com/mikehelmick" class="twython-mention">@mikehelmick</a> shd <a href="https://twitter.com/search?q=%23checkitout" class="twython-hashtag">#checkitout</a>. Love, <a href="https://twitter.com/__twython__" class="twython-mention">@__twython__</a> <a href="https://twitter.com/?q=%24IBM" class="twython-symbol">$IBM</a> <a href="https://t.co/67pwRvY6z9" class="twython-url">github.com</a> <a href="http://t.co/N6InAO4B71" class="twython-media">pic.twitter.com/N6InAO4B71</a>
 
-.. note:: When converting the string to HTML we add a class to each HTML tag so that you can maninpulate the DOM later on.
+.. note:: When converting the string to HTML we add a class to each HTML tag so that you can manipulate the DOM later on.
 
 - For urls that are replaced we add ``class="twython-url"`` to the anchor tag
 - For media urls that are replaced we add ``class="twython-media"`` to the anchor tag

docs/usage/starting_out.rst

@@ -74,7 +74,7 @@ Handling the Callback
 
 .. note:: If your application is a Desktop or Mobile Application *oauth_verifier* will be the PIN code
 
-After they authorize your application to access some of their account details, they'll be redirected to the callback url you specified in ``get_autentication_tokens``
+After they authorize your application to access some of their account details, they'll be redirected to the callback url you specified in ``get_authentication_tokens``
 
 You'll want to extract the ``oauth_verifier`` from the url.