Merge branch 'naga' into feature/drel-1157-discord-timeout-with-decryptandcombine

Author: Ansonhkg

docs/governance/overview.mdx

@@ -2,6 +2,12 @@
 title: "Overview"
 ---
 
+<Tip>
+$LITKEY and the Staking Contest to Select the Genesis Node Operator Set for the Naga Mainnet are now LIVE.
+
+[Learn More](https://spark.litprotocol.com/litkey-is-live/).
+</Tip>
+
 Lit Protocol has established an initial governance system to guide and organize its development and operations. This system exists to manage decision-making related to the core protocol, the infrastructure that supports it, and the broader ecosystem of applications built on top of it.
 
 ## Purpose

docs/index.mdx

@@ -4,13 +4,9 @@ description: 'Decentralized key management and private compute'
 ---
 
 <Tip>
-We're excited to announce that Vincent is now live! Vincent is a powerful toolkit that enables secure web3 capabilities for AI agents through:
+$LITKEY and the Staking Contest to Select the Genesis Node Operator Set for the Naga Mainnet are now LIVE.
 
-- Secure Delegation: Safely delegate wallet operations to AI agents while maintaining full control
-- Customizable Tools: Define and manage specific web3 actions your agents can perform
-- Policy Controls: Set granular rules and restrictions for how agents interact with web3
-
-Check out the [Vincent documentation](https://docs.heyvincent.ai/) to get started!
+[Learn More](https://spark.litprotocol.com/litkey-is-live/).
 </Tip>
 
 # Overview

docs/node-ops/overview.mdx

@@ -2,6 +2,12 @@
 title: "Overview"
 ---
 
+<Tip>
+$LITKEY and the Staking Contest to Select the Genesis Node Operator Set for the Naga Mainnet are now LIVE.
+
+[Learn More](https://spark.litprotocol.com/litkey-is-live/).
+</Tip>
+
 Lit Protocol is secured and operated by a decentralized network of validator nodes. These nodes are responsible for executing the threshold cryptographic operations that underpin the core functionality of the network, including signing, encryption, decryption, and private compute via Lit Actions.
 
 Each node participates in threshold signature multi-party computation (TSS MPC) protocols and operates inside a confidential compute environment (TEE), ensuring that no single operator can access plaintext key material or violate policy constraints.
@@ -14,4 +20,4 @@ A staking and delegation contest will be run to select the genesis validator set
 
 To whitelist your node, visit https://staking.litprotocol.com/ 
 
-Refer to the next page for details on hardware specs, minimum requirements, and operational guidelines for node operators. 
+Refer to the next page for details on hardware specs, minimum requirements, and operational guidelines for node operators. 

docs/sdk/auth-context-consumption/encrypt-and-decrypt.mdx

@@ -78,7 +78,7 @@ console.log("🧔🏻‍♂️ BobsAccount:", BobsAccount.address);
 Alice decides who can decrypt her encrypted data
 
 <Tip>
-  See SDK Reference for more details on the Access Control Conditions Builder. [Access Control Conditions Builder Reference](/sdk/sdk-reference/access-control-conditions/functions/createAccBuilder)
+  See the [Access Control Conditions Builder Reference API](/sdk/sdk-reference/access-control-conditions/functions/createAccBuilder) for more details on how to build access control conditions.
 </Tip>
 
 ### Build Access Control Conditions

docs/sdk/auth-context-consumption/pkp-sign.mdx

@@ -4,8 +4,7 @@ description: "Use your PKP to sign a message with the selected chain and scheme.
 ---
 
 <Tip>
-  See SDK Reference for more details on the PKP Sign. [PKP Sign
-  Reference](/sdk/sdk-reference/lit-client/functions/createLitClient#chain-raw-pkpsign)
+  See the [PKP Sign Reference API](/sdk/sdk-reference/lit-client/functions/createLitClient#chain-raw-pkpsign) for more details on how to sign a message with your PKP.
 </Tip>
 
 # Prerequisites

docs/sdk/auth/pkp-custom-auth/pkp-custom-auth.mdx

@@ -15,13 +15,13 @@ description: "Implement custom PKP authentication methods with Lit Actions"
 
 Custom Authentication allows <b>dApp owners</b> to provide PKPs (Programmable Key Pairs) to their users without requiring them to understand blockchain technology or manage private keys. Instead of forcing users to learn new authentication methods, you can leverage your existing authentication systems (OAuth, APIs, databases) while providing them with powerful web3 capabilities.
 
-This demonstrates the complete <b>dApp-centric custom authentication</b> flow from both perspectives: the <b>Site Owner</b> who sets up the system and the User who interacts with it.
+This demonstrates the complete <b>dApp-centric custom authentication</b> flow from both perspectives: the <b>Site Owner</b> who sets up the system and the <b>User</b> who interacts with it.
 
 # Overview
 
 In this example:
 
-- site owners control the PKP minting process and provide immutable validation logic via IPFS.
+- Site owners control the PKP minting process and provide immutable validation logic via IPFS.
 - Users get pre-minted PKPs and authenticate through the site owner's validation Lit Action.
 
 # Site Owner Walkthrough

docs/sdk/auth/pkp-native-auth/pkp-discord-auth.mdx

@@ -49,7 +49,7 @@ description: "Discord Authentication uses your Discord account to authenticate v
   </Step>
 
     <Step title="Generate Auth Context">
-Use your newly minted PKP to create an AuthContext. This method will cache two things:
+Use your PKP's public key to create an AuthContext. This method will cache two things:
 1. session key pair - a temporary cryptographic key pair generated on the client side that acts as a temporary identity for the client application. It consists of:
     - A public key - shared with the Lit nodes
     - A secret key (private key) - kept securely on the client
@@ -59,7 +59,7 @@ Use your newly minted PKP to create an AuthContext. This method will cache two t
 
 const authContext = await authManager.createPkpAuthContext({
   authData: authData, // <-- Retrieved earlier
-  pkpPublicKey: pkpInfo.pubkey, // <-- Minted earlier
+  pkpPublicKey: pkpInfo.pubkey,
   authConfig: {
     resources: [
       ["pkp-signing", "*"],

docs/sdk/auth/pkp-native-auth/pkp-eoa-auth.mdx

@@ -38,7 +38,7 @@ description: "Externally Owned Account (EOA) authentication uses your existing E
 
   <Step title="Authenticate with EOA">
 
-Use the WalletClientAuthenticator/ViemAccountAuthenticator to authenticate your connected wallet and generate auth data.
+Use the `WalletClientAuthenticator` or `ViemAccountAuthenticator` to authenticate your connected wallet and generate auth data.
 
   <CodeGroup>
 ```ts wagmi
@@ -97,17 +97,17 @@ You can select an existing PKP associated with your account or mint a new one.
   </Step>
 
   <Step title="Generate Auth Context">
-Use your newly minted PKP to create an AuthContext. This method will cache two things:
+Use your PKP's public key to create an AuthContext. This method will cache two things:
 1. session key pair - a temporary cryptographic key pair generated on the client side that acts as a temporary identity for the client application. It consists of:
     - A public key - shared with the Lit nodes
     - A secret key (private key) - kept securely on the client
-2. Delegation AuthSig aka. the inner auth sig - a cryptographic attestation from the Lit Protocol nodes that authorises your session key to act on behalf of your PKP.
+2. Delegation AuthSig (aka. the inner auth sig) - a cryptographic attestation from the Lit Protocol nodes that authorises your session key to act on behalf of your PKP.
 
 ```ts
 
 const authContext = await authManager.createPkpAuthContext({
   authData: authData, // <-- Retrieved earlier
-  pkpPublicKey: pkpInfo.pubkey, // <-- Minted earlier
+  pkpPublicKey: pkpInfo.pubkey,
   authConfig: {
     resources: [
       ["pkp-signing", "*"],

docs/sdk/auth/pkp-native-auth/pkp-google-auth.mdx

@@ -49,7 +49,7 @@ description: "Google Authentication uses your Google account to authenticate via
   </Step>
 
     <Step title="Generate Auth Context">
-Use your newly minted PKP to create an AuthContext. This method will cache two things:
+Use your PKP's public key to create an AuthContext. This method will cache two things:
 1. session key pair - a temporary cryptographic key pair generated on the client side that acts as a temporary identity for the client application. It consists of:
     - A public key - shared with the Lit nodes
     - A secret key (private key) - kept securely on the client
@@ -59,7 +59,7 @@ Use your newly minted PKP to create an AuthContext. This method will cache two t
 
 const authContext = await authManager.createPkpAuthContext({
   authData: authData, // <-- Retrieved earlier
-  pkpPublicKey: pkpInfo.pubkey, // <-- Minted earlier
+  pkpPublicKey: pkpInfo.pubkey,
   authConfig: {
     resources: [
       ["pkp-signing", "*"],

docs/sdk/auth/pkp-native-auth/pkp-stytch-2fa-totp-auth.mdx

@@ -6,7 +6,7 @@ description: "Stytch TOTP 2FA Authentication is a secondary authentication metho
 # Prerequisites
 
 <Warning>
-  ⚠️ Backend Required: This authentication method requires a backend service
+  Backend Required: This authentication method requires a backend service
   that handles Stytch Email OTP operations. The auth service already has the
   implementation in place with the `/stytch/email/send-otp` and
   `/stytch/email/verify-otp` endpoints, but they are disabled by default. Simply
@@ -121,7 +121,7 @@ const authData = await StytchWhatsAppOtpAuthenticator.authenticate({
 
     <Step title="Generate Auth Context">
 
-Use your newly minted PKP to create an AuthContext. This method will cache two things:
+Use your PKP's public key to create an AuthContext. This method will cache two things:
 
 1. session key pair - a temporary cryptographic key pair generated on the client side that acts as a temporary identity for the client application. It consists of:
    - A public key - shared with the Lit nodes
@@ -131,7 +131,7 @@ Use your newly minted PKP to create an AuthContext. This method will cache two t
 ```ts
 const authContext = await authManager.createPkpAuthContext({
   authData: authData, // <-- Retrieved earlier
-  pkpPublicKey: pkpInfo.pubkey, // <-- Minted earlier
+  pkpPublicKey: pkpInfo.pubkey,
   authConfig: {
     resources: [
       ["pkp-signing", "*"],