Wrap long lines

pengwynn · pengwynn · commit fb5feaeb1b61 · 2013-01-29T08:58:33.000-06:00
diff --git a/content/v3.md b/content/v3.md
@@ -127,13 +127,21 @@ If resources have custom validation errors, they will be documented with the res
 
 ## HTTP Redirects
 
-API v3 uses HTTP redirection where appropriate. Clients should assume that any request may result in a redirection. Receiving an HTTP redirection is *not* an error and clients should follow that redirect. Redirect responses will have a `Location` header field which contains the URI of the resource to which the client should repeat the requests.
+API v3 uses HTTP redirection where appropriate. Clients should assume that any
+request may result in a redirection. Receiving an HTTP redirection is *not* an
+error and clients should follow that redirect. Redirect responses will have a
+`Location` header field which contains the URI of the resource to which the
+client should repeat the requests.
 
 301
-: Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed the new URI.
+: Permanent redirection. The URI you used to make the request has been
+superseded by the one specified in the `Location` header field. This and all
+future requests to this resource should be directed to the new URI.
 
 302, 307
-: Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
+: Temporary redirection. The request should be repeated verbatim to the URI
+specified in the `Location` header field but clients should continue to use the
+original URI for future requests.
 
 Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
 
