Couple of typos fixed.

doc/auth_tutorial.rst

@@ -21,7 +21,7 @@ Basic Authentication
 
 Basic authentication uses the user's Twitter username and password for
 authenticating with the API. You must query the user for these two
-pieces of infomation before we can authenticate.
+pieces of information before we can authenticate.
 
 Now first we must create an instance of the BasicAuthHandler and pass
 into it the username and password::
@@ -156,7 +156,7 @@ you would do this::
    auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
    auth.set_access_token(key, secret)
 
-So now that we have our OAuthHandler equiped with an access token, we
+So now that we have our OAuthHandler equipped with an access token, we
 are ready for business::
 
    api = tweepy.API(auth)

doc/cursor_tutorial.rst

@@ -13,7 +13,7 @@ We use pagination a lot in Twitter API development. Iterating through
 timelines, user lists, direct messages, etc. In order to perform
 pagination we must supply a page/cursor parameter with each of our
 requests. The problem here is this requires a lot of boiler plate code
-just to mange the pagination loop. To help mage pagination easier and
+just to manage the pagination loop. To help make pagination easier and
 require less code Tweepy has the Cursor object.
 
 Old way vs Cursor way

doc/getting_started.rst

@@ -10,7 +10,7 @@ Introduction
 
 If you are new to Tweepy, this is the place to begin. The goal of this
 tutorial is to get you set-up and rolling with Tweepy. We won't go
-into too much details here, just some important basics.
+into too much detail here, just some important basics.
 
 Hello Tweepy
 ============
@@ -40,7 +40,7 @@ API
 
 The API class provides access to the entire twitter RESTful API
 methods. Each method can accept various parameters and return
-responses. For more infomation about these methods please refer to
+responses. For more information about these methods please refer to
 :ref:`API Reference <api_reference>`.
 
 Models

doc/parameters.rst

@@ -5,8 +5,8 @@
 .. |count| replace:: Specifies the number of statuses to retrieve.
 .. |page| replace:: Specifies the page of results to retrieve. Note: there are pagination limits.
 .. |uid| replace:: Specifies the ID or screen name of the user.
-.. |user_id| replace:: Specfies the ID of the user. Helpful for disambiguating when a valid user ID is also a valid screen name.
-.. |screen_name| replace:: Specfies the screen name of the user. Helpful for disambiguating when a valid screen name is also a user ID.
+.. |user_id| replace:: Specifies the ID of the user. Helpful for disambiguating when a valid user ID is also a valid screen name.
+.. |screen_name| replace:: Specifies the screen name of the user. Helpful for disambiguating when a valid screen name is also a user ID.
 .. |sid| replace:: The numerical ID of the status.
 .. |cursor| replace:: Breaks the results into pages. Provide a value of  -1 to begin paging. Provide values as returned to in the response body's next_cursor and previous_cursor attributes to page back and forth in the list.
 .. |exclude| replace:: Setting this equal to hashtags will remove all hashtags from the trends list.