Skip to content

Commit cb282b1

Browse files
committed
captcha - address review comments
1 parent a7d09aa commit cb282b1

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

articles/active-directory-b2c/add-captcha.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -293,7 +293,7 @@ To enable CAPTCHA in MFA flow, you need to make an update in two technical profi
293293

294294
1. Inspect your sign-up sign-in user journey, such as *SignUpOrSignIn*, to identify the self-asserted technical profile and phone factor technical profiles that are responsible for your sign-up or sign-in flow.
295295

296-
1. In both of the technical profiles, add a metadata key and a display claim entries as shown in the following code:
296+
1. In both of the technical profiles, add a metadata key and a display claim entry as shown in the following code:
297297

298298
```xml
299299
<TechnicalProfile Id="PhoneFactor-InputOrVerify">

articles/active-directory-b2c/captcha-technical-profile.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The following example shows a self-asserted technical profile for email sign-up:
3939
```
4040
## CAPTCHA technical profile operations
4141

42-
CAPTCHA technical profile operations has two operations:
42+
CAPTCHA technical profile operations have two operations:
4343

4444
- **Get challenge operation** generates the CAPTCHA code string, then displays it on the user interface by using a [CAPTCHA display control](display-control-captcha.md). The display includes an input textbox. This operation directs the user to input the characters they see or hear into the input textbox. The user can switch between visual and audio challenge types as needed.
4545

@@ -51,12 +51,12 @@ The first operation generates the CAPTCHA code string, then displays it on the u
5151

5252
### Input claims
5353

54-
The **InputClaims** element contains a list of claims to send to Azure AD B2C's capt service.
54+
The **InputClaims** element contains a list of claims to send to Azure AD B2C's CAPTCHA service.
5555

5656
| ClaimReferenceId | Required | Description |
5757
| --------- | -------- | ----------- |
5858
| challengeType | No | The CAPTCHA challenge type, Audio or Visual (default).|
59-
| azureregion | Yes | The service region that will serve the CAPTCHA challenge request. |
59+
| azureregion | Yes | The service region that serves the CAPTCHA challenge request. |
6060

6161
### Display claims
6262

@@ -75,7 +75,7 @@ The **OutputClaims** element contains a list of claims returned by the CAPTCHA t
7575
| --------- | -------- | ----------- |
7676
| challengeId | Yes | A unique identifier for CAPTCHA challenge code.|
7777
| challengeString | Yes | The CAPTCHA challenge code.|
78-
| azureregion | Yes | The service region that will serve the CAPTCHA challenge request.|
78+
| azureregion | Yes | The service region that serves the CAPTCHA challenge request.|
7979

8080

8181
### Metadata
@@ -122,14 +122,14 @@ The second operation verifies the CAPTCHA challenge.
122122

123123
### Input claims
124124

125-
The **InputClaims** element contains a list of claims to send to Azure AD B2C's capt service.
125+
The **InputClaims** element contains a list of claims to send to Azure AD B2C's CAPTCHA service.
126126

127127
| ClaimReferenceId | Required | Description |
128128
| --------- | -------- | ----------- |
129129
| challengeType | No | The CAPTCHA challenge type, Audio or Visual (default).|
130130
|challengeId| Yes | A unique identifier for CAPTCHA used for session verification. Populated from the *GetChallenge* call. |
131131
|captchaEntered| Yes | The challenge code that the user inputs into the challenge textbox on the user interface. |
132-
|azureregion| Yes | The service region that will serve the CAPTCHA challenge request. Populated from the *GetChallenge* call.|
132+
|azureregion| Yes | The service region that serves the CAPTCHA challenge request. Populated from the *GetChallenge* call.|
133133

134134

135135
### Display claims

articles/active-directory-b2c/display-control-captcha.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Use CAPTCHA display controls to generate a CAPTCHA challenge string, then verify
2222

2323
The screenshot shows the CAPTCHA display control shown on a sign-up page:
2424

25-
:::image type="content" source="media/add-captcha/add-captcha.png" alt-text="Screenshot of CAPTCHA as it appears in the sign up page.":::
25+
:::image type="content" source="media/add-captcha/add-captcha.png" alt-text="Screenshot of CAPTCHA as it appears in the sign-up page.":::
2626

2727
The sign-up page loads with the CAPTCHA display control. The user then inputs the characters they see or hear. The **Send verification code** button sends a verification code to the user's email, and isn't CAPTCHA display control element, but it causes the CAPTCHA challenge string to be verified.
2828

@@ -38,7 +38,7 @@ This table summarizes the elements that a CAPTCHA display control contains.
3838
| OutputClaim | No | Any claim to be returned to the self-asserted page after the user completes CAPTCHA code verification process. |
3939
| Actions | Yes | CAPTCHA display control contains two actions, *GetChallenge* and *VerifyChallenge*. <br> *GetChallenge* action generates, then displays a CAPTCHA challenge code on the user interface. <br> *VerifyChallenge* action verifies the CAPTCHA challenge code that the user inputs. |
4040

41-
The following XML snippet code shows an examples of CaptchaProvider display control:
41+
The following XML snippet code shows an example of CaptchaProvider display control:
4242

4343
```xml
4444
<DisplayControls>

articles/active-directory-b2c/page-layout.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ Azure AD B2C page layout uses the following versions of the [jQuery library](htt
207207
- You can now add the `data-preload="true"` attribute [in your HTML tags](customize-ui-with-html.md#guidelines-for-using-custom-page-content)
208208
- Load linked CSS files at the same time as your HTML template so it doesn't 'flicker' between loading the files.
209209
- Control the order in which your `script` tags are fetched and executed before the page load.
210-
- Email field is now `type=email` and mobile keyboards will provide the correct suggestions.
210+
- Email field is now `type=email` and mobile keyboards provide the correct suggestions.
211211
- Support for Chrome translate.
212212
- Added support for company branding in user flow pages.
213213

0 commit comments

Comments
 (0)