flatpak: change sections organizations

The "Publishing a single application" section introduces the use of
.flatpakrepo files, which are detailed in the subsequent "Publishing a
repository" section. Moving the latter section before the former
therefore makes more sense.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

content/guides/flatpak.md

@@ -61,6 +61,29 @@ More details about those commands are available in the
 
 # Publishing signed flatpaks applications
 
+## Publishing a repository
+
+When distributing several applications, it can be useful to publish the whole
+repository using a [.flatpakrepo](https://docs.flatpak.org/en/latest/hosting-a-repository.html#flatpakrepo-files)
+file.
+
+The only difference here is that the `GPGKey=...` line must be replaced with
+`SignatureKey=<PUBLICKEY>`, where `<PUBLICKEY>` is the base64-encoded public
+Ed25519 key.
+
+Such a .flatpakrepo file could be:
+
+```
+[Flatpak Repo]
+Title=Sample Repository
+Url=https://example.org/flatpak/repo
+Homepage=https://example.org/flatpak
+Comment=Sample Flatpak repository signed with Ed25519
+Description=This Flatpak repository provides applications signed with Ed25519
+Icon=https://example.org/flatpak/icon.svg
+SignatureKey=B3a86SmB+sby/N5onaxTXjK1OEAbZOI2fsdr3kKD+KE=
+```
+
 ## Publishing a single application
 
 One convenient way to distribute single flatpak applications is to use
@@ -68,9 +91,9 @@ One convenient way to distribute single flatpak applications is to use
 files. Those files include all necessary information for flatpak to be able to
 install and update the application.
 
-The only difference here is that the `GPGKey=...` line must be replaced with
-`SignatureKey=<PUBLICKEY>`, where `<PUBLICKEY>` is the base64-encoded public
-Ed25519 key.
+Exactly as it is done with with `.flatpakrepo` files, using
+`SignatureKey=<PUBLICKEY>` instead of `GPGKey=...` will instruct flatpak to
+enable Ed25519 signature verification for this repository.
 
 This line will instruct flatpak to add the corresponding configuration keys to
 the remote and perform signature verification when installing and/or updating
@@ -88,29 +111,6 @@ IsRuntime=false
 SignatureKey=B3a86SmB+sby/N5onaxTXjK1OEAbZOI2fsdr3kKD+KE=
 ```
 
-## Publishing a repository
-
-When distributing several applications, it can be useful to publish the whole
-repository using a [.flatpakrepo](https://docs.flatpak.org/en/latest/hosting-a-repository.html#flatpakrepo-files)
-file.
-
-Exactly as it is done with with `.flatpakref` files, using
-`SignatureKey=<PUBLICKEY>` instead of `GPGKey=...` will instruct flatpak to
-enable Ed25519 signature verification for this repository.
-
-Such a .flatpakrepo file could be:
-
-```
-[Flatpak Repo]
-Title=Sample Repo
-Url=https://example.org/flatpak/repo
-Homepage=https://example.org/flatpak
-Comment=Sample Flatpak repository signed with Ed25519
-Description=This Flatpak repository provides applications signed with Ed25519
-Icon=https://example.org/flatpak/icon.svg
-SignatureKey=B3a86SmB+sby/N5onaxTXjK1OEAbZOI2fsdr3kKD+KE=
-```
-
 ## Publishing a bundle
 
 Flatpak applications can also be distributed as