From f5df4b96b041f61280684cdaebd8b0f4e98bc3a8 Mon Sep 17 00:00:00 2001 From: Samuel Ryan Date: Mon, 9 Nov 2015 18:23:21 +0000 Subject: [PATCH] Standardises referencing label format MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit “RFCxxx Section x.x” rather than “Section x.x of RFCxxx”. --- contents/codes/100.md | 2 +- contents/codes/101.md | 2 +- contents/codes/200.md | 2 +- contents/codes/203.md | 6 +++--- contents/codes/204.md | 2 +- contents/codes/206.md | 2 +- contents/codes/207.md | 4 ++-- contents/codes/208.md | 10 ++++++---- contents/codes/300.md | 2 +- contents/codes/426.md | 2 +- 10 files changed, 18 insertions(+), 16 deletions(-) diff --git a/contents/codes/100.md b/contents/codes/100.md index 3c42a96..035682f 100644 --- a/contents/codes/100.md +++ b/contents/codes/100.md @@ -20,7 +20,7 @@ If the request did not contain an Expect header field containing the --- -* 1 As described in [RFC7231 Section 5.1.1][2] +* 1 Expect [RFC7231 Section 5.1.1][2] * Source: [RFC7231 Section 6.1.1][1] [1]: diff --git a/contents/codes/101.md b/contents/codes/101.md index ffe5a21..69b825a 100644 --- a/contents/codes/101.md +++ b/contents/codes/101.md @@ -21,7 +21,7 @@ protocol might be advantageous when delivering resources that use such features. --- -* 1 As described in [Section 6.7 of RFC7230][2] +* 1 Upgrade [RFC7230 Section 6.7][2] * Source: [RFC7231 Section 6.2.2][1] [1]: diff --git a/contents/codes/200.md b/contents/codes/200.md index caea02a..2647e00 100644 --- a/contents/codes/200.md +++ b/contents/codes/200.md @@ -31,7 +31,7 @@ method definition or explicit cache controls[1](#ref-1). --- * 1 Calculating Heuristic Freshness -[Section 4.2.2 of RFC7234][2] +[RFC7234 Section 4.2.2][2] * Source: [RFC7231 Section 6.3.1][1] [1]: diff --git a/contents/codes/203.md b/contents/codes/203.md index 92ca247..d162e4a 100644 --- a/contents/codes/203.md +++ b/contents/codes/203.md @@ -25,10 +25,10 @@ method definition or explicit cache controls[3](#ref-3). --- * 1 Transformations -[Section 5.7.2 of RFC7230][2] -* 2 Warning [Section 5.5 of RFC7234][3] +[RFC7230 Section 5.7.2][2] +* 2 Warning [RFC7234 Section 5.5][3] * 3 Calculating Heuristic Freshness -[Section 4.2.2 of RFC7234][4] +[RFC7234 Section 4.2.2][4] * Source: [RFC7231 Section 6.3.4][1] [1]: diff --git a/contents/codes/204.md b/contents/codes/204.md index d49841e..4052279 100644 --- a/contents/codes/204.md +++ b/contents/codes/204.md @@ -39,7 +39,7 @@ method definition or explicit cache controls[1](#ref-1). --- * 1 Calculating Heuristic Freshness -[Section 4.2.2 of RFC7234][2] +[RFC7234 Section 4.2.2][2] * Source: [RFC7231 Section 6.3.5][1] [1]: diff --git a/contents/codes/206.md b/contents/codes/206.md index 4e5fd9a..314b763 100644 --- a/contents/codes/206.md +++ b/contents/codes/206.md @@ -108,7 +108,7 @@ explicit cache controls[3](#ref-3). * 2 Internet Media Type multipart/byteranges [RFC7233 Appendix A][3] * 3 Calculating Heuristic Freshness -[Section 4.2.2 of RFC7234][4] +[RFC7234 Section 4.2.2][4] * Source: [RFC7233 Section 4.1][1] [1]: diff --git a/contents/codes/207.md b/contents/codes/207.md index bfc0fd4..4f5a385 100644 --- a/contents/codes/207.md +++ b/contents/codes/207.md @@ -31,12 +31,12 @@ of the message execution for the identified resource as a whole[1](#ref-1). Some method definitions provide information about specific status codes clients should be prepared to see in a response. However, clients MUST be able to handle other status codes, using the generic -rules defined in [Section 10 of RFC2616][3]. +rules defined in [RFC2616 Section 10][3]. 2\. For PROPFIND and PROPPATCH, the format has been extended using the 'propstat' element instead of 'status', providing information about individual properties of a resource. This format is specific to PROPFIND and PROPPATCH, and is -described in detail in [RFC4918 Sections 9.1][4] and [RFC4918 9.2][5]. +described in detail in [RFC4918 Section 9.1][4] and [RFC4918 Section 9.2][5]. --- diff --git a/contents/codes/208.md b/contents/codes/208.md index 6ab6928..b11eac2 100644 --- a/contents/codes/208.md +++ b/contents/codes/208.md @@ -14,7 +14,7 @@ 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 -a bind loop as discussed in [RFC5842][2]. +a bind loop[1](#ref-1). A client can request the DAV:resource-id property in a PROPFIND request to guarantee that they can accurately reconstruct the binding structure of a @@ -23,7 +23,7 @@ collection with multiple bindings to a single resource. For backward compatibility with clients not aware of the 208 status code appearing in multistatus response bodies, it SHOULD NOT be used unless the client has signaled support for this specification using the "DAV" request -header[1](#ref-1). Instead, a [508 Loop Detected](/508) status should +header[2](#ref-2). Instead, a [508 Loop Detected](/508) status should be returned when a binding loop is discovered. This allows the server to return the 508 as the top-level return status, if it discovers it before it started the response, or in the middle of a multistatus, if it discovers it in the middle of @@ -31,8 +31,10 @@ streaming out a multistatus response. --- -* 1 'DAV' Request Header -[RFC5842Section 8.2][3] +* 1 URI Mappings Created by a New Binding +[RFC5842 Section 2.2][2] +* 2 'DAV' Request Header +[RFC5842 Section 8.2][3] * Source: [RFC5842 Section 7.1][1] [1]: diff --git a/contents/codes/300.md b/contents/codes/300.md index 2cb2e46..678a9a4 100644 --- a/contents/codes/300.md +++ b/contents/codes/300.md @@ -46,7 +46,7 @@ though deployment is a chicken-and-egg problem. * 1 Content Negotiation [RFC7231 Section 3.4][2] * 2 Calculating Heuristic Freshness -[Section 4.2.2 of RFC7234][3] +[RFC7234 Section 4.2.2][3] * 3 Web Linking [RFC5988][4] * Source: [RFC7231 Section 6.4.1][1] diff --git a/contents/codes/426.md b/contents/codes/426.md index f88947e..51f4b98 100644 --- a/contents/codes/426.md +++ b/contents/codes/426.md @@ -26,7 +26,7 @@ This service requires use of the HTTP/3.0 protocol. --- -* 1 Upgrade [Section 6.7 of RFC7230][2] +* 1 Upgrade [RFC7230 Section 6.7][2] * Source: [RFC7231 Section 6.5.15][1] [1]: