refactor: Rename main services to infrastructure

Makes it clear that we are talking about wrappers for nodejs and
electron functionality, and not the services being displayed by the
application.

Signed-off-by: Kristóf Marussy <kristof@marussy.com>

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/architecture.md b/docs/architecture.md
index 0122809..791b57b 100644
--- a/docs/architecture.md
+++ b/docs/architecture.md
@@ -82,11 +82,11 @@ Instead, they purely rely on IPC messages to invoke actions in the main process
 
 In the main process, _controllers_ react to `MainStore` changes by invoking Electron APIs and subscribe to Electron events in order to invoke `MainStore` actions.
 
-For easier testability, controllers may rely on _services_ abstracting away the underlying Electron APIs.
-The service has to come with a TypeScript interface and an implementation.
-In the tests, the default implementation of the interface is replaced by a mock.
+For better testability, controllers may rely on _infrastructure services_ (wrappers) abstracting away the underlying Electron APIs.
+Each infrastructure of the service has to come with a TypeScript interface and at least one implementation.
+In the tests, the default implementations of the interfaces are replaced by mocks.
 
-The services and controllers are instatiated and connected to the `MainStore` in the [composition root](https://gitlab.com/say-hi-to-sophie/sophie/-/blob/main/packages/main/src/compositionRoot.ts).
+The infrastructure services and controllers are instantiated and connected to the `MainStore` in the [composition root](https://gitlab.com/say-hi-to-sophie/sophie/-/blob/main/packages/main/src/init.ts).
 
 **TODO:**
 While a service is a common term in MVC application architecture, we should come up with a different name to avoid clashing witch services, i.e., web sites loaded by Sophie.