[pull] master from supabase:master

.github/workflows/docs-tests.yml

@@ -5,6 +5,7 @@ on:
     branches: ['master']
     paths:
       - 'apps/docs/**/*.ts*'
+      - 'apps/docs/spec/**/*.json'
 
 # Cancel old builds on new commit for same workflow + branch/PR
 concurrency:

apps/docs/content/guides/auth/jwts.mdx

@@ -6,7 +6,7 @@ subtitle: 'Information on how best to use JSON Web Tokens with Supabase'
 
 A [JSON Web Token](https://jwt.io/introduction) is a type of data structure, represented as a string, that usually contains identity and authorization information about a user. It encodes information about its lifetime and is signed with a cryptographic key to make it tamper-resistant.
 
-Supabase Auth continuously issues a new JWT for each user session, for as long as the user remains signed in. Check the comprehensive guide on [Sessions](/docs/guides/sessions) to find out how you can tailor this process for your needs.
+Supabase Auth continuously issues a new JWT for each user session, for as long as the user remains signed in. Check the comprehensive guide on [Sessions](/docs/guides/auth/sessions) to find out how you can tailor this process for your needs.
 
 JWTs provide the foundation for [Row Level Security](/docs/guides/database/row-level-security). Each Supabase product is able to securely decode and verify the validity of a JWT it receives before using Postgres policies and roles to authorize access to the project's data.