diff --git a/docs/my-website/docs/exception_mapping.md b/docs/my-website/docs/exception_mapping.md
index 11671a04c0..b29f2d4b9d 100644
--- a/docs/my-website/docs/exception_mapping.md
+++ b/docs/my-website/docs/exception_mapping.md
@@ -9,7 +9,7 @@ LiteLLM maps exceptions across all providers to their OpenAI counterparts.
 - APIError 
 - APIConnectionError
 
-Base case we return APIError
+Base case we return APIConnectionError
 
 All our exceptions inherit from OpenAI's exception types, so any error-handling you have for that, should work out of the box with LiteLLM. 
 
diff --git a/docs/my-website/docs/migration.md b/docs/my-website/docs/migration.md
index 0687f53523..6ab29982e7 100644
--- a/docs/my-website/docs/migration.md
+++ b/docs/my-website/docs/migration.md
@@ -15,6 +15,7 @@ When we have breaking changes (i.e. going from 1.x.x to 2.x.x), we will document
 - *NEW* litellm client, allow users to pass api_key
     - `litellm.Litellm(api_key="sk-123")`
 - response objects now inherit from `BaseModel` (prev. `OpenAIObject`)
+- *NEW* default exception - `APIConnectionError` (prev. `APIError`)
 
 **How can we communicate changes better?**
 Tell us