Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: typos #1170

Merged
merged 1 commit into from
Feb 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-kits/kits/Connector Kit/Adoption View/adoption-view.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ be limited further by constraints (temporal or spatial) and duties ("e.g. deleti

#### Contract Definition

By combining [`Assets`](#data asset) and Policies, Contracts for data offerings are defined. These Contracts need to be
By combining [`Assets`](#data-assets) and Policies, Contracts for data offerings are defined. These Contracts need to be
accepted by consuming participants (Connectors) for the data exchange to take place.

#### Contract offer
Expand All @@ -188,7 +188,7 @@ participants, including a start and an end date and further relevant information
#### Transfer process

After a successful contract negotiation, `DataRequests` can be sent from the consumer connector to the provider
connector to initiate the data transfer. It references the requested [`Asset`](#data asset)
connector to initiate the data transfer. It references the requested [`Asset`](#data-assets)
and [`ContractAgreement`](#contract-agreement) as well as information about the [data destination](#data-address).

Similar to the `ContractNegotiation`, this object captures the current state of a data transfer. This process is
Expand Down