Skip to content

Commit a18d4c4

Browse files
committed
Fixes
1 parent f9c7651 commit a18d4c4

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

articles/active-directory-b2c/identity-provider-google.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ zone_pivot_groups: b2c-policy-type
3737

3838
## Create a Google application
3939

40-
To enable sign-in for users with a Google account in Azure Active Directory B2C (Azure AD B2C), you need to create an application in [Google Developers Console](https://console.developers.google.com/). For more information, see [Setting up OAuth 2.0](https://support.google.com/googleapi/answer/6158849). If you don't already have a Google account you can sign up at [`https://accounts.google.com/Signup`](https://accounts.google.com/SignUp).
40+
To enable sign-in for users with a Google account in Azure Active Directory B2C (Azure AD B2C), you need to create an application in [Google Developers Console](https://console.developers.google.com/). For more information, see [Setting up OAuth 2.0](https://support.google.com/googleapi/answer/6158849). If you don't already have a Google account you can sign up at [`https://accounts.google.com/signup`](https://accounts.google.com/signup).
4141

4242
1. Sign in to the [Google Developers Console](https://console.developers.google.com/) with your Google account credentials.
4343
1. In the upper-left corner of the page, select the project list, and then select **New Project**.
@@ -193,4 +193,4 @@ If the sign-in process is successful, your browser is redirected to `https://jwt
193193

194194
## Next steps
195195

196-
Learn how to [pass Google token to your application](idp-pass-through-user-flow.md).
196+
Learn how to [pass a Google token to your application](idp-pass-through-user-flow.md).

articles/active-directory-b2c/partner-biocatch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,7 +233,7 @@ document.getElementById("clientSessionId").style.display = 'none';
233233
```
234234

235235
> [!Note]
236-
> BioCatch will provide you the URL, customer ID and unique user ID (UUID) to configure. The customer SessionID claim is passed through as a querystring parameter to BioCatch. You can choose the activity type, for example *MAKE_PAYMENT*.
236+
> BioCatch will provide you the URL, customer ID and unique user ID (UUID) to configure. The customer SessionID claim is passed through as a query string parameter to BioCatch. You can choose the activity type, for example *MAKE_PAYMENT*.
237237

238238
7. Configure the userjourney; follow the example
239239

articles/active-directory/saas-apps/qliksense-enterprise-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,11 +164,11 @@ In this section, you'll enable Britta Simon to use Azure single sign-on by grant
164164

165165
![Screenshot shows Edit virtual proxy Authentication section where you can enter the values described.][qs10]
166166

167-
a. The **Anonymous access mode** drop down determines if anonymous users may access Qlik Sense through the virtual proxy. The default option is No anonymous user.
167+
a. The **Anonymous access mode** dropdown list determines if anonymous users may access Qlik Sense through the virtual proxy. The default option is **No anonymous user**.
168168

169-
b. The **Authentication method** drop-down determines the authentication scheme the virtual proxy will use. Select SAML from the drop-down list. More options appear as a result.
169+
b. The **Authentication method** dropdown list determines the authentication scheme the virtual proxy will use. Select SAML from the dropdown list. More options appear as a result.
170170

171-
c. In the **SAML host URI field**, input the hostname users enter to access Qlik Sense through this SAML virtual proxy. The hostname is the URI of the Qlik Sense server.
171+
c. In the **SAML host URI field**, input the host name that users enter to access Qlik Sense through this SAML virtual proxy. The host name is the URI of the Qlik Sense server.
172172

173173
d. In the **SAML entity ID**, enter the same value entered for the SAML host URI field.
174174

@@ -194,7 +194,7 @@ In this section, you'll enable Britta Simon to use Azure single sign-on by grant
194194

195195
![Screenshot shows the Edit virtual proxy Advanced screen.][qs13]
196196

197-
The Host allow list identifies hostnames that are accepted when connecting to the Qlik Sense server. **Enter the hostname users will specify when connecting to Qlik Sense server.** The hostname is the same value as the SAML host URI without the https://.
197+
The Host allow list identifies host names that are accepted when connecting to the Qlik Sense server. **Enter the host name that users will specify when connecting to Qlik Sense server.** The host name is the same value as the SAML host URI without the `https://`.
198198

199199
11. Click the **Apply** button.
200200

articles/data-factory/lab-data-flow-data-share.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ In Azure Data Factory linked services define the connection information to exter
9292

9393
In section *Transform data using mapping data flow*, you'll be building mapping data flows. A best practice before building mapping data flows is to turn on debug mode, which allows you to test transformation logic in seconds on an active spark cluster.
9494

95-
To turn on debug, click the **Data flow debug** slider in the top bar of data flow canvas or pipeline canvas when you have **Data flow** activities. Click ok when the confirmation dialog popups. The cluster will take about 5-7 minutes to start up. Continue on to *Ingest data from Azure SQL DB into ADLS Gen2 using the copy activity* while it is initializing.
95+
To turn on debug, click the **Data flow debug** slider in the top bar of data flow canvas or pipeline canvas when you have **Data flow** activities. Click **OK** when the confirmation dialog is shown. The cluster will start up in about 5 to 7 minutes. Continue on to *Ingest data from Azure SQL DB into ADLS Gen2 using the copy activity* while it is initializing.
9696

9797
:::image type="content" source="media/lab-data-flow-data-share/configure10.png" alt-text="Portal configure 10":::
9898

0 commit comments

Comments
 (0)