docs(auth): clarify JWT validity after session expiry

src/routes/docs/products/auth/jwt/+page.markdoc

@@ -18,7 +18,7 @@ When you build backend APIs to extend Appwrite's functionality, these APIs shoul
 
 [JSON Web Tokens](https://jwt.io/introduction) (JWTs) are a secure means to transfer information or claims between two parties. JWTs act like temporary copies of the user's ID card that allow Appwrite's Server SDKs to access information on behalf of a user.
 
-You need to create a session using the Client SDKs **before** generating a JWT. The JWT will be a stateless proof of claim for the identity of the authenticated user and expire after 15 minutes or when the session is deleted.
+You need to create a session using the Client SDKs **before** generating a JWT. The JWT is a stateless proof of claim for the identity of the authenticated user and expires after 15 minutes. It also becomes invalid if the session it was created from expires or is deleted.
 
 You can generate a JWT like this on a [Client SDK](/docs/sdks#client).
 
@@ -547,4 +547,4 @@ This will return every row regardless of permissions, which could lead to privac
 }
 ```
 
-If you're integrating existing backend services with Appwrite or adding backend endpoints to perform more complex logic, JWT authentication helps them behave similarly to actual Appwrite endpoints.
+If you're integrating existing backend services with Appwrite or adding backend endpoints to perform more complex logic, JWT authentication helps them behave similarly to actual Appwrite endpoints.