Sentence case fixes

Author: rchinn1

src/personas/identity-resolution/personas-space-set-up.md

@@ -13,7 +13,7 @@ When starting with Personas, begin by creating a *Dev* space. This will be your
 
 Before you connect any source to the Dev space, Segment recommends that you first start by reviewing and configuring your Identity settings, as changes to the Identity rules will only be applied to new events received following any updates. Read more on those settings [here](/docs/personas/identity-resolution/identity-resolution-settings/).
 
-## Step three: Set up a Connection Policy
+## 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, navigate to the Connection Policy page in the Personas space settings. Here, you can enforce that only sources labeled *Dev* can be connected to your *Dev* Personas instance.
 
@@ -22,16 +22,16 @@ If you haven't already, Segment highly recommends labeling all your sources with
 > note ""
 > **Note:** The Identity Resolution table can only be edited by workspace owners and users with the Identity Admin role.
 
-## Step four: Connect Sources and create test Audiences
+## Step four: Connect sources and create test audiences
 
-Once your Connection Policy is in place, click on the Sources tab in space settings. Now you can connect a few Sources that will automatically begin to replay.
+Once your connection policy is in place, click on the Sources tab in space 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.
+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.
 
-## Step five: Connect Audiences to a Dev instance of a downstream destination
+## Step five: Connect audiences to a Dev instance of a downstream destination
 
 Connect test audiences or traits to a dev instance of your downstream destination. Confirm that users are appearing as expected.
 
-## Step six: Apply changes to Prod Sources
+## Step six: Apply changes to Prod sources
 
 Once everything looks good to go, create a new *Prod* space, following all the same steps above, and connect a live instance of your downstream destination to your *Prod* space.