Skip to content

Commit f4f6b6e

Browse files
authored
Minor revisions
Rewording some of the phrasing
1 parent 93c914b commit f4f6b6e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/verifiable-credentials/how-to-dnsbind.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ After you have the well-known configuration file, you need to make the file avai
8080

8181
## User experience in the wallet
8282

83-
When a user is going through an issuance flow or presenting a verifiable credential, they should know something about organization and its DID. Microsoft Authenticator, validates a DID's relationship with the domain in the DID document and presents users with two different experiences depending on the outcome.
83+
When a user is going through an issuance flow or presenting a verifiable credential, they should know something about the organization and its DID. Microsoft Authenticator, validates a DID's relationship with the domain in the DID document and presents users with two different experiences depending on the outcome.
8484

8585
## Verified domain
8686

@@ -97,11 +97,11 @@ If all of the previously mentioned are true, then Microsoft Authenticator displa
9797

9898
## Unverified domain
9999

100-
If any of the above aren't true, Microsoft Authenticator displays a full page warning to the user that the domain is unverified. The user is warned that they are in the middle of a risky transaction and they should proceed with caution. We have chosen to take this route because:
100+
If any of the above aren't true, Microsoft Authenticator displays a full page warning to the user indicating that the domain is unverified. The user is warned that they are in the middle of a potential risky transaction and they should proceed with caution. We have chosen to take this route because:
101101

102102
* The DID is either not anchored to a domain.
103103
* The configuration wasn't set up properly.
104-
* The DID the user is interacting with is malicious and actually can't prove they own a domain (since they actually don't).
104+
* The DID that the user is interacting with could be malicious and actually can't prove that they own the domain linked.
105105

106106
It is of high importance that you link your DID to a domain recognizable to the user.
107107

0 commit comments

Comments
 (0)