spelling: correct Cloudfront -> CloudFront

Author: cdxker

advanced/subpath/route53-cloudfront.mdx

@@ -1,12 +1,12 @@
 ---
-title: "AWS Route 53 and Cloudfront"
+title: "AWS Route 53 and CloudFront"
 sidebarTitle: "AWS"
 description: "Host documentation at a /docs subdirectory using AWS services"
 ---
 
 import Propagating from "/snippets/custom-subpath-propagating.mdx";
 
-To host your documentation at a `/docs` subpath using AWS Route 53 and Cloudfront, you need to configure your DNS provider to point to your Cloudfront distribution.
+To host your documentation at a `/docs` subpath using AWS Route 53 and CloudFront, you need to configure your DNS provider to point to your CloudFront distribution.
 
 ## Proxies with Vercel deployments
 
@@ -32,19 +32,19 @@ You must create a custom origin request policy that forwards the `HOST` header a
 
 You must include the `CloudFront-Viewer-Address` header in your origin request policy or cache policy headers configuration to forward the header to your origin.
 
-## Create Cloudfront distribution
+## Create CloudFront distribution
 
-1. Navigate to [Cloudfront](https://aws.amazon.com/cloudfront) inside the AWS console.
+1. Navigate to [CloudFront](https://aws.amazon.com/cloudfront) inside the AWS console.
 2. Select **Create distribution**.
 
   <Frame>
-    ![Cloudfront Distributions page with the "Create distribution" button emphasized.](/images/cloudfront/create-distribution.png)
+    ![CloudFront Distributions page with the "Create distribution" button emphasized.](/images/cloudfront/create-distribution.png)
   </Frame>
 
 3. For the Origin domain, input `[SUBDOMAIN].mintlify.dev` where `[SUBDOMAIN]` is your project's unique subdomain.
 
   <Frame>
-    ![Cloudfront "Create distribution" page showing "acme.mintlify.dev" as the origin domain.](/images/cloudfront/origin-name.png)
+    ![CloudFront "Create distribution" page showing "acme.mintlify.dev" as the origin domain.](/images/cloudfront/origin-name.png)
   </Frame>
 
 4. For "Web Application Firewall (WAF)," enable security protections.
@@ -61,7 +61,7 @@ You must include the `CloudFront-Viewer-Address` header in your origin request p
 1. After creating the distribution, navigate to the "Origins" tab.
 
   <Frame>
-    ![A Cloudfront distribution with the "Origins" tab highlighted.](/images/cloudfront/origins.png)
+    ![A CloudFront distribution with the "Origins" tab highlighted.](/images/cloudfront/origins.png)
   </Frame>
 
 2. Find your staging URL that mirrors the main domain. This is highly variant depending on how your landing page is hosted. For example, the Mintlify staging URL is [mintlify-landing-page.vercel.app](https://mintlify-landing-page.vercel.app).
@@ -75,26 +75,26 @@ You must include the `CloudFront-Viewer-Address` header in your origin request p
 3. Create a new Origin and add your staging URL as the "Origin domain".
 
   <Frame>
-    ![Cloudfront "Create origin" page with a "Origin domain" input field highlighted.](/images/cloudfront/default-origin.png)
+    ![CloudFront "Create origin" page with a "Origin domain" input field highlighted.](/images/cloudfront/default-origin.png)
   </Frame>
 
 By this point, you should have two Origins: one with `[SUBDOMAIN].mintlify.app` and another with your staging URL.
 
 <Frame>
-  ![Cloudfront "Origins" page with two origins: One for `mintlify` and another for `mintlify-landing-page`.](/images/cloudfront/final-origins.png)
+  ![CloudFront "Origins" page with two origins: One for `mintlify` and another for `mintlify-landing-page`.](/images/cloudfront/final-origins.png)
 </Frame>
 
 ## Set behaviors
 
-Behaviors in Cloudfront enable control over the subpath logic. At a high level, we're looking to create the following logic.
+Behaviors in CloudFront enable control over the subpath logic. At a high level, we're looking to create the following logic.
 
 - **If a user lands on /docs**, go to `[SUBDOMAIN].mintlify.dev`.
 - **If a user lands on any other page**, go the current landing page.
 
-Navigate to the "Behaviors" tab of your Cloudfront distribution.
+Navigate to the "Behaviors" tab of your CloudFront distribution.
 
 <Frame>
-	![Cloudfront "Behaviors" tab highlighted.](/images/cloudfront/behaviors.png)
+	![CloudFront "Behaviors" tab highlighted.](/images/cloudfront/behaviors.png)
 </Frame>
 
 Select the **Create behavior** button and create the following behaviors.
@@ -106,7 +106,7 @@ Create behaviors for Vercel domain verification paths with a **Path pattern** of
 For "Cache policy", select **CachingDisabled** to ensure these verification requests pass through without caching.
 
 <Frame>
-  ![Cloudfront "Create behavior" page with a "Path pattern" of "/.well-known/*" and "Origin and origin groups" pointing to the staging URL.](/images/cloudfront/well-known-policy.png)
+  ![CloudFront "Create behavior" page with a "Path pattern" of "/.well-known/*" and "Origin and origin groups" pointing to the staging URL.](/images/cloudfront/well-known-policy.png)
 </Frame>
 
 <Info>
@@ -120,16 +120,16 @@ If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a m
 Create a behavior with a **Path pattern** of `/docs` with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`).
 
 - Set "Cache policy" to **CachingOptimized**.
-- In "Origin request policy". Create an origin request policy named **VercelCloudFrontProxy**. That forward the `Origin` and `CloudFront-Viewer-Address` headers.
+- In "Origin request policy", create an origin request policy named **VercelCloudFrontProxy**. That forwards the `Origin` and `CloudFront-Viewer-Address` headers.
 
 <Frame>
-	![Cloudfront Create origin request policy page that forwards the `Origin` and `CloudFront-Viewer-Address` headers](/images/cloudfront/origin-request-policy.png)
+	![CloudFront Create origin request policy page that forwards the `Origin` and `CloudFront-Viewer-Address` headers](/images/cloudfront/origin-request-policy.png)
 </Frame>
 
 - Set Viewer Protocol Policy to **Redirect HTTP to HTTPS**
 
 <Frame>
-  ![Cloudfront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.dev` URL.](/images/cloudfront/behavior-1.png)
+  ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.dev` URL.](/images/cloudfront/behavior-1.png)
 </Frame>
 
 ### `/docs/*`
@@ -147,13 +147,13 @@ These settings should exactly match `/docs`. With the exception of the **Path pa
 Lastly, we're going to edit the `Default (*)` behavior.
 
 <Frame>
-  ![A Cloudfront distribution with the "Default (*)" behavior selected and the Edit button emphasized.](/images/cloudfront/default-behavior-1.png)
+  ![A CloudFront distribution with the "Default (*)" behavior selected and the Edit button emphasized.](/images/cloudfront/default-behavior-1.png)
 </Frame>
 
 1. Change the default behavior's **Origin and origin groups** to the staging URL (in our case `mintlify-landing-page.vercel.app`).
 
 <Frame>
-  ![Cloudfront "Edit behavior" page with the "Origin and origin groups" input field highlighted.](/images/cloudfront/default-behavior-2.png)
+  ![CloudFront "Edit behavior" page with the "Origin and origin groups" input field highlighted.](/images/cloudfront/default-behavior-2.png)
 </Frame>
 
 2. Select **Save changes**.
@@ -163,22 +163,22 @@ Lastly, we're going to edit the `Default (*)` behavior.
 If you follow the above steps, your behaviors should look like this:
 
 <Frame>
-  ![Cloudfront "Behaviors" page with 4 behaviors: `/docs/*`, `/docs`, `Default`, and `/.well-known/*`.](/images/cloudfront/all-behaviors.png)
+  ![CloudFront "Behaviors" page with 4 behaviors: `/docs/*`, `/docs`, `Default`, and `/.well-known/*`.](/images/cloudfront/all-behaviors.png)
 </Frame>
 
 ## Preview distribution
 
 You can now test if your distribution is set up properly by going to the "General" tab and visiting the **Distribution domain name** URL.
 
 <Frame>
-  ![Cloudfront "General" tab with the "Distribution domain name" URL highlighted.](/images/cloudfront/preview-distribution.png)
+  ![CloudFront "General" tab with the "Distribution domain name" URL highlighted.](/images/cloudfront/preview-distribution.png)
 </Frame>
 
 All pages should be directing to your main landing page, but if you append `/docs` to the URL, you should see it going to your Mintlify documentation instance.
 
 ## Connect with Route53
 
-Now, we're going to bring the functionality of the Cloudfront distribution into your primary domain.
+Now, we're going to bring the functionality of the CloudFront distribution into your primary domain.
 
 <Note>
   For this section, you can also refer to AWS's official guide on [Configuring