Update connected-network-type.yaml

code/API_definitions/connected-network-type.yaml

@@ -33,7 +33,11 @@ info:
 
     The endpoint `POST /retrieve` allows to get connected Network Type.
 
-    # Identifying the device from the access token
+    # Further info and support
+
+    (FAQs will be added in a later version of the documentation)
+
+    ### Identifying the device from the access token
 
     This API requires the API consumer to identify a device as the subject of the API as follows:
     - When the API is invoked using a two-legged access token, the subject will be identified from the optional `device` object, which therefore MUST be provided.
@@ -47,10 +51,6 @@ info:
 
     - If the subject can be identified from the access token and the optional `device` object is also included in the request, then the server will return an error with the `422 UNNECESSARY_IDENTIFIER` error code. This will be the case even if the same device is identified by these two methods, as the server is unable to make this comparison.
 
-    ## Further info and support
-
-    (FAQs will be added in a later version of the documentation)
-
     ### Multi-SIM scenario handling
 
     In multi-SIM scenarios where more than one mobile device is associated with a phone number (e.g. a smartphone with an associated smartwatch), it might not be possible to uniquely identify from that phone number the device for which the connected network type should be returned. If the phone number is used as the device identifier when querying in a multi-SIM scenario, the API may: