Update phone-factor-technical-profile.md

capitalization fix, per Azure style

Author: v-albemi

articles/active-directory-b2c/phone-factor-technical-profile.md

@@ -54,7 +54,7 @@ The InputClaimsTransformations element may contain a collection of input claims
 
 The InputClaims element must contain the following claims. You can also map the name of your claim to the name defined in the phone factor technical profile. 
 
-|  Data Type| Required | Description |
+|  Data type| Required | Description |
 | --------- | -------- | ----------- | 
 | string| Yes | A unique identifier for the user. The claim name, or PartnerClaimType must be set to `UserId`. This claim should not contain personal identifiable information.|
 | string| Yes | List of claim types. Each claim contains one phone number. If any of the input claims do not contain a phone number, the user will be asked to enroll and verify a new phone number. The validated phone number is returned as an output claim. If one of the input claims contain a phone number, the user is asked to verify it. If multiple input claims contain a phone number, the user is asked to choose and verify one of the phone numbers. |
@@ -73,7 +73,7 @@ The following example demonstrates using multiple phone numbers. For more inform
 
 The OutputClaims element contains a list of claims returned by the phone factor technical profile.
 
-|  Data Type| Required | Description |
+|  Data type| Required | Description |
 |  -------- | ----------- |----------- |
 | boolean | Yes | Indicates whether the new phone number has been entered by the user. The claim name, or PartnerClaimType must be set to `newPhoneNumberEntered`|
 | string| Yes | The verified phone number. The claim name, or PartnerClaimType must be set to `Verified.OfficePhone`.|