🔄 synced local 'docs/' with remote 'docs/'

docs/cloud/browser-management/browser-profiles.mdx

@@ -21,7 +21,7 @@ Profiles are ideal when you:
 - Need multiple workflows to share the same authenticated state
 
 <Note>
-Looking to manage profiles from code? See the [API & SDK guide](/optimization/browser-profiles) instead.
+Looking to manage profiles from code? See the [API & SDK guide](/developers/optimization/browser-profiles) instead.
 </Note>
 
 ---
@@ -111,7 +111,7 @@ For sites with short-lived sessions (banks, healthcare portals), refresh profile
   <Card
     title="Browser Profiles (API)"
     icon="code"
-    href="/optimization/browser-profiles"
+    href="/developers/optimization/browser-profiles"
   >
     Create and manage profiles programmatically
   </Card>

docs/cloud/browser-management/browser-sessions.mdx

@@ -15,7 +15,7 @@ keywords:
 A **browser session** is a live browser instance that stays open between runs. Cookies, login state, cart contents, and page context all persist, like keeping a browser tab open. Use sessions when you need back-to-back tasks to share state, or when you want to interact with the browser yourself between automated steps.
 
 <Note>
-Looking to use browser sessions from code? See the [API & SDK guide](/optimization/browser-sessions) instead.
+Looking to use browser sessions from code? See the [API & SDK guide](/developers/optimization/browser-sessions) instead.
 </Note>
 
 ---
@@ -174,7 +174,7 @@ Use a session when you need a live browser right now. Use a [profile](/cloud/bro
   <Card
     title="Browser Sessions (API)"
     icon="code"
-    href="/optimization/browser-sessions"
+    href="/developers/optimization/browser-sessions"
   >
     Create and manage sessions programmatically
   </Card>