Update string-transformations.md

Remove whitespaces

Author: yoelhor

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

@@ -77,7 +77,7 @@ The self-asserted technical profile calls the validation **login-NonInteractive*
 - Input claims:
   - **inputClaim1**: [email protected]
   - **inputClaim2**: [email protected]
-    - Input parameters:
+- Input parameters:
   - **stringComparison**:  ordinalIgnoreCase
 - Result: Error thrown
 
@@ -360,22 +360,21 @@ Use this claims transformation to format any string with two parameters, {0} and
 
 ## GetLocalizedStringsTransformation 
 
-  Copies localized strings into claims.
-
-  | Item | TransformationClaimType | Data Type | Notes |
- | ---- | ----------------------- | --------- | ----- |
- | OutputClaim | The name of the localized string | string | List of claim types that is produced after this claims transformation has been invoked. |
+Copies localized strings into claims.
 
-  To use the GetLocalizedStringsTransformation claims transformation:
+| Item | TransformationClaimType | Data Type | Notes |
+| ---- | ----------------------- | --------- | ----- |
+| OutputClaim | The name of the localized string | string | List of claim types that is produced after this claims transformation has been invoked. |
 
-  1. Define a [localization string](localization.md) and associate it with a [self-asserted-technical-profile](self-asserted-technical-profile.md).
- 1. The `ElementType` of the `LocalizedString` element must set to `GetLocalizedStringsTransformationClaimType`.
- 1. The `StringId` is a unique identifier that you define, and use it later in your claims transformation.
- 1. In the claims transformation specify the list of claims to be set with the localized string. The `ClaimTypeReferenceId` is a reference to a ClaimType already defined in the ClaimsSchema section in the policy. The `TransformationClaimType` is the name of the localized string as defined in the `StringId` of the `LocalizedString` element.
- 1. In a [self-asserted technical profile](self-asserted-technical-profile.md), or a [display control](display-controls.md) input or output claims transformation, make a reference to your claims transformation.
+To use the GetLocalizedStringsTransformation claims transformation:
 
+1. Define a [localization string](localization.md) and associate it with a [self-asserted-technical-profile](self-asserted-technical-profile.md).
+1. The `ElementType` of the `LocalizedString` element must set to `GetLocalizedStringsTransformationClaimType`.
+1. The `StringId` is a unique identifier that you define, and use it later in your claims transformation.
+1. In the claims transformation specify the list of claims to be set with the localized string. The `ClaimTypeReferenceId` is a reference to a ClaimType already defined in the ClaimsSchema section in the policy. The `TransformationClaimType` is the name of the localized string as defined in the `StringId` of the `LocalizedString` element.
+1. In a [self-asserted technical profile](self-asserted-technical-profile.md), or a [display control](display-controls.md) input or output claims transformation, make a reference to your claims transformation.
 
-The following example looks up the email subject, body, your code message, and the signature of the email, from localized strings. These claims later used by custom email verification template.  
+The following example looks up the email subject, body, your code message, and the signature of the email, from localized strings. These claims later used by custom email verification template.
 
 Define localized strings for English (default) and Spanish.