Update core concepts guide (#2669)

Author: alexisintech

docs/getting-started/core-concepts.mdx

@@ -39,34 +39,46 @@ To get started, see the [configuration docs](/docs/guides/configure/auth-strateg
 
 ## Building your application
 
-The Clerk JavaScript SDK, or ClerkJS, is where Clerk all started. It is the core SDK that powers all other JavaScript SDKs, including React and Next.js. The following sections will introduce you to the main objects that make up ClerkJS.
+### Session token
 
-### Clerk
+When a user is authenticated in your application, Clerk generates a short-lived session token that you can use to authenticate requests to your backend. This token is a JSON Web Token (JWT) that contains information about the user and their session.
+
+Read more about Clerk session tokens and how they work in [the guide on how Clerk works](/docs/guides/how-clerk-works/overview).
+
+### Key Clerk objects
+
+The Clerk JavaScript SDK, or ClerkJS, is where Clerk all started. It is the core SDK that powers all other JavaScript SDKs, including React and Next.js. As you build, you'll likely interact with the following objects.
+
+#### Clerk
 
 The [`Clerk`](/docs/reference/javascript/clerk) class is the main entry point for the Clerk JavaScript SDK. All other objects are accessible from the `Clerk` object. As you're building your application, you'll likely interact with these objects, either directly or through helpers provided by the other SDKs, like React hooks or Vue composables.
 
-### Client
+#### Client
 
 A client represents the current device or software accessing an application such as your web browser, native application, or Chrome Extension. It is represented by the [`Client`](/docs/reference/javascript/client) object.
 
-### Session
+#### Session
 
 A session is a secure representation of the authentication state of the current user. Each client can hold multiple sessions on the same device. It is represented by the [`Session`](/docs/reference/javascript/session) object.
 
-### User
+#### User
 
 The [`User`](/docs/reference/javascript/user) object represents the current user of the session. It holds all the basic user information such as the user's name, email addresses, and phone numbers, and including their public, private, and unsafe metadata.
 
-### Organization
+#### Organization
 
 Organizations are a flexible and scalable way to manage users and their access to resources within your Clerk application. With organizations, you can assign specific roles and permissions to users, making them useful for managing projects, coordinating teams, or facilitating partnerships.
 
-Users can belong to many organizations. One of them will be the ["active organization"](/docs/guides/organizations/overview#active-organization) of the session. It is represented by the [`Organization`](/docs/reference/javascript/organization) object. To learn about organizations, see the [dedicated guide](/docs/guides/organizations/overview).
+Users can belong to many organizations. One of them will be the [active organization](!active-organization) of the session. It is represented by the [`Organization`](/docs/reference/javascript/organization) object. To learn about organizations, see the [dedicated guide](/docs/guides/organizations/overview).
 
-### Sign in
+#### Sign in
 
 The [`SignIn`](/docs/reference/javascript/sign-in) object holds the state of the current sign-in and provides helper methods to navigate and complete the sign-in process. It is used to manage the sign-in lifecycle, including the first and second factor verification, and the creation of a new session.
 
-### Sign up
+#### Sign up
 
 The [`SignUp`](/docs/reference/javascript/sign-up) object holds the state of the current sign-up and provides helper methods to navigate and complete the sign-up process. Once a sign-up is complete, a new user is created.
+
+## Deep dive
+
+For a deeper dive into how Clerk works, like how our authentication model works, see the [dedicated guide](/docs/guides/how-clerk-works/overview).

docs/guides/organizations/overview.mdx

@@ -58,7 +58,7 @@ Verified domains can be used to streamline enrollment into an organization. For
 In the Clerk Dashboard, there are two types of workspaces:
 
 - **Personal account**: A personal account/workspace is a user's unique, individual space, independent of any organization.
-- **Organization workspace**: An organization workspace is owned and managed by an organization, which can have multiple members, also known as collaborators. The organization workspace that a user is currently viewing is called the [active organization](/docs/guides/organizations/overview#active-organization).
+- **Organization workspace**: An organization workspace is owned and managed by an organization, which can have multiple members, also known as collaborators. The organization workspace that a user is currently viewing is called the [active organization](!active-organization).
 
 Most multi-tenant applications want every user to be part of an organization rather than operating in an isolated personal account. Accordingly, **personal accounts are disabled by default** once you enable organizations. After signing up, [a user must create or join an organization before they can proceed](/docs/guides/configure/session-tasks).
 

docs/guides/sessions/session-tokens.mdx

@@ -98,7 +98,7 @@ Read more about Clerk session tokens and how they work in [the guide on how Cler
     | `sid` | session ID | The ID of the current session. | `sess_123` |
     | `sub` | subject | The ID of the current user of the session. See [RFC 7519](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.2) for more information. | `user_123` |
 
-    The following claims are only included if the user is part of an organization and that organization is [active](/docs/guides/organizations/overview#active-organization):
+    The following claims are only included if the user is part of an organization and that organization is [active](!active-organization):
 
     | Claim | Abbreviation expanded | Description | Example |
     | - | - | - | - |