From bcb54c43fe371e96a6445f16f0dd4e756dd6c633 Mon Sep 17 00:00:00 2001 From: Donne Martin Date: Fri, 19 Sep 2014 17:58:27 -0400 Subject: [PATCH] Fix for Typos in README.rst #344 --- README.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 143a277..80bfa75 100644 --- a/README.rst +++ b/README.rst @@ -115,7 +115,7 @@ Handling the Callback 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. @@ -134,10 +134,10 @@ Now that you have the ``oauth_verifier`` stored to a variable, you'll want to cr final_step = twitter.get_authorized_tokens(oauth_verifier) -Once you have the final user tokens, store them in a database for later use!:: +Once you have the final user tokens, store them in a database for later use:: OAUTH_TOKEN = final_step['oauth_token'] - OAUTH_TOKEN_SECERT = final_step['oauth_token_secret'] + OAUTH_TOKEN_SECRET = final_step['oauth_token_secret'] For OAuth 2 (Application Only, read-only) authentication, see `our documentation `_