refactor: order admin addresses before permissions

Author: PaulRBerg

docs/concepts/11-governance.mdx

@@ -17,6 +17,15 @@ Admin addresses that control the Comptroller are listed in the [Admin Addresses]
 
 <ComptrollersTable />
 
+## Admin Addresses
+
+The Comptroller is introduced in Lockup v3.0, Airdrops v2.0 and Flow v2.0. For earlier versions, we use a direct "Admin"
+role for governance. These admin accounts have the same authority as the current Comptroller contract, with direct
+access to specific protocol functions. More concretely, the Admin is a collection of multisig wallets and EOAs currently
+in control of Sablier Labs.
+
+<AdminsTable />
+
 ## Contract Permissions
 
 ### Lockup
@@ -48,15 +57,6 @@ Comptroller has the following permissions on each chain where Flow is deployed:
 | Set Native Token   | [`setNativeToken`](/reference/flow/contracts/contract.SablierFlow#setnativetoken)     |
 | Set NFT Descriptor | [`setNFTDescriptor`](/reference/flow/contracts/contract.SablierFlow#setnftdescriptor) |
 
-## Admin Addresses
-
-The Comptroller is introduced in Lockup v3.0, Airdrops v2.0 and Flow v2.0. For earlier versions, we use a direct "Admin"
-role for governance. These admin accounts have the same authority as the current Comptroller contract, with direct
-access to specific protocol functions. More concretely, the Admin is a collection of multisig wallets and EOAs currently
-in control of Sablier Labs.
-
-<AdminsTable />
-
 ## Trustlessness
 
 Despite having an admin, the Sablier Protocol remains trustless. Here's why: