diff --git a/docs/configuration/options.md b/docs/configuration/options.md
index 2daf83f0..48e53d25 100644
--- a/docs/configuration/options.md
+++ b/docs/configuration/options.md
@@ -17,8 +17,8 @@ If your Next.js application uses a custom base path, specify the route to the AP
 
 _e.g. `NEXTAUTH_URL=https://example.com/custom-route/api/auth`_
 
-:::tip
-To set environment variables on Vercel, you can use the [dashboard](https://vercel.com/dashboard) or the `vercel env` command.
+:::note
+On [Vercel](https://vercel.com) deployments, we will read the `VERCEL_URL` environment variable, so you won't need to define `NEXTAUTH_URL`.
 :::
 
 ### NEXTAUTH_URL_INTERNAL
@@ -66,11 +66,17 @@ See the [providers documentation](/configuration/providers/oauth) for a list of
 
 #### Description
 
-A random string used to hash tokens, sign cookies and generate cryptographic keys.
+A random string used to hash tokens, sign/encrypt cookies and generate cryptographic keys.
+
+If not specified, it uses a hash for all configuration options, including OAuth Client ID / Secrets for entropy. Although if the user does not use such a provider, the configuration might be guessed.
 
-If not specified, it uses a hash for all configuration options, including Client ID / Secrets for entropy.
+:::warning
+The default behaviour is volatile, and it is strongly recommended you explicitly specify a value. If `secret` is omitted in production, we will throw an error.
+:::
 
-The default behaviour is volatile, and it is strongly recommended you explicitly specify a value to avoid invalidating end user sessions when configuration changes are deployed.
+:::tip
+If you rely on the default secret generation in development, you might notice JWT decryption errors, since the secret changes whenever you change your configuration. Defining a secret will make this problem go away.
+:::
 
 ---
 
@@ -116,38 +122,17 @@ session: {
 
 JSON Web Tokens can be used for session tokens if enabled with `session: { jwt: true }` option. JSON Web Tokens are enabled by default if you have not specified a database.
 
-By default JSON Web Tokens are not signed (JWS) but are encrypted (JWE).
+By default JSON Web Tokens are encrypted (JWE). We recommend you keep this behavoiur, but you can override it by defining your own `encode` and `decode` methods.
 
 #### JSON Web Token Options
 
 ```js
 jwt: {
-  // A secret to use for key generation - you should set this explicitly
-  // Defaults to NextAuth.js secret if not explicitly specified.
-  // This is used to generate the actual signingKey and produces a warning
-  // message if not defined explicitly.
+  // A secret to use for key generation. Defaults to the top-level `session`.
   secret: 'INp8IvdIyeMcoGAgFGoA61DdBglwwSqnXJZkgz8PSnw',
-  // You can generate a signing key using `jose newkey -s 512 -t oct -a HS512`
-  // This gives you direct knowledge of the key used to sign the token so you can use it
-  // to authenticate indirectly (eg. to a database driver)
-  signingKey: {
-     kty: "oct",
-     kid: "Dl893BEV-iVE-x9EC52TDmlJUgGm9oZ99_ZL025Hc5Q",
-     alg: "HS512",
-     k: "K7QqRmJOKRK2qcCKV_pi9PSBv3XP0fpTu30TP8xn4w01xR3ZMZM38yL2DnTVPVw6e4yhdh0jtoah-i4c_pZagA"
-  },
-  // If you chose something other than the default algorithm for the signingKey (HS512)
-  // you also need to configure the algorithm
-  verificationOptions: {
-     algorithms: ['HS256']
-  },
-  // Set to true to use encryption. Defaults to false (signing only).
-  encryption: true,
-  encryptionKey: "",
-  // decryptionKey: encryptionKey,
-  decryptionOptions: {
-     algorithms: ['A256GCM']
-  },
+  // The maximum age of the NextAuth.js issued JWT in seconds.
+  // Defaults to `session.maxAge`.
+  maxAge: 60 * 60 * 24 * 30,
   // You can define your own encode/decode functions for signing and encryption
   // if you want to override the default behaviour.
   async encode({ secret, token, maxAge }) {},
diff --git a/docs/errors.md b/docs/errors.md
index a82a6769..3a5e687e 100644
--- a/docs/errors.md
+++ b/docs/errors.md
@@ -166,6 +166,10 @@ This error happens when `[...nextauth].js` file is not found inside `pages/api/a
 
 Make sure the file is there and the filename is written correctly.
 
+#### NO_SECRET
+
+In production, we expect you to define a `secret` property in your configuration. In development, this is shown as a warning for convenienve. [Read more](https://next-auth.js.org/configuration/options#secret)
+
 #### oauth_callback_error expected 200 OK with body but no body was returned
 
 This error might happen with some of the providers. It happens due to `openid-client`(which is peer dependency) node version mismatch. For instance, `openid-client` requires `>=14.2.0` for `lts/fermium` and has similar limits for the other versions. For the full list of the compatible node versions please see [package.json](https://github.com/panva/node-openid-client/blob/2a84e46992e1ebeaf685c3f87b65663d126e81aa/package.json#L78)
diff --git a/docs/warnings.md b/docs/warnings.md
index e7e21ee2..669c993a 100644
--- a/docs/warnings.md
+++ b/docs/warnings.md
@@ -15,39 +15,19 @@ All warnings indicate things which you should take a look at, but do not inhibit
 
 Environment variable `NEXTAUTH_URL` missing. Please set it in your `.env` file.
 
+:::note
+On [Vercel](https://vercel.com) deployments, we will read the `VERCEL_URL` environment variable, so you won't need to define `NEXTAUTH_URL`.
+:::
+
 ---
 
 ## Server
 
 These warnings are displayed on the terminal.
 
-#### JWT_AUTO_GENERATED_SIGNING_KEY
-
-To remedy this warning, you can either:
-
-**Option 1**: Pass a pre-regenerated Private Key (and, optionally a Public Key) in the jwt options.
-
-```js title="/pages/api/auth/[...nextauth].js"
-jwt: {
-  signingKey: process.env.JWT_SIGNING_PRIVATE_KEY,
-
-  // You can also specify a public key for verification if using public/private key (but private only is fine)
-  // verificationKey: process.env.JWT_SIGNING_PUBLIC_KEY,
-
-  // If you want to use some key format other than HS512 you can specify custom options to use
-  // when verifying (note: verificationOptions should include a value for maxTokenAge as well).
-  // verificationOptions = {
-  //   maxTokenAge: `${maxAge}s`, // e.g. `${30 * 24 * 60 * 60}s` = 30 days
-  //   algorithms: ['HS512']
-  // },
-}
-```
-
-You can use [node-jose-tools](https://www.npmjs.com/package/node-jose-tools) to generate keys on the command line and set them as environment variables, i.e. `jose newkey -s 256 -t oct -a HS512`.
-
-**Option 2**: Specify custom encode/decode functions on the jwt object. This gives you complete control over signing / verification / etc.
+#### NO_SECRET
 
-#### JWT_AUTO_GENERATED_ENCRYPTION_KEY
+In development, we generate a `secret` based on your configuration for convenience. This is volatile and will throw an error in production. [Read more](https://next-auth.js.org/configuration/options#secret)
 
 ## Adapter