Merge pull request #119 from cassidyjames/patch-2

verification: Include more info and an example

docs/02-for-app-authors/10-verification.md

@@ -10,7 +10,17 @@ First, [log in to Flathub](https://www.flathub.org/login). Go to the developer t
 
 ### Website
 
-To verify an app is associated with a specific website, Flathub uses the app ID in reverse domain name notation to look for a well-known URI. For example, an app ID `com.example.App` would require verifying the `example.com` domain with a response at `https://example.com/.well-known/org.flathub.VerifiedApps.txt` containing the unique code provided by the Flathub website during the verification process.
+To verify an app is associated with a specific website, Flathub uses the app ID in reverse domain name notation to look for a well-known URI. For example, an app ID `com.example.App` would require verifying the `example.com` domain with a response at `https://example.com/.well-known/org.flathub.VerifiedApps.txt` containing the unique token provided by the Flathub website during the verification process.
+
+The verification token is unique and unchanging for each app; if multiple apps are verified under the same domain, include each token on its own line. Lines beginning with `#` are ignored and can be used as comments. For example:
+
+```ini
+# com.example.App
+00000000-aaaa-0000-aaaa-000000000000
+
+# com.example.AnotherApp
+aaaaaaaa-0000-aaaa-0000-aaaaaaaaaaaa
+```
 
 For convenience and flexibility, verification of the well-known URI will follow redirects.