UI casing updates

rchinn1 · rchinn1 · commit 3fca8656c8f2 · 2023-03-27T10:31:12.000-07:00
diff --git a/src/unify/debugger.md b/src/unify/debugger.md
@@ -13,7 +13,7 @@ The Debugger provides you with the payload information you need to troubleshoot
 
 ## Working with the Debugger
 
-Navigate to the Debugger tab on the Unify Settings page of the space you want to debug. Select the Source you want to inspect in the Debugger.
+Navigate to the Debugger tab on the Unify settings page of the space you want to debug. Select the Source you want to inspect in the Debugger.
 
 The Debugger presents a stream of incoming events. The event inspector displays three tabs for each event:
 
diff --git a/src/unify/identity-resolution/space-setup.md b/src/unify/identity-resolution/space-setup.md
@@ -14,7 +14,7 @@ Before you connect any source to the Dev space, Segment recommends that you firs
 
 ## Step three: Set up a connection policy
 
-If you haven't already, Segment highly recommends labeling all your sources with *Dev* or *Prod* [environments](/docs/segment-app/iam/labels/). Once your sources have been labeled, visit the **Connection Policy** page by navigating to **Unify > Unify Settings > Space Management**. Here, you can enforce that only sources labeled *Dev* can be connected to your *Dev* Unify instance.
+If you haven't already, Segment highly recommends labeling all your sources with *Dev* or *Prod* [environments](/docs/segment-app/iam/labels/). Once your sources have been labeled, visit the **Connection Policy** page by navigating to **Unify > Unify settings > Space management**. Here, you can enforce that only sources labeled *Dev* can be connected to your *Dev* Unify instance.
 
 [](images/connection-policy.png)
 
@@ -23,7 +23,7 @@ If you haven't already, Segment highly recommends labeling all your sources with
 
 ## Step four: Connect sources and create test audiences
 
-Once your connection policy is in place, select the **Sources** tab in **Unify Settings**. Now you can connect a few sources that will automatically begin to replay.
+Once your connection policy is in place, select the **Profile sources** tab in **Unify settings**. Now you can connect a few sources that will automatically begin to replay.
 
 Once the sources have finished replaying, check user profiles to ensure that profiles are merging as expected. This would also be an ideal time to create test audiences and confirm that these populate the expected number of users.
 
diff --git a/src/unify/index.md b/src/unify/index.md
@@ -7,7 +7,7 @@ redirect_from:
 
 Use Segment Unify, formerly known as Profiles, for a complete view of your customers.
 
-With [Identity Resolution](#identity-resolution), track every interaction across the entire user journey to create unified, real-time customer identities. View user profiles in one place through the [Profile Explorer](#profile-explorer) in the Segment app. Use the [Profile API](#profile-api) to programmatically query user profiles, traits, and events.
+With [Identity Resolution](#identity-resolution), track every interaction across the entire user journey to create unified, real-time customer identities. View user profiles in one place through the [Profile explorer](#profile-explorer) in the Segment app. Use the [Profile API](#profile-api) to programmatically query user profiles, traits, and events.
 
 You can then use this interaction data with customer engagement tools, such as Engage, to deliver personalized, omnichannel experiences.
 
@@ -31,9 +31,9 @@ With Identity Resolution:
 
 Visit Segment's [Identity Resolution docs](/docs/unify/identity-resolution/) to learn more.
 
-## Profile Explorer
+## Profile explorer
 
-Use the Profile Explorer to view all user data, including their event history, traits, and identifiers.
+Use the Profile explorer to view all user data, including their event history, traits, and identifiers.
 
 With the Explorer, you have a complete view of your customers.
 
@@ -42,7 +42,7 @@ With the Explorer, you have a complete view of your customers.
 - **Provide sales and support context**: Look up a user profile to understand where they are on their journey with your business or product.
 
 > info ""
-> If you're using Engage, use the Profile Explorer to view audiences, traits, journey membership, and [subscription states](/docs/engage/user-subscriptions/) for email and phone numbers.
+> If you're using Engage, use the Profile explorer to view audiences, traits, journey membership, and [subscription states](/docs/engage/user-subscriptions/) for email and phone numbers.
 
 ## Profile API
 
diff --git a/src/unify/profile-api.md b/src/unify/profile-api.md
@@ -17,7 +17,7 @@ You can use this API to:
 - **Power personalized marketing campaigns** by enriching dynamic / custom properties with profile traits in marketing tools like Braze
 - **Qualify leads faster** by embedding the user event timeline in Salesforce
 
-This document has four parts: 
+This document has four parts:
 
 1. [**Product Highlights**](#product-highlights)
 2. [**Quickstart**](#quickstart): Walks you through how to get started querying your user profile in <1 min
@@ -43,17 +43,17 @@ Your access token enables you to call the Profile API and access customer data.
 > info "European Union requirements"
 > To implement the Profile API in the European Union, you must complete the following steps within an EU workspace. View the [regional Segment documentation](/docs/guides/regional-segment/#create-a-new-workspace-with-a-different-region) for more information.
 
-1.  Navigate to the API Access settings page **Unify > Unify Settings > API Access**.
+1.  Navigate to the API access settings page **Unify > Unify settings > API access**.
 
 2.  Create your **Access Token** with a name that describes your use case, for example `testing/development`. Take note of the **space ID** value, you'll pass this into the Profile API request URL in a later step.
 
 3.  Click **Generate token**. Copy the resulting **Access Token** and store it in a file on your computer. You'll pass in the **Access Token** into the Profile API for authorization as an HTTP Basic Auth username in a later step.
 
 ### Find a user's external id
 
-1. Navigate to **Unify > Profiles Explorer** and select the user you want to query through the API.
+1. Navigate to **Unify > Profile explorer** and select the user you want to query through the API.
 2. Take note of the user's available identifiers. For example, this user has an `anonymous_id` with the value `eml_3bca54b7fe7491add4c8d5d4d9bf6b3e085c6092`. The Profile API requires both the type of ID and the value separated by a colon. For example, `anonymous_id:eml_3bca54b7fe7491add4c8d5d4d9bf6b3e085c6092`. Click the duplicate icon to copy the identifier to your clipboard.   
-![Retrieving a user's identifiers with the Profiles Explorer](images/profile_api_anonymous_id.png)
+![Retrieving a user's identifiers with the Profile explorer](images/profile_api_anonymous_id.png)
 
 > warning ""
 > To query phone numbers that contain a plus sign (`+`), insert the escape characters `%2B` in place of the plus sign.
@@ -161,7 +161,7 @@ The Segment API is organized around [REST](http://en.wikipedia.org/wiki/Represen
 
 The Profile API uses basic authentication for authorization — with the **Access Token** as the authorization key. Your **Access Token** carries access to all of your customer data, so be sure to keep them secret. Don't share your Access Token in publicly accessible areas such as GitHub or client-side code.
 
-You can create your Access Secret in your Unify Settings page. Segment recommends that you name your tokens with the name of your app and its environment, such as `marketing_site/production`. Access tokens are shown once — you won't be able to see it again. In the event of a security incident, you can revoke and cycle the access token.
+You can create your Access Secret in your Unify settings page. Segment recommends that you name your tokens with the name of your app and its environment, such as `marketing_site/production`. Access tokens are shown once — you won't be able to see it again. In the event of a security incident, you can revoke and cycle the access token.
 
 When you make requests to the Profile API, use the Access Token as the basic authentication username and keep the password blank. Base64 is a requirement for authentication. If you use a tool like Postman, or if you use the `-u` flag in a cURL request, this encoding occurs automatically. Otherwise, you'll need to use Base64 to manually encode your Access Token.
 
diff --git a/src/unify/quickstart.md b/src/unify/quickstart.md
@@ -35,7 +35,7 @@ You probably have teammates who help set up your Segment Workspace with the data
 
 ## Step 3: Connect production sources
 
-1. From your Segment space, navigate to **Unify Settings** and click **Sources**.
+1. From your Segment space, navigate to **Unify settings** and click **Profile sources**.
 2. On the screen that appears, choose one or two production sources from your Connections workspace.
    Segment recommends connecting your production website or App source as a great starting point.
 
@@ -57,11 +57,11 @@ Once the Source(s) finish replaying, data from your connected Sources flows into
 
 ## Step 4: Check your profile data
 
-Once the replay finishes, you can see the data replayed into Unify using the Profile Explorer. You should have a lot! The data should include information from multiple sources and multiple sessions, all resolved into a single profile per user.
+Once the replay finishes, you can see the data replayed into Unify using the Profile explorer. You should have a lot! The data should include information from multiple sources and multiple sessions, all resolved into a single profile per user.
 
 Before you continue, check a few user profiles to make sure they show an accurate and recent snapshot of your users.
 
-A good test is to look at _your own_ user profile, and maybe some colleagues' profiles. Look in the Profile Explorer for your Profile, and look at your event history, custom traits and identifiers. If these identifiers look correct across a few different profiles (and you can verify that they are all correct), then you're ready to create an audience.
+A good test is to look at _your own_ user profile, and maybe some colleagues' profiles. Look in the Profile explorer for your Profile, and look at your event history, custom traits and identifiers. If these identifiers look correct across a few different profiles (and you can verify that they are all correct), then you're ready to create an audience.
 
 If your user profiles look wrong, or you aren't confident users are being accurately defined and merged, stop here and troubleshoot. It's important to have accurate identity resolution before you continue. See the [detailed Identity Resolution documentation](/docs/unify/identity-resolution/) to better understand how it works, and why you may be running into problems. (Still need help? [Contact Segment](https://segment.com/help/contact/){:target="_blank"} for assistance.)
 
