Clarify where to get the values for githubOrgName and githubOrgAdminToken

Author: n4bb12

README.md

@@ -46,21 +46,33 @@ The output directory of the static website.
 
 `config.githubOrgName`
 
-The GitHub org users need to be part of.
+The GitHub organization users need to be part of in order to be able to sign in.
+
+You cannot use your personal GitHub account for this, you need an organization.
 
 `config.githubClientId`
 `config.githubClientSecret`
 
 The id/secret pair of your GitHub OAuth app.
-You can create a new app at `https://github.com/organizations/{config.githubOrgName}/settings/applications/new`
+
+Create a new OAuth app at
+`https://github.com/organizations/{config.githubOrgName}/settings/applications/new`
 
 `config.githubOrgAdminToken`
 
-Private org memberships can only be determined by making an authenticated API request.
+Create a token with `read:org` permission at <https://github.com/settings/tokens>.
 
-We could request `read:org` scope during the OAuth flow and then use each user's access token to determine org membership, but using this method means the user additionally needs to request org access during or after the login flow and requires an org admin to confirm. This makes this approach inconvenient for both the users and the admin.
+The reason you need a token is that private org memberships can only be
+determined by making an authenticated API request.
 
-Therefore we're using a separate org admin token to verify membership during login (org admins can see all users).
+We could request `read:org` scope during the OAuth flow and then use each user's
+access token to determine org membership, but using this method means the user
+additionally needs to request org access during or after the login flow and
+requires an org admin to confirm. This makes this approach inconvenient for both
+the users and the admin.
+
+Therefore we're using a separate org admin token to verify membership during
+login (org admins can see all users).
 
 ### Step 3 — Create a `vercel.json`
 
@@ -78,13 +90,21 @@ Therefore we're using a separate org admin token to verify membership during log
 
 This routes all traffic through the lambda endpoint.
 
-Adapt `includeFiles` to your public output folder. Including these files is required because the static website needs to be deployed as part of the lambda function, not the default build. See also the [function docs](https://vercel.com/docs/projects/project-configuration#functions) and [size limit docs](https://vercel.com/docs/functions/serverless-functions/runtimes#size-limits).
+Adapt `includeFiles` to your public output folder. Including these files is
+required because the static website needs to be deployed as part of the lambda
+function, not the default build. See also these docs:
+
+- [functions](https://vercel.com/docs/projects/project-configuration#functions)
+- [size limits](https://vercel.com/docs/functions/serverless-functions/runtimes#size-limits).
 
 ### Step 4 — Build
 
-If you have an existing `build` script, rename it to `vercel-build` to build your website as part of the lambda build instead of the normal build.
+If you have an existing `build` script, rename it to `vercel-build` to build
+your website as part of the lambda build instead of the normal build.
 
-Make sure to not keep the `build` script as it would result in duplicate work or may break deployment entirely. For more information see [custom-build-step-for-node-js](https://vercel.com/docs/functions/serverless-functions/runtimes/node-js#custom-build-step-for-node.js).
+Make sure to not keep the `build` script as it would result in duplicate work or
+may break deployment entirely. For more information see
+[custom-build-step-for-node-js](https://vercel.com/docs/functions/serverless-functions/runtimes/node-js#custom-build-step-for-node.js).
 
 ```json
 {
@@ -102,4 +122,5 @@ To develop locally, run
 yarn vercel dev
 ```
 
-When developing locally, you'll need to update your GitHub OAuth app's redirect URL to `http://localhost:3000`.
+When developing locally, you'll need to update your GitHub OAuth app's redirect
+URL to `http://localhost:3000`.