Minor typos, ex: tenet -> tenant

Design:-Runtime-Editor-Split.md

@@ -4,8 +4,8 @@ The plan is to break them up into their own discrete packages to provide some mo
 
  - [Use Cases](#use-cases)
    - [Headless](#headless)
-   - [Multi-user, single-tenet runtimes](#multi-user-single-tenet-runtimes)
-   - [Multi-user, multi-tenet runtimes](#multi-user-multi-tenet-runtimes)
+   - [Multi-user, single-tenant runtimes](#multi-user-single-tenant-runtimes)
+   - [Multi-user, multi-tenant runtimes](#multi-user-multi-tenant-runtimes)
    - [Distributed](#distributed)
    - [Scaled](#scaled)
    - [Repurposed Editor](#repurposed-editor)
@@ -28,21 +28,21 @@ A device that runs a flow it is given. The flow is edited elsewhere and remotely
 
 </details>
 
-### Multi-user, single-tenet runtimes
+### Multi-user, single-tenant runtimes
 <details>
 
  - A single hosted instance of the editor is backed by multiple runtimes - one per user or group of users
- - The user access the editor and the underlying api requests are proxied to the appropriate runtime
+ - The user accesses the editor and the underlying api requests are proxied to the appropriate runtime
  - Authentication is handled at the proxy layer
  - API requests can be proxied unmodified (other than auth tokens)
 
 </details>
 
-### Multi-user, multi-tenet runtimes
+### Multi-user, multi-tenant runtimes
 <details>
 
  - A single hosted instance of the editor is backed by multiple runtimes.
- - The user access the editor and the underlying api requests are proxied to the appropriate runtime.
+ - The user accesses the editor and the underlying api requests are proxied to the appropriate runtime.
  - Each runtime may host flows of different users that should not see each other
  - The proxy layer provides a filtered view of the flow to ensure the editor only displays information available to the logged in user.