Gives 2xx codes simple opening paragraphs

contents/codes/200.md

@@ -6,9 +6,11 @@ references:
     "Rails HTTP Status Symbol": ":not_found"
 ---
 
-The 200 (OK) status code indicates that the request has succeeded. The payload 
-sent in a 200 response depends on the request method. For the methods defined by 
-this specification, the intended meaning of the payload can be summarized as:
+The 200 OK status code indicates that the request has succeeded. The payload
+sent in a 200 response depends on the request method.
+
+For the methods defined by  this specification, the intended meaning of the
+payload can be summarized as:
 
 GET a representation of the target resource
 

contents/codes/201.md

@@ -6,8 +6,10 @@ references:
     "Rails HTTP Status Symbol": ":created"
 ---
 
-The 201 (Created) status code indicates that the request has been fulfilled and
-has resulted in one or more new resources being created. The primary resource
+The 201 Created status code indicates that the request has been fulfilled and
+has resulted in one or more new resources being created.
+
+The primary resource
 created by the request is identified by either a Location header field in the
 response or, if no Location field is received, by the effective request URI.
 

contents/codes/202.md

@@ -6,10 +6,12 @@ references:
     "Rails HTTP Status Symbol": ":accepted"
 ---
 
-The 202 (Accepted) status code indicates that the request has been accepted for
+The 202 Accepted status code indicates that the request has been accepted for
 processing, but the processing has not been completed. The request might or
 might not eventually be acted upon, as it might be disallowed when processing
-actually takes place. There is no facility in HTTP for re-sending a status code
+actually takes place.
+
+There is no facility in HTTP for re-sending a status code
 from an asynchronous operation.
 
 The 202 response is intentionally noncommittal. Its purpose is to allow a server

contents/codes/203.md

@@ -6,14 +6,15 @@ references:
     "Rails HTTP Status Symbol": ":non_authoritative_information"
 ---
 
-The 203 (Non-Authoritative Information) status code indicates that the request
+The 203 Non-Authoritative Information status code indicates that the request
 was successful but the enclosed payload has been modified from that of the
 origin server's [200 (OK)](/200) response by a transforming proxy
-([Section 5.7.2 of RFC7230][2]). This status code allows the proxy to notify
-recipients when a transformation has been applied, since that knowledge might
-impact later decisions regarding the content. For example, future cache
-validation requests for the content might only be applicable along the same
-request path (through the same proxies).
+([Section 5.7.2 of RFC7230][2]).
+
+This status code allows the proxy to notify recipients when a transformation has
+been applied, since that knowledge might impact later decisions regarding the
+content. For example, future cache validation requests for the content might
+only be applicable along the same request path (through the same proxies).
 
 The 203 response is similar to the Warning code of 214 Transformation Applied
 ([Section 5.5 of RFC7234][3]), which has the advantage of being applicable to

contents/codes/204.md

@@ -6,11 +6,12 @@ references:
     "Rails HTTP Status Symbol": ":no_content"
 ---
 
-The 204 (No Content) status code indicates that the server has successfully
+The 204 No Content status code indicates that the server has successfully
 fulfilled the request and that there is no additional content to send in the
-response payload body. Metadata in the response header fields refer to the
-target resource and its selected representation after the requested action was
-applied.
+response payload body.
+
+Metadata in the response header fields refer to the target resource and its
+selected representation after the requested action was applied.
 
 For example, if a 204 status code is received in response to a PUT request and
 the response contains an ETag header field, then the PUT was successful and the

contents/codes/205.md

@@ -6,7 +6,7 @@ references:
     "Rails HTTP Status Symbol": ":reset_content"
 ---
 
-The 205 (Reset Content) status code indicates that the server has fulfilled the
+The 205 Reset Content status code indicates that the server has fulfilled the
 request and desires that the user agent reset the "document view", which caused
 the request to be sent, to its original state as received from the origin
 server.

contents/codes/206.md

@@ -4,7 +4,7 @@ code: 206
 title: Partial Content
 ---
 
-The 206 (Partial Content) status code indicates that the server is successfully
+The 206 Partial Content status code indicates that the server is successfully
 fulfilling a range request for the target resource by transferring one or more
 parts of the selected representation that correspond to the satisfiable ranges
 found in the request's Range header field (see [RFC7233 Section 3.1][2]).

contents/codes/207.md

@@ -7,11 +7,12 @@ references:
 ---
 
 A Multi-Status response conveys information about multiple resources in
-situations where multiple status codes might be appropriate. The default
-Multi-Status response body is a text/xml or application/xml HTTP entity with a
-'multistatus' root element. Further elements contain 200, 300, 400, and 500
-series status codes generated during the method invocation. 100 series status
-codes SHOULD NOT be recorded in a 'response' XML element.
+situations where multiple status codes might be appropriate.
+
+The default Multi-Status response body is a text/xml or application/xml HTTP
+entity with a 'multistatus' root element. Further elements contain 200, 300,
+400, and 500 series status codes generated during the method invocation. 100
+series status codes SHOULD NOT be recorded in a 'response' XML element.
 
 Although '207' is used as the overall response status code, the recipient needs
 to consult the contents of the multistatus response body for further information

contents/codes/208.md

@@ -4,12 +4,14 @@ code: 208
 title: Already Reported
 ---
 
-The 208 (Already Reported) status code can be used inside a DAV: propstat
+The 208 Already Reported status code can be used inside a DAV: propstat
 response element to avoid enumerating the internal members of multiple bindings
-to the same collection repeatedly. For each binding to a collection inside the
-request's scope, only one will be reported with a 200 status, while subsequent
-DAV:response elements for all other bindings will use the 208 status, and no
-DAV:response elements for their descendants are included.
+to the same collection repeatedly.
+
+For each binding to a collection inside the request's scope, only one will be
+reported with a 200 status, while subsequent DAV:response elements for all other
+bindings will use the 208 status, and no DAV:response elements for their
+descendants are included.
 
 Note that the 208 status will only occur for "Depth: infinity" requests, and
 that it is of particular importance when the multiple collection bindings cause

contents/codes/226.md

@@ -8,12 +8,14 @@ references:
 
 The server has fulfilled a GET request for the resource, and the response is a
 representation of the result of one or more instance-manipulations applied to
-the current instance. The actual current instance might not be available except
-by combining this response with other previous or future responses, as
-appropriate for the specific instance-manipulation(s). If so, the headers of the
-resulting instance are the result of combining the headers from the status-226
-response and the other instances, following the rules in [section 13.5.3][2] of
-the HTTP/1.1 specification [10].
+the current instance.
+
+The actual current instance might not be available except by combining this
+response with other previous or future responses, as appropriate for the
+specific instance-manipulation(s). If so, the headers of the resulting instance
+are the result of combining the headers from the status-226 response and the
+other instances, following the rules in [section 13.5.3][2] of the
+HTTP/1.1 specification [10].
 
 The request MUST have included an A-IM header field listing at least
 one instance-manipulation.  The response MUST include an Etag header