Update user-profile-attributes.md

Author: itechedit

articles/active-directory-b2c/user-profile-attributes.md

@@ -15,7 +15,7 @@ ms.subservice: B2C
 
 # User profile attributes
 
-Your Azure AD B2C directory user profile comes with a built-in set of attributes, such as given name, surname, city, postal code, and phone number. You can extend the user profile with your own application data without requiring an external data store. Most of the attributes that can be used with Azure AD B2C user profiles are also supported by Microsoft Graph. This article describes supported Azure AD B2C user profile attributes. It also notes those attributes that are not supported by Microsoft Graph, as well as Microsoft Graph attributes that should not be used with Azure AD B2C.
+Your Azure Active Directory (Azure AD) B2C directory user profile comes with a built-in set of attributes, such as given name, surname, city, postal code, and phone number. You can extend the user profile with your own application data without requiring an external data store. Most of the attributes that can be used with Azure AD B2C user profiles are also supported by Microsoft Graph. This article describes supported Azure AD B2C user profile attributes. It also notes those attributes that are not supported by Microsoft Graph, as well as Microsoft Graph attributes that should not be used with Azure AD B2C.
 
 > [!IMPORTANT]
 > You should not use built-in or extension attributes to store sensitive personal data, such as account credentials, government identification numbers, cardholder data, financial account data, healthcare information, or sensitive background information.
@@ -56,7 +56,7 @@ The table below lists the [user resource type](https://docs.microsoft.com/graph/
 |mailNickName    |String|The mail alias for the user. Max length 64.|No|No|Persisted, Output|
 |mobile (mobilePhone) |String|The primary cellular telephone number for the user. Max length 64.|Yes|No|Persisted, Output|
 |netId           |String|Net ID.|No|No|Persisted, Output|
-|objectId        |String|A Guid that is the unique identifier for the user. Example: 12345678-9abc-def0-1234-56789abcde. Read only, Immutable.|Read only|Yes|Input, Persisted, Output|
+|objectId        |String|A globally unique identifier (GUID) that is the unique identifier for the user. Example: 12345678-9abc-def0-1234-56789abcde. Read only, Immutable.|Read only|Yes|Input, Persisted, Output|
 |otherMails      |String collection|A list of additional email addresses for the user. Example: ["[email protected]", "[email protected]"].|Yes (Alternate email)|No|Persisted, Output|
 |password        |String|The password for the local account during user creation.|No|No|Persisted|
 |passwordPolicies     |String|Policy of the password. It's a string consisting of different policy name separated by comma. i.e. "DisablePasswordExpiration, DisableStrongPassword".|No|No|Persisted, Output|
@@ -93,16 +93,15 @@ You’ll often need to create your own attributes, as in the following cases:
 
 Azure AD B2C extends the set of attributes stored on each user account. Extension attributes [extend the schema](https://docs.microsoft.com/graph/extensibility-overview#schema-extensions) of the user objects in the directory. The extension attributes can only be registered on an application object, even though they might contain data for a user. The extension attribute is attached to the application called b2c-extensions-app. Do not modify this application, as it's used by Azure AD B2C for storing user data. You can find this application under Azure Active Directory App registrations.
 
-Notes:
-
-- Up to 100 extension attributes can be written to any user account.
-- If the b2c-extensions-app application is deleted, those extension attributes are removed from all users along with any data they contain.
-- If an extension attribute is deleted by the application, it's removed from all user accounts and the values are deleted.
-- The underlying name of the extension attribute is generated in the format "Extension_" + Application ID + "_" + Attribute name. For example, if you create an extension attribute LoyaltyNumber, and the b2c-extensions-app Application ID is 831374b3-bd50-41bf-aa54-263ec9e050fc, the underlying extension attribute name will be: extension_831374b3bd5041bfaa54263ec9e050fc_LoyaltyNumber. You use the underlying name when you run Graph API queries to create or update user accounts.
+> [!NOTE]
+> - Up to 100 extension attributes can be written to any user account.
+> - If the b2c-extensions-app application is deleted, those extension attributes are removed from all users along with any data they contain.
+> - If an extension attribute is deleted by the application, it's removed from all user accounts and the values are deleted.
+> - The underlying name of the extension attribute is generated in the format "Extension_" + Application ID + "_" + Attribute name. For example, if you create an extension attribute LoyaltyNumber, and the b2c-extensions-app Application ID is 831374b3-bd50-41bf-aa54-263ec9e050fc, the underlying extension attribute name will be: extension_831374b3bd5041bfaa54263ec9e050fc_LoyaltyNumber. You use the underlying name when you run Graph API queries to create or update user accounts.
 
 The following data types are supported when defining a property in a schema extension:
 
-|Property Type |Remarks  |
+|Property type |Remarks  |
 |--------------|---------|
 |Boolean    | Possible values: **true** or **false**. |
 |DateTime   | Must be specified in ISO 8601 format. Will be stored in UTC.   |