Fix grammatical errors in route53-cloudfront.mdx

deploy/route53-cloudfront.mdx

@@ -23,7 +23,7 @@
 - `/mintlify-assets/_next/static/*`
 - `Default (*)`	- Your website's landing page
 
-All Behaviors must have the an **origin request policy** of `AllViewerExceptHostHeader`.
+All Behaviors must have an **origin request policy** of `AllViewerExceptHostHeader`.
 
 ![CloudFront "Behaviors" page with 4 behaviors: `/docs/*`, `/docs`, `Default`, and `/.well-known/*`.](/images/cloudfront/all-behaviors.png)
 
@@ -39,13 +39,13 @@
 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)
   </Frame>
 
 4. For "Web Application Firewall (WAF)," enable security protections.
 
   <Frame>
     ![Web Application Firewall (WAF) options with "Enable security protections" selected.](/images/cloudfront/enable-security-protections.png)
   </Frame>
 
 5. The remaining settings should be default.
@@ -59,10 +59,10 @@
     ![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).
 
 <Info>
   If your landing page is hosted on Webflow, use Webflow's staging URL. It would look like `.webflow.io`.
 
   If you use Vercel, use the `.vercel.app` domain available for every project.
 </Info>
@@ -84,7 +84,7 @@
 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 your custom subpath**, go to `[SUBDOMAIN].mintlify.dev`.
-- **If a user lands on any other page**, go the current landing page.
+- **If a user lands on any other page**, go to the current landing page.
 
 1. Navigate to the "Behaviors" tab of your CloudFront distribution.
 
@@ -105,21 +105,21 @@
 </Frame>
 
 <Info>
 If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a minimum for Vercel:
   - `/.well-known/vercel/*` - Required for Vercel domain verification
   - `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
 </Info>
 
 ### Your subpath
 
 Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.dev` URL (in our case `acme.mintlify.dev`).
 
 - Set "Cache policy" to **CachingOptimized**.
 - Set "Origin request policy" to **AllViewerExceptHostHeader**.
 - 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)
 </Frame>
 
 ### Your subpath with wildcard
@@ -143,10 +143,10 @@
 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)
 </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)
@@ -154,7 +154,7 @@
 
 2. Select **Save changes**.
 
 ### Check behaviors are set up correctly
 
 If you follow the preceding steps, your behaviors should look like this:
 
@@ -164,7 +164,7 @@
 
 ## 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)
@@ -172,9 +172,9 @@
 
 All pages should be directing to your main landing page, but if you append your chosen subpath, for example `/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.
 
 <Note>
   For this section, you can also refer to AWS's official guide on [Configuring