From 0ac6b8d9bcd748217dcb0ca6c8f551dd4d07fcd3 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Thu, 25 Jul 2024 14:31:01 -0400
Subject: [PATCH] Apply suggestions from code review
Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com>
---
src/_includes/content/domain-delegation-solutions.md | 2 +-
.../catalog/libraries/website/javascript/custom-proxy.md | 2 +-
src/connections/sources/custom-domain.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/_includes/content/domain-delegation-solutions.md b/src/_includes/content/domain-delegation-solutions.md
index 524e486837..9f6f4ab726 100644
--- a/src/_includes/content/domain-delegation-solutions.md
+++ b/src/_includes/content/domain-delegation-solutions.md
@@ -5,7 +5,7 @@ Segment offers two domain delegation solutions: [Custom Proxy](/docs/connections
| Service | How it works | Infrastructure management | Availability |
| ------- | ------------ | ------------------------- | ------------ |
| Custom Domain with DNS Delegation | A Segment service that allows your website to use your own subdomain to load Analytics.js securely over HTTPS and send event data. It is not limited to Analytics.js and is also compatible with server libraries. It uses a DNS subdomain that you delegate to Segment.* | **Segment manages all related infrastructure**, including applying security updates, managing the SSL certificate lifecycle, and monitoring. | Business Tier
Recommended for reliable data collection. |
-| Custom Domain with CNAME | This approach uses a Cannonical Name (CNAME) to map an alias name on your domain name to Analytics.js. It is not limited to Analytics.js and is also compatible with server libraries. | Customers are responsible for maintaining CNAME. | Business Tier
Not recommended due to evolving and persistent browser privacy measures. |
+| Custom Domain with CNAME | This approach uses a Canonical Name (CNAME) to map an alias name on your domain name to Analytics.js. It is not limited to Analytics.js and is also compatible with server libraries. | Customers are responsible for maintaining CNAME. | Business Tier
Not recommended due to evolving and persistent browser privacy measures. |
| Custom Proxy | This approach uses a proxy or wrapper where all data is first collected by a proxy on your domain and then forwarded to Segment. | Customers are responsible for maintaining their own proxy infrastructure. | Available to all Segment users.
Not recommended because it adds a point of failure, but remains an option if Custom Domain with sub-domain delegation is unavailable to you. |
*_If it's not possible for you to delegate subdomains to Segment, you can use a CNAME instead. Segment encourages users to delegate a DNS subdomain rather than use use CNAME aliasing due to the evolving privacy standards in browsers, but CNAME aliasing remains an option for users not interested in using nameservers._
\ No newline at end of file
diff --git a/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md b/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
index 414a737970..27e024a067 100644
--- a/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
+++ b/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
@@ -6,7 +6,7 @@ strat: ajs
Custom proxies allow you to proxy Analytics.js and all tracking event requests through your own domain.
-You cannot use custom proxy setup for Analytics.js CDN or Tracking API with device-mode destinations because it requires the destination's native scripts are loaded onto the client, and the requests are sent directly to the destination.
+You cannot use custom proxy setup for Analytics.js CDN or Tracking API with device-mode destinations because it requires that the destination's native scripts are loaded onto the client, and the requests are sent directly to the destination.
> info "Business Tier customers can also use Custom Domain"
> Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS to track event requests through your domain instead of tracking events through Segment's default domain. For more information, see the [Custom Domain](/docs/connections/sources/custom-domain) documentation.
diff --git a/src/connections/sources/custom-domain.md b/src/connections/sources/custom-domain.md
index 94ceac323d..f0fc7e11e0 100644
--- a/src/connections/sources/custom-domain.md
+++ b/src/connections/sources/custom-domain.md
@@ -4,7 +4,7 @@ plan: custom-domain
hidden: true
---
-Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS. You can then track event requests through your own domain (for example, cdp.mydomain.com), instead of the default (segment.com). Tracking events through your own domain allows for more secure and complete first-party data collection by reclaiming first-party data lost to browser controls. With a more complete view of your customer behaviors, you can build more robust profiles for greater attribution and ROAS.
+Custom Domain is a fully-managed service that enables you to configure a first-party subdomain over HTTPS. You can then track event requests through your own domain (for example, `cdp.mydomain.com`), instead of the default (`segment.com`). Tracking events through your own domain allows for more secure and complete first-party data collection by reclaiming first-party data lost to browser controls. With a more complete view of your customer behaviors, you can build more robust profiles for greater attribution and ROAS.
