Fixed some minor typos

catalog/catalog.binding.https.md

@@ -37,7 +37,7 @@ Authorization: ...
 
 {
   "@context":  "https://w3id.org/dspace/v0.8/context.json",
-  "@type": "dspace:CatalogRequest"
+  "@type": "dspace:CatalogRequest",
   "dspace:filter": {}
 }
 ```
@@ -132,7 +132,7 @@ the [HTTP 1.1 Specification](https://www.rfc-editor.org/rfc/rfc9110.html#name-gz
 
 ### 4.1 Asynchronous Interactions
 
-We may want to specify optional support for asynchronous callbacks for the catalog response. This would require addling a `callbackAddress` property and an `@id` to the request:
+We may want to specify optional support for asynchronous callbacks for the catalog response. This would require adding a `callbackAddress` property and an `@id` to the request:
 
 ```
 POST https://provider.com/catalog/request

model/model.md

@@ -12,9 +12,9 @@ The relationships between the primary dataspace entities are defined as follows:
 
 Note that all relationships are multiplicities unless specified.
 
-- A `Dataspace Authority` manges one or more `Dataspaces`. This will include participant registration and may entail mandating business and/or requirements. For example, a
+- A `Dataspace Authority` manages one or more `Dataspaces`. This will include participant registration and may entail mandating business and/or requirements. For example, a
   Dataspace Authority may require participants to obtain some form of business certification. A Dataspace authority may also impose technical requirements such as support for the
-  technical enforcements of specific usage policies.
+  technical enforcement of specific usage policies.
 - A `Participant` is a member of one or more `Dataspaces`. A participant registers `Participant Agents` that perform tasks on its behalf.
 - A `Participant Agent` performs tasks such as publishing a catalog or engaging in an asset transfer. In order to accomplish these tasks, a participant agent may
   use a _**verifiable presentation**_ generated from a _**credential**_ obtained from a third-party issuer. A participant agent may also use an _**ID token**_ issued by a
@@ -46,8 +46,8 @@ elements of the model, i.e. those that are represented in protocol message flows
 A `Catalog` is a [DCAT Catalog](https://www.w3.org/TR/vocab-dcat-3/#Class:Catalog) with the following attributes:
 
 - 0..N  `Asset Entries`. Since a catalog may be dynamically generated for a request based on the requesting participant's credentials it is possible for it to contain 0 matching
-  asset entries.  (DCAT PROFILE)
-- 1.N [DCAT DataService](https://www.w3.org/TR/vocab-dcat-3/#Class:Data_Service) that references a `Connector` where assets may be obtained.  (DCAT PROFILE)
+  asset entries. (DCAT PROFILE)
+- 1..N [DCAT DataService](https://www.w3.org/TR/vocab-dcat-3/#Class:Data_Service) that references a `Connector` where assets may be obtained. (DCAT PROFILE)
 
 ### 2.2.2 Asset Entry
 

model/terminology.md

@@ -26,9 +26,9 @@ An `IdentityProvider` is a trusted technology system that creates, maintains, an
 
 A `CredentialIssuer` is a trusted technology system that issues verifiable credentials for a `Participant` and `ParticipantAgents`.
 
-## Observability, Tracability and Audit Logging
+## Observability, Traceability and Audit Logging
 
-`Observability, Tracability and Audit Logging` of transactions, e.g. `Contract Negotiation`, `Data Transfer` and enforcement of access policies or usage policies, in a `Data Space` can be a requirement.
+`Observability, Traceability and Audit Logging` of transactions, e.g. `Contract Negotiation`, `Data Transfer` and enforcement of access policies or usage policies, in a `Dataspace` can be a requirement.
 If a  trusted technology system is required that records and verifies those domain events. This is not in the scope of the current version of the document and is subject of future work.
 
 ## DataspaceRegistrationService
@@ -57,11 +57,11 @@ A collection of entries representing `Assets` and their `Offers` that is adverti
 
 ## CatalogService
 
-A `PariticipantAgent` that makes a `Catalog` accessible to `Participants`.
+A `ParticipantAgent` that makes a `Catalog` accessible to `Participants`.
 
 ## Connector (DataService)
 
-A `PariticipantAgent` that produces `Agreements` and manages `Asset` sharing.
+A `ParticipantAgent` that produces `Agreements` and manages `Asset` sharing.
 
 ## Contract Negotiation
 

negotiation/contract.negotiation.binding.https.md

@@ -210,7 +210,7 @@ Authorization: ...
 }
 ```
 
-If the message is successfully processed, consumer provider connector must return and HTTP 200 (OK) response. The response body is not specified and clients are not required to
+If the message is successfully processed, the consumer provider connector must return an HTTP 200 (OK) response. The response body is not specified and clients are not required to
 process it.
 
 ### 3.3 The consumer `negotiations/:id/agreement` resource

negotiation/contract.negotiation.protocol.md

@@ -173,7 +173,7 @@ When the `ContractNegotiationEventMessage` is sent by a provider with an `eventT
 is accessible. The state machine is transitioned to the `FINALIZED` state. Other event types may be defined in the future. A consumer responds with an error if the signature
 can't be validated or is incorrect.
 
-It is an error for a consumer to send a `ContractNegotiationEventMessage` with an eventType `finalized` to the provider.
+It is an error for a consumer to send a `ContractNegotiationEventMessage` with an eventType `FINALIZED` to the provider.
 
 When the `ContractNegotiationEventMessage` is sent by a consumer with an `eventType` set to  `ACCEPTED`, the state machine is placed in the `ACCEPTED` state.