Make RFC6570 appendix C instead of B

The data type conversion handled in another PR adding an appendix
logically occurs before the 6570 concerns.

Author: handrews

versions/3.0.4.md

@@ -1060,7 +1060,7 @@ Field Name | Type | Description
 <a name="parameterExample"></a>example | Any | Example of the parameter's potential value. The example SHOULD match the specified schema and encoding properties if present. The `example` field is mutually exclusive of the `examples` field. Furthermore, if referencing a `schema` that contains an example, the `example` value SHALL _override_ the example provided by the schema. To represent examples of media types that cannot naturally be represented in JSON or YAML, a string value can contain the example with escaping where necessary.
 <a name="parameterExamples"></a>examples | Map[ `string`, [Example Object](#exampleObject) \| [Reference Object](#referenceObject)] | Examples of the parameter's potential value. Each example SHOULD contain a value in the correct format as specified in the parameter encoding. The `examples` field is mutually exclusive of the `example` field. Furthermore, if referencing a `schema` that contains an example, the `examples` value SHALL _override_ the example provided by the schema.
 
-See also [Appendix B: Using RFC6570 Implementations](#usingRFC6570Implementations) for additional guidance.
+See also [Appendix C: Using RFC6570 Implementations](#usingRFC6570Implementations) for additional guidance.
 
 ###### Fixed Fields and considerations for use with `content`
 
@@ -3498,7 +3498,7 @@ Version   | Date       | Notes
 1.1       | 2012-08-22 | Release of Swagger 1.1
 1.0       | 2011-08-10 | First release of the Swagger Specification
 
-## <a name="usingRFC6570Implementations"></a>Appendix B: Using RFC6570 Implementations
+## <a name="usingRFC6570Implementations"></a>Appendix C: Using RFC6570 Implementations
 
 Serialization is defined in terms of RFC6570 URI Templates in two scenarios: