SVCB: swap URI production and literals

draft-ietf-core-transport-indication.md

@@ -815,12 +815,6 @@ it would have required that the server present some credential that could be ver
 for example an x5chain containing a Let's Encrypt certificate.
 
 
-## Expressing Service Parameters as literals {#svcblit}
-
-TBD
-
-### Examples
-
 ## Producing a URI from a discovered service {#svcb2uri}
 
 If a service's discovery process does not produce a URI but an address, host name and/or Service Binding Parameters,
@@ -832,6 +826,13 @@ TBD
 
 ### Examples
 
+
+## Expressing Service Parameters as literals {#svcblit}
+
+TBD
+
+### Examples
+
 # Guidance to upcoming transports {#upcomingtransports}
 
 When new transports are defined for CoAP,