Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
Signed-off-by: Emiliano Suñé <[email protected]>
  • Loading branch information
esune committed Aug 29, 2024
1 parent 3eb9775 commit 68db11d
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/patterns/access.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@ Please refer to the [VC-AuthN OIDC](../solutions/vc-authn-sso.md) page for addit

## Direct Access

For more advanced interaction, a direct access pattern may be considered: this will provide the application with full control over the interaction teh same way as if it was a [verifier](verifier.md).
For more advanced interaction, a direct access pattern may be considered: this will provide the application with full control over the interaction the same way as if it was a [verifier](verifier.md).

Direct access, however, requires a significantly higher amount of work when compared to OIDC based access since the application team will be responsible for directly integrating with [Traction's](../solutions/traction-overview.md) APIs to create and process proof-requests as well as developing a custom authentication framework.
2 changes: 1 addition & 1 deletion docs/patterns/overview.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Digital Trust Patterns

Digital Trust interactions generally follow one (or more) of teh following patterns:
Digital Trust interactions generally follow one (or more) of the following patterns:

- [Access](access.md): when a system requires users to authenticate before they can access protected information or functionality.
- [Verifier](verifier.md): when a system needs to verify that users (or other systems) can provide a valid response to a proof-request. Proof requests could either require information to be shared, or only require proof of specific assertions such as "Are you over 19 years of age?" or "Are you authorized to submit this request?".
Expand Down
2 changes: 1 addition & 1 deletion docs/solutions/endorser-service.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ An Endorser Service is responsible for authorizing write transactions to each on
When a write operation such as publishing a new schema definition to the ledger is required, tenant administrators will need to request authorization to the Digital trust team. Each request for endorsement will be reviewed and, if the governance terms are respected, will be approved.

!!! info "Note"
Endorsement requests in the `dev` environment will be automatically approved in order to facilitate rapid prototyping and development of new solutions, once a conenction with the endorser agent is established. `test` an `prod`, however, will require a DITP member to review the request and approve it before the transaction can be written and completed.
Endorsement requests in the `dev` environment will be automatically approved in order to facilitate rapid prototyping and development of new solutions, once a connection with the endorser agent is established. `test` and `prod`, however, will require a DITP member to review the request and approve it before the transaction can be written and completed.

!!! warning "Endorsement is Asynchronous!"
Endorsement requests are asynchronous and may take several hours or even days to complete, especially when review by a DITP team member is required. Ensure your code does not expect an immediate endorsement request, especially when requesting new schemas or credential definitions to be published.

0 comments on commit 68db11d

Please sign in to comment.