diff --git a/docs/architecture/06_runtime_view.md b/docs/architecture/06_runtime_view.md
index f7488d5c..832ad12c 100644
--- a/docs/architecture/06_runtime_view.md
+++ b/docs/architecture/06_runtime_view.md
@@ -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)
diff --git a/docs/architecture/08_concepts.md b/docs/architecture/08_concepts.md
index cebe85b2..07373b35 100644
--- a/docs/architecture/08_concepts.md
+++ b/docs/architecture/08_concepts.md
@@ -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._