Skip to content

Commit 8221597

Browse files
Update identity-broker.md
Minor edits to resolve Acrolinx term issues.
1 parent 5b6dd96 commit 8221597

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/hdinsight/domain-joined/identity-broker.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The ID Broker feature will add one extra VM to the cluster. This VM is the ID Br
4242
![Option to enable ID Broker](./media/identity-broker/identity-broker-enable.png)
4343

4444
### Using Azure Resource Manager templates
45-
If you add a new role called `idbrokernode` with the following attributes to the compute profile of your template, then the cluster will get created with the id broker node enabled:
45+
If you add a new role called `idbrokernode` with the following attributes to the compute profile of your template, then the cluster will get created with the ID broker node enabled:
4646

4747
```json
4848
.
@@ -97,7 +97,7 @@ In the ID broker setup, custom apps and clients connecting to the gateway can be
9797

9898
* OAuth resource uri: https://hib.azurehdinsight.net
9999
* AppId: 7865c1d2-f040-46cc-875f-831a1ef6a28a
100-
* Permission: (name: Cluster.ReadWrite, id:8f89faa0-ffef-4007-974d-4989b39ad77d)
100+
* Permission: (name: Cluster.ReadWrite, id: 8f89faa0-ffef-4007-974d-4989b39ad77d)
101101

102102
## Next steps
103103

0 commit comments

Comments
 (0)