renamed domains & handlers to domains

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/domains/page-client.tsx

@@ -230,7 +230,7 @@ export default function PageClient() {
 
 
   return (
-    <PageLayout title="Domains and Handler">
+    <PageLayout title="Domains">
       <SettingCard
         title="Trusted domains"
         description="Features that will redirect to your app, such as SSO and e-mail verification, will refuse to redirect to domains other than the ones listed here. Please make sure that you trust all domains listed here, as they can be used to access user data."

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/domains/page.tsx

@@ -1,7 +1,7 @@
 import PageClient from "./page-client";
 
 export const metadata = {
-  title: "Domains & Handlers",
+  title: "Domains",
 };
 
 export default function Page() {

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/sidebar-layout.tsx

@@ -139,7 +139,7 @@ const navigationItems: (Label | Item | Hidden)[] = [
     type: 'label'
   },
   {
-    name: "Domains & Handlers",
+    name: "Domains",
     href: "/domains",
     regex: /^\/projects\/[^\/]+\/domains$/,
     icon: LinkIcon,

docs/fern/docs/pages/getting-started/production.mdx

@@ -5,7 +5,7 @@ subtitle: Steps to prepare Stack for production use
 
 Stack makes development easy with various default settings, but these settings need to be optimized for security and user experience when moving to production. Here's a checklist of things you need to do before switching to production mode:
 
-### Domains and handlers
+### Domains
 
 By default, Stack allows all localhost paths as valid callback URLs. This is convenient for development but poses a security risk in production because attackers could use their own domains as callback URLs to intercept sensitive information. Therefore, in production, Stack must know your domain (e.g., `https://your-website.com`) and only allow callbacks from those domains.