Fix grammar & typos: custom developer portals page

deploy/custom-portal.mdx

@@ -8,7 +8,7 @@
   Custom portals require an [Enterprise plan](https://mintlify.com/pricing?ref=custom-portal) and a [self-hosted deployment](/deploy/self-host). Reach out to your account team to scope one.
 </Info>
 
-For some platforms, documentation is one surface of a larger product—an API marketplace, a partner portal, or a developer experience with sign-in, credentials, and support built in. Mintlify supports those use cases by designing, building, and maintaining a  custom presentation layer that replaces your existing portal front end, while your team authors content through the Mintlify editor or a Git-backed workflow.
+For some platforms, documentation is one surface of a larger product—an API marketplace, a partner portal, or a developer experience with sign-in, credentials, and support built in. Mintlify supports those use cases by designing, building, and maintaining a custom presentation layer that replaces your existing portal front end, while your team authors content through the Mintlify editor or a Git-backed workflow.
 
 The portal integrates with your existing APIs, gateway, and downstream systems, which remain owned and operated by your team.
 
@@ -33,7 +33,7 @@
 
 ## Architecture
 
 The custom presentation layer integrates with the self-hosted Mintlify platform for content, search, and personalization; your API gateway for applications, subscriptions, and support; and your identity provider for authentication.
 
 ```mermaid
 flowchart TD
@@ -47,7 +47,7 @@
   ED --> PLAT
 ```
 
 The custom presentation layer and Mintlify platform run inside your network boundary, using your cluster, data stores, and observability stack, with no third-party egress. Your downstream systems of record remain unchanged; the portal accesses them through your existing APIs.
 
 ## How the engagement runs
 
@@ -62,11 +62,11 @@
     Sign-in, credential management, subscriptions, and other logged-in experiences follow, integrated with your identity provider and backend APIs.
   </Step>
   <Step title="Search, personalization, and AI">
-    Login-aware search and server-side personalization complete the core experience. Optional AI features remain disabled disabled until your security or AI governance team approves them.
+    Login-aware search and server-side personalization complete the core experience. Optional AI features remain disabled until your security or AI governance team approves them.
   </Step>
 </Steps>
 
 Throughout, your team reviews releases in non-production environments and controls every cutover.
 
 ## Next steps