diff --git a/docs/my-website/docs/tutorials/claude_code_websearch.md b/docs/my-website/docs/tutorials/claude_code_websearch.md
index cc2f79666da..46062158162 100644
--- a/docs/my-website/docs/tutorials/claude_code_websearch.md
+++ b/docs/my-website/docs/tutorials/claude_code_websearch.md
@@ -6,7 +6,7 @@ Enable Claude Code's web search tool to work with any provider (Bedrock, Azure,
 
 Add WebSearch interception to your `litellm_config.yaml`:
 
-```yaml
+```yaml showLineNumbers title="litellm_config.yaml"
 model_list:
   - model_name: bedrock-sonnet
     litellm_params:
@@ -37,7 +37,7 @@ search_tools:
 
 Create `config.yaml`:
 
-```yaml
+```yaml showLineNumbers title="config.yaml"
 model_list:
   - model_name: bedrock-sonnet
     litellm_params:
@@ -58,14 +58,14 @@ search_tools:
 
 ### 2. Start Proxy
 
-```bash
+```bash showLineNumbers title="Start LiteLLM Proxy"
 export PERPLEXITY_API_KEY=your-key
 litellm --config config.yaml
 ```
 
 ### 3. Use with Claude Code
 
-```bash
+```bash showLineNumbers title="Configure Claude Code"
 export ANTHROPIC_BASE_URL=http://localhost:4000
 export ANTHROPIC_API_KEY=sk-1234
 claude
@@ -116,12 +116,19 @@ sequenceDiagram
 
 Configure which search provider to use. LiteLLM supports multiple search providers:
 
-| Provider | Configuration |
-|----------|---------------|
-| **Perplexity** | `search_provider: perplexity` |
-| **Tavily** | `search_provider: tavily` |
+| Provider | `search_provider` Value | Environment Variable |
+|----------|------------------------|----------------------|
+| **Perplexity AI** | `perplexity` | `PERPLEXITYAI_API_KEY` |
+| **Tavily** | `tavily` | `TAVILY_API_KEY` |
+| **Exa AI** | `exa_ai` | `EXA_API_KEY` |
+| **Parallel AI** | `parallel_ai` | `PARALLEL_AI_API_KEY` |
+| **Google PSE** | `google_pse` | `GOOGLE_PSE_API_KEY`, `GOOGLE_PSE_ENGINE_ID` |
+| **DataForSEO** | `dataforseo` | `DATAFORSEO_LOGIN`, `DATAFORSEO_PASSWORD` |
+| **Firecrawl** | `firecrawl` | `FIRECRAWL_API_KEY` |
+| **SearXNG** | `searxng` | `SEARXNG_API_BASE` (required) |
+| **Linkup** | `linkup` | `LINKUP_API_KEY` |
 
-See [all supported search providers](../search/index.md) for the complete list.
+See [all supported search providers](../search/index.md) for detailed setup instructions and provider-specific parameters.
 
 ## Configuration Options
 
@@ -145,7 +152,7 @@ Use these values in `enabled_providers`:
 
 ### Complete Configuration Example
 
-```yaml
+```yaml showLineNumbers title="Complete config.yaml"
 model_list:
   - model_name: bedrock-sonnet
     litellm_params:
diff --git a/docs/my-website/release_notes/v1.81.0/index.md b/docs/my-website/release_notes/v1.81.0/index.md
index 7c7192bf24d..b5fd5068dfa 100644
--- a/docs/my-website/release_notes/v1.81.0/index.md
+++ b/docs/my-website/release_notes/v1.81.0/index.md
@@ -48,6 +48,7 @@ pip install litellm==1.81.0
 - **Claude Code** - Support for using web search across Bedrock, Vertex AI, and all LiteLLM providers
 - **Major Change** - [50MB limit on image URL downloads](#major-change---chatcompletions-image-url-download-size-limit) to improve reliability
 - **Performance** - [25% CPU Usage Reduction](#performance---25-cpu-usage-reduction) by removing premature model.dump() calls from the hot path
+- **Deleted Keys Audit Table on UI** - [View deleted keys and teams for audit purposes](../../docs/proxy/deleted_keys_teams.md) with spend and budget information at the time of deletion
 
 ---
 
@@ -143,11 +144,18 @@ This feature improves reliability by:
 
 ## Performance - 25% CPU Usage Reduction
 
-
 LiteLLM now reduces CPU usage by removing premature `model.dump()` calls from the hot path in request processing. Previously, Pydantic model serialization was performed earlier and more frequently than necessary, causing unnecessary CPU overhead on every request. By deferring serialization until it is actually needed, LiteLLM reduces CPU usage and improves request throughput under high load.
 
 ---
 
+## Deleted Keys Audit Table on UI
+
+<Image img={require('../../../img/ui_deleted_keys_table.png')} />
+
+LiteLLM now provides a comprehensive audit table for deleted API keys and teams directly in the UI. This feature allows you to easily track the spend of deleted keys, view their associated team information, and maintain accurate financial records for auditing and compliance purposes. The table displays key details including key aliases, team associations, and spend information captured at the time of deletion. For more information on how to use this feature, see the [Deleted Keys & Teams documentation](../../docs/proxy/deleted_keys_teams.md).
+
+---
+
 ## New Models / Updated Models
 
 #### New Model Support