Minor change

Author: yoelhor

articles/active-directory-b2c/custom-policy-rest-api-intro.md

@@ -77,7 +77,7 @@ The output claims parsed by the RESTful claims provider always expect to parse a
 ```json
 {
   "name": "Emily Smith",
-  "email": "emily@contoso.com",
+  "email": "emily@outlook.com",
   "loyaltyNumber":  1234
 }
 ```
@@ -176,7 +176,6 @@ Design your REST API service and its underlying components (such as the database
 
 See the following articles for examples of using a RESTful technical profile:
 
-- [Integrate REST API claims exchanges in your Azure AD B2C custom policy](custom-policy-rest-api-intro.md)
 - [Walkthrough: Integrate REST API claims exchanges in your Azure AD B2C user journey as validation of user input](custom-policy-rest-api-claims-validation.md)
 - [Walkthrough: Add REST API claims exchanges to custom policies in Azure Active Directory B2C](custom-policy-rest-api-claims-validation.md)
 - [Secure your REST API services](secure-rest-api.md)