Moved GBFS reference in Provider

Author: schnuerle

provider/README.md

@@ -12,6 +12,7 @@ This specification contains a data standard for *mobility as a service* provider
   * [Versioning](#versioning)
   * [Modes](#modes)
   * [Responses and Error Messages](#responses-and-error-messages)
+  * [GBFS](#GBFS)
   * [JSON Schema](#json-schema)
   * [Pagination](#pagination)
   * [Municipality Boundary](#municipality-boundary)
@@ -34,7 +35,6 @@ This specification contains a data standard for *mobility as a service* provider
   * [Special Group Type](#special-group-type)
   * [Data Redaction](#data-redaction)
 * [Realtime Data](#realtime-data)
-  * [GBFS](#GBFS)
   * [Data Latency Requirements][data-latency]
   * [Events][events]
   * [Stops](#stops)
@@ -86,6 +86,12 @@ All response fields must use `lower_case_with_underscores`.
 
 [Top][toc]
 
+### GBFS
+
+See the [GBFS Requirement](/README.md#gbfs-requirement) language for more details.
+
+[Top][toc]
+
 ### JSON Schema
 
 MDS defines [JSON Schema][json-schema] files for each endpoint.
@@ -451,12 +457,6 @@ Using k-anonymity will reduce, but not necessarily eliminate the risk that an in
 
 ## Realtime Data
 
-### GBFS
-
-See the [GBFS Requirement](/README.md#gbfs-requirement) language for more details.
-
-[Top][toc]
-
 ### Data Latency Requirements
 
 The data returned by a near-realtime endpoint should be as close to realtime as possible, but in no case should it be more than 5 minutes out-of-date. Near-realtime endpoints must contain `last_updated` and `ttl` properties in the top-level of the response body. These properties are defined as: