From d9a25865a24dfcbfac5082fda6ba44ae81c3025e Mon Sep 17 00:00:00 2001 From: "Antoine R. Dumont (@ardumont)" Date: Tue, 26 Jun 2018 10:48:12 +0200 Subject: [PATCH] docs/tutorials: Format sentences --- docs/tutorial.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/tutorial.rst b/docs/tutorial.rst index b23f05b..88d430b 100644 --- a/docs/tutorial.rst +++ b/docs/tutorial.rst @@ -268,13 +268,14 @@ We can also see that there are a few differences: * GitHub sends the next URL as part of the response header, while BitBucket sends it in the response body. -* GitHub differentiates API versions with a request header (our HTTP transport -mix-in will automatically use any headers provided by an optional -request_headers method that we implement here), while BitBucket has it as part -of their base service URL. BitBucket uses the IETF standard HTTP 429 response -code for their rate limit notifications (the HTTP transport mix-in -automatically handles that), while GitHub uses their own custom response -headers that need special treatment. +* GitHub differentiates API versions with a request header (our HTTP + transport mix-in will automatically use any headers provided by an + optional request_headers method that we implement here), while + BitBucket has it as part of their base service URL. BitBucket uses + the IETF standard HTTP 429 response code for their rate limit + notifications (the HTTP transport mix-in automatically handles + that), while GitHub uses their own custom response headers that need + special treatment. * But look at them! 58 lines of Python code, combined, to absorb all repositories from two of the largest and most influential source code hosting