make asynapi collapseable, reorder accordions according to left nav

Author: devalog

fern/products/api-def/api-def.yml

@@ -55,6 +55,7 @@ navigation:
             path: ./openapi-pages/server-frameworks/fastapi.mdx
             slug: fastapi
   - section: AsyncAPI
+    collapsed: true
     slug: asyncapi
     contents:
       - page: Overview

fern/products/api-def/pages/what-is-an-api-definition.mdx

@@ -151,64 +151,6 @@ Fern integrates with several API definition formats:
               description: The userId for the sender of the message
   ```
     
-  </Accordion>
-  <Accordion
-    title="Fern Definition (REST, Webhook, & WebSocket APIs)"
-  >
-    The Fern Definition is our take on a simpler API definition format. It is designed with **best-practices**, 
-    supports **both RESTful and event-driven APIs**, and is optimized for **SDK generation**. 
-
-    <Note>
-      The Fern Definition is inspired from internal API Definition formats built at companies like 
-      [Amazon](https://smithy.io/2.0/index.html), [Google](https://grpc.io/), [Palantir](https://blog.palantir.com/introducing-conjure-palantirs-toolchain-for-http-json-apis-2175ec172d32), 
-      Twilio and Stripe. These companies **rejected** OpenAPI and built their own version. 
-    </Note>
-
-    Check out an example Fern Definition below: 
-
-    ```yaml maxLines={0}
-    types:
-      MovieId: string
-
-      Movie:
-        properties:
-          id: MovieId
-          title: string
-          rating:
-            type: double
-            docs: The rating scale is one to five stars
-
-      CreateMovieRequest:
-        properties:
-          title: string
-          rating: double
-
-    service:
-      auth: false
-      base-path: /movies
-      endpoints:
-        createMovie:
-          docs: Add a movie to the database
-          method: POST
-          path: /create-movie
-          request: CreateMovieRequest
-          response: MovieId
-
-        getMovie:
-          method: GET
-          path: /{movieId}
-          path-parameters:
-            movieId: MovieId
-          response: Movie
-          errors:
-            - MovieDoesNotExistError
-
-    errors:
-      MovieDoesNotExistError:
-        status-code: 404
-        type: MovieId
-    ```
-
   </Accordion>
   <Accordion
     title="OpenRPC (JSON-RPC APIs)"
@@ -318,6 +260,64 @@ Fern integrates with several API definition formats:
     }
     ```
   </Accordion>
+  <Accordion
+    title="Fern Definition (REST, Webhook, & WebSocket APIs)"
+  >
+    The Fern Definition is our take on a simpler API definition format. It is designed with **best-practices**, 
+    supports **both RESTful and event-driven APIs**, and is optimized for **SDK generation**. 
+
+    <Note>
+      The Fern Definition is inspired from internal API Definition formats built at companies like 
+      [Amazon](https://smithy.io/2.0/index.html), [Google](https://grpc.io/), [Palantir](https://blog.palantir.com/introducing-conjure-palantirs-toolchain-for-http-json-apis-2175ec172d32), 
+      Twilio and Stripe. These companies **rejected** OpenAPI and built their own version. 
+    </Note>
+
+    Check out an example Fern Definition below: 
+
+    ```yaml maxLines={0}
+    types:
+      MovieId: string
+
+      Movie:
+        properties:
+          id: MovieId
+          title: string
+          rating:
+            type: double
+            docs: The rating scale is one to five stars
+
+      CreateMovieRequest:
+        properties:
+          title: string
+          rating: double
+
+    service:
+      auth: false
+      base-path: /movies
+      endpoints:
+        createMovie:
+          docs: Add a movie to the database
+          method: POST
+          path: /create-movie
+          request: CreateMovieRequest
+          response: MovieId
+
+        getMovie:
+          method: GET
+          path: /{movieId}
+          path-parameters:
+            movieId: MovieId
+          response: Movie
+          errors:
+            - MovieDoesNotExistError
+
+    errors:
+      MovieDoesNotExistError:
+        status-code: 404
+        type: MovieId
+    ```
+
+  </Accordion>
 </AccordionGroup>
 
 ## Why create an API definition?