Merge branch 'main' into migration

Author: Deland-Han

.openpublishing.redirection.json

@@ -244,7 +244,7 @@ If you reference a REST API technical profile directly from a user journey, the
 
 ## Development of your REST API 
 
-Your REST API can be developed on any platform and written in any programing language, as long as it's secure and can send and receive claims in JSON format.
+Your REST API can be developed on any platform and written in any programming language, as long as it's secure and can send and receive claims in JSON format.
 
 The request to your REST API service comes from Azure AD B2C servers. The REST API service must be published to a publicly accessible HTTPS endpoint. The REST API call arrives from an Azure data center IP address.
 

articles/active-directory-b2c/api-connectors-overview.md

@@ -325,7 +325,7 @@ The **DateTimeDropdown** user input type is used to provide a set of drop-downs
 
 The **RadioSingleSelect** user input type is used to provide a collection of radio buttons that allows the user to select one option.
 
-![Using claim type with radiodsingleselect](./media/claimsschema/radiosingleselect.png)
+![Using claim type with radiosingleselect](./media/claimsschema/radiosingleselect.png)
 
 ```xml
 <ClaimType Id="color">

articles/active-directory-b2c/claimsschema.md

@@ -190,7 +190,7 @@ Your final configuration file should look like the following JSON:
 ```json
 {
     "credentials": {
-        "tenantName": "<your-tenant-namee>",
+        "tenantName": "<your-tenant-name>",
         "clientID": "<your-webapi-application-ID>",
         "issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
     },

articles/active-directory-b2c/configure-authentication-sample-angular-spa-app.md

@@ -41,7 +41,7 @@ In the [Azure AD B2C samples GitHub repository](https://github.com/azure-ad-b2c/
 
 ### Claims
 
-A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programing language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims. 
+A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programming language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims. 
 
 When the policy runs, Azure AD B2C sends and receives claims to and from internal and external parties and then sends a subset of these claims to your relying party application as part of the token. Claims are used in these ways: 
 

articles/active-directory-b2c/custom-policy-overview.md

@@ -71,7 +71,7 @@ To use a session provider in your technical profile:
 
     ```xml
     <TechnicalProfile Id="SM-AAD">
-      <DisplayName>Session Mananagement Provider</DisplayName>
+      <DisplayName>Session Management Provider</DisplayName>
       <Protocol Name="Proprietary" Handler="Web.TPEngine.SSO.DefaultSSOSessionProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
       <PersistedClaims>
         <PersistedClaim ClaimTypeReferenceId="objectId" />

articles/active-directory-b2c/custom-policy-reference-sso.md

@@ -36,7 +36,7 @@ Create a JSON single element array from a claim value. Check out the [Live demo]
 The following example creates a JSON single array. 
 
 ```xml
-<ClaimsTransformation Id="createlJsonPayload" TransformationMethod="CreateJsonArray">
+<ClaimsTransformation Id="CreateJsonPayload" TransformationMethod="CreateJsonArray">
   <InputClaims>
     <InputClaim ClaimTypeReferenceId="email" TransformationClaimType="inputClaim" />
   </InputClaims>
@@ -315,7 +315,7 @@ In the following example, the claims transformation extracted the `emailAddress`
 The GetClaimFromJson claims transformation gets a single element from a JSON data. In the preceding example, the emailAddress. To get the displayName, create another claims transformation. For example:
 
 ```xml
-<ClaimsTransformation Id="GetDispalyNameClaimFromJson" TransformationMethod="GetClaimFromJson">
+<ClaimsTransformation Id="GetDisplayNameClaimFromJson" TransformationMethod="GetClaimFromJson">
   <InputClaims>
     <InputClaim ClaimTypeReferenceId="customUserData" TransformationClaimType="inputJson" />
   </InputClaims>
@@ -593,7 +593,7 @@ In the following example, the claims transformation extracts the first element (
 
 - Output claims:
   - **key**: givenName
-  - **value**: Emilty
+  - **value**: Emily
 
 
 ## GetSingleValueFromJsonArray
@@ -637,7 +637,7 @@ Convert XML data to JSON format. Check out the [Live demo](https://github.com/az
 ```xml
 <ClaimsTransformation Id="ConvertXmlToJson" TransformationMethod="XmlStringToJsonString">
   <InputClaims>
-    <InputClaim ClaimTypeReferenceId="intpuXML" TransformationClaimType="xml" />
+    <InputClaim ClaimTypeReferenceId="inputXML" TransformationClaimType="xml" />
   </InputClaims>
   <OutputClaims>
     <OutputClaim ClaimTypeReferenceId="outputJson" TransformationClaimType="json" />

articles/active-directory-b2c/json-transformations.md

@@ -50,7 +50,7 @@ The following example shows a technical profile for `JwtIssuer`:
 
 ## Input, output, and persist claims
 
-The **InputClaims**, **OutputClaims**, and **PersistClaims** elements are empty or absent. The **InutputClaimsTransformations** and **OutputClaimsTransformations** elements are also absent.
+The **InputClaims**, **OutputClaims**, and **PersistClaims** elements are empty or absent. The **InputClaimsTransformations** and **OutputClaimsTransformations** elements are also absent.
 
 ## Metadata
 

articles/active-directory-b2c/jwt-issuer-technical-profile.md

@@ -161,7 +161,7 @@ The ElementType reference to a claim type, a claim transformation, or a user int
 | Identity provider name |`ClaimsProvider`| | The ID of the ClaimsExchange element|
 | Claim type attributes|`ClaimType`|Name of the claim type| The attribute of the claim to be localized. Possible values: `AdminHelpText`, `DisplayName`, `PatternHelpText`, and `UserHelpText`.|
 |Error message|`ErrorMessage`||The ID of the error message |
-|Copies localized strings into claims|`GetLocalizedStringsTra nsformationClaimType`||The name of the output claim|
+|Copies localized strings into claims|`GetLocalizedStringsTransformationClaimType`||The name of the output claim|
 |Predicate user message|`Predicate`|The name of the predicate| The attribute of the predicate to be localized. Possible values: `HelpText`.|
 |Predicate group user message|`PredicateValidation`|The ID of the PredicateValidation element.|The ID of the PredicateGroup element. The predicate group must be a child of the predicate validation element as defined in the ElementId.|
 |User interface elements |`UxElement` | | The ID of the user interface element to be localized.|
@@ -246,7 +246,7 @@ The FormatLocalizedStringTransformationClaimType value is used to format claims
     <InputClaim ClaimTypeReferenceId="email" />
   </InputClaims>
   <InputParameters>
-    <InputParameter Id="stringFormatId" DataType="string" Value="ResponseMessge_EmailExists" />
+    <InputParameter Id="stringFormatId" DataType="string" Value="ResponseMessage_EmailExists" />
   </InputParameters>
   <OutputClaims>
     <OutputClaim ClaimTypeReferenceId="responseMsg" TransformationClaimType="outputClaim" />
@@ -257,7 +257,7 @@ The FormatLocalizedStringTransformationClaimType value is used to format claims
 The following example shows how to localize string format of the FormatLocalizedStringTransformationClaimType claims transformation.
 
 ```xml
-<LocalizedString ElementType="FormatLocalizedStringTransformationClaimType" StringId="ResponseMessge_EmailExists">The email '{0}' is already an account in this organization. Click Next to sign in with that account.</LocalizedString>
+<LocalizedString ElementType="FormatLocalizedStringTransformationClaimType" StringId="ResponseMessage_EmailExists">The email '{0}' is already an account in this organization. Click Next to sign in with that account.</LocalizedString>
 ```
 
 ### GetLocalizedStringsTransformationClaimType

articles/active-directory-b2c/localization.md

@@ -117,7 +117,7 @@ In the provided [custom policies](https://github.com/azure-ad-b2c/partner-integr
 |{Settings:ContentDefinitionBaseUri}|Endpoint in where you deployed the UI files|`https://<my-storage-account>.blob.core.windows.net/<my-storage-container>`|
 |{Settings:DfpApiBaseUrl}|The base path for your DFP API instance, found in the DFP portal| `https://tenantname-00001111-aaaa-2222-bbbb-3333cccc4444.api.dfp.dynamics.com/v1.0/`|
 |{Settings:DfpApiAuthScope}|The client_credentials scope for the DFP API service|`https://api.dfp.dynamics-int.com/.default or https://api.dfp.dynamics.com/.default`|
-|{Settings:DfpTenantId}|The ID of the Microsoft Entra tenant (not B2C) where DFP is licensed and installed|`00001111-aaaa-2222-bbbb-3333cccc4444` or `consoto.onmicrosoft.com` |
+|{Settings:DfpTenantId}|The ID of the Microsoft Entra tenant (not B2C) where DFP is licensed and installed|`00001111-aaaa-2222-bbbb-3333cccc4444` or `contoso.onmicrosoft.com` |
 |{Settings:DfpAppClientIdKeyContainer}|Name of the policy key-in which you save the DFP client ID|`B2C_1A_DFPClientId`|
 |{Settings:DfpAppClientSecretKeyContainer}|Name of the policy key-in which you save the DFP client secret |`B2C_1A_DFPClientSecret`|
 |{Settings:DfpEnvironment}| The ID of the DFP environment.|Environment ID is a global unique identifier of the DFP environment that you send the data to. Your custom policy should call the API endpoint, including the query string parameter `x-ms-dfpenvid=your-env-id>`|