From d913145f5785ec9cdf6a3582bd06407ef47cce84 Mon Sep 17 00:00:00 2001 From: mdxs Date: Mon, 15 Sep 2014 09:55:33 +0200 Subject: [PATCH] Small documentation fix --- docs/client.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/client.rst b/docs/client.rst index 655eacf2..bb459f13 100644 --- a/docs/client.rst +++ b/docs/client.rst @@ -108,7 +108,7 @@ redirected back to. For example:: return twitter.authorize(callback=url_for('oauth_authorized', next=request.args.get('next') or request.referrer or None)) -If the application redirects back, the remote application will can fetch +If the application redirects back, the remote application can fetch all relevant information in the `oauth_authorized` function with :meth:`~OAuthRemoteApp.authorized_response`:: @@ -132,7 +132,7 @@ all relevant information in the `oauth_authorized` function with return redirect(next_url) We store the token and the associated secret in the session so that the -tokengetter can return it. Additionally we also store the Twitter username +tokengetter can return it. Additionally, we also store the Twitter username that was sent back to us so that we can later display it to the user. In larger applications it is recommended to store satellite information in a database instead to ease debugging and more easily handle additional information