Minor corrections to OAuth setup

1 files changed, 9 insertions, 12 deletions

diff --git a/installation.md b/installation.md
index 2448eb7..e4b6213 100644
--- a/installation.md
+++ b/installation.md
@@ -178,20 +178,17 @@ client before users can log into your service.  To do that, visit your profile
 on your meta.sr.ht instance, select the OAuth tab and register a new client.
 Append the path `/oauth/callback` to the URL of your service instance and
 choose this value as the base redirect URI (for example
-`https://git.sr.ht/oauth/callback`).  Update your configuration file with the
+`https://git.sr.ht/oauth/callback`). Update your configuration file with the
 client ID and secret.
 
-Before you can use that OAuth client, you have to set it to preauthorized using
-a database query, for example:
-
-    $ psql meta.sr.ht
-    meta.sr.ht=# select client_id, client_name from public.oauthclient;
-        client_id     | client_name
-    ------------------+-------------
-     00061df177b1e089 | git
-    (1 row)
-    meta.sr.ht=# update public.oauthclient set preauthorized = true where id = 1;
-    UPDATE 1
+You then need to configure that client as "preauthorized", e.g. first-party.
+This skips the OAuth consent screen that third-party applications are subject to
+and enables some extra API features. Log into the meta.sr.ht database and run
+the following query (adjusting the client ID as appropriate):
+
+```sql
+update oauthclient set preauthorized = true where client_id = 'your client ID';
+```
 
 Now you should be able to log into your new service.