diff --git a/architecture-docs/data-model-requirements.md b/architecture-docs/data-model-requirements.md
index 5b98200..d9e79fa 100644
--- a/architecture-docs/data-model-requirements.md
+++ b/architecture-docs/data-model-requirements.md
@@ -4,7 +4,7 @@ To transfer between two providers, the target provider must be able to import th
  * (May need a way to show on the front-end which versions are in place, and which migrations are supported. However, for application versions which are completely controlled by the installation and setup, this is "solved".)
 
 for release version 0, focus on known current needs
- * to be expanded later as each new application is added and can be transfered between providers
+ * to be expanded later as each new application is added and can be transferred between providers
  * review migration guides for the known apps with an eye to odd/unusual details that influence design choices (task for Niols? others?)
 
 Specifically, this suggests scoping to migrating:
@@ -30,7 +30,7 @@ Hosting Provider provides:
 
 FooUniversity (Operator)
 * invoice info
-  * is all info expected to be transfered from provider A to provider B?
+  * is all info expected to be transferred from provider A to provider B?
     * May not want to transfer e.g. bank details, because they are already set up at B
     * May also depend on regulation (which information are you allowed to hand out?)
 * Admins: