From d2fc94fc136d40dc52aa0e223400e65d16711c23 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Sat, 16 May 2026 20:05:01 +0000
Subject: [PATCH] docs: align voice and tone with style guide in three pages
---
customize/custom-scripts.mdx | 2 +-
deploy/ghes.mdx | 4 ++--
deploy/route53-cloudfront.mdx | 10 +++++-----
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/customize/custom-scripts.mdx b/customize/custom-scripts.mdx
index c475b449ab..8e271fe170 100644
--- a/customize/custom-scripts.mdx
+++ b/customize/custom-scripts.mdx
@@ -360,5 +360,5 @@ gtag('config', 'TAG_ID');
```
- Please use with caution to not introduce security vulnerabilities.
+ Use with caution to avoid introducing security vulnerabilities.
\ No newline at end of file
diff --git a/deploy/ghes.mdx b/deploy/ghes.mdx
index 7856159322..fba049dc53 100644
--- a/deploy/ghes.mdx
+++ b/deploy/ghes.mdx
@@ -150,7 +150,7 @@ Configure the following:
## Share credentials with us
-Please share the following information with our team using your secure information transfer method of choice.
+Share the following information with our team using your secure information transfer method of choice.
### Required credentials
- GitHub Enterprise Server base URL: https://your-github-server.com
@@ -247,7 +247,7 @@ No, your GHES must be able to communicate with our cloud-hosted server.
-Please reach out to your customer success representative who you've spoken to at Mintlify, or our support team at support@mintlify.com with:
+Reach out to your customer success representative at Mintlify, or contact our support team at support@mintlify.com with:
- Your GitHub Enterprise Server version.
- Specific error messages.
diff --git a/deploy/route53-cloudfront.mdx b/deploy/route53-cloudfront.mdx
index d63db1249d..e3482d8ef8 100644
--- a/deploy/route53-cloudfront.mdx
+++ b/deploy/route53-cloudfront.mdx
@@ -81,7 +81,7 @@ By this point, you should have two Origins: one with `[SUBDOMAIN].mintlify.app`
## 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, you 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 to the current landing page.
@@ -112,7 +112,7 @@ If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a m
### 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`).
+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 (for example, `acme.mintlify.dev`).
- Set "Cache policy" to **CachingOptimized**.
- Set "Origin request policy" to **AllViewerExceptHostHeader**.
@@ -140,13 +140,13 @@ These settings should exactly match your base subpath behavior. With the excepti
### `Default (*)`
-Lastly, we're going to edit the `Default (*)` behavior.
+Lastly, edit the `Default (*)` behavior.
-1. Change the default behavior's **Origin and origin groups** to the staging URL (in our case `mintlify-landing-page.vercel.app`).
+1. Change the default behavior's **Origin and origin groups** to the staging URL (for example, `mintlify-landing-page.vercel.app`).
@@ -174,7 +174,7 @@ All pages should be directing to your main landing page, but if you append your
## Connect with Route 53
-Now, we're going to bring the capabilities of the CloudFront distribution into your primary domain.
+Now, bring the capabilities of the CloudFront distribution into your primary domain.
For this section, you can also refer to AWS's official guide on [Configuring