Skip to content

Commit

Permalink
docs: fixed typos in documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
tom-rm-meyer-ISST committed Jul 24, 2024
1 parent 55ce66d commit d3a4132
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/architecture/06_runtime_view.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,8 @@ as soon as a MaterialPartnerRelation is changed. The Digital Twin is always recr

## Scenario: Exchange Notifications

The notification feature allows users to inform partners about demand and capacity disruptions. The termsData Provider
and Data Consumer are in this scenario somewhat misleading because:
The notification feature allows users to inform partners about demand and capacity disruptions. The terms
`Data Provider` and `Data Consumer` are in this scenario somewhat misleading because:

- The Data Consumer is the message sending party
- The Data Provider is the message receiving party (providing the endpoint consuming the data)
Expand Down
2 changes: 1 addition & 1 deletion docs/architecture/08_concepts.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ which restricts the `specificAssetIds` based on BPNLs.
Two different policies are used depending on the Asset Type:

- Digital Twin Registry: Use Access Policy also as Contract Policy
- Submodels & Notification Endoint: Use Contract Policy as defined below
- Submodels & Notification Endpoint: Use Contract Policy as defined below

_Note: The submodel `PartTypeInformation` is also registered with the same Contract Policy as the other Submodels._

Expand Down

0 comments on commit d3a4132

Please sign in to comment.