diff --git a/usage-examples/submodules-eiffel.md b/usage-examples/submodules-eiffel.md
index 867118a3..6738c940 100644
--- a/usage-examples/submodules-eiffel.md
+++ b/usage-examples/submodules-eiffel.md
@@ -15,4 +15,4 @@ This will show you one setup for the Eiffel model on how to get around the use-c
 
 Depending on the solution setup, a Service can be created to listen for SCCs (Source Change Created) that carry a specific identification tag/id for the Parent repository. Upon detecting such an SCC, the Service uses the SourceChange API to read the SHA IDs of contained submodules. It then fetches the related SCCs based on these IDs. Finally, it generates a CompositionDefined (CD) event and publishes it on the bus.
 
-Important drawback from this is that it does not create a linear relationship downwards. Even though one could argue that it does, but it requires knowledge about what SCC one is suposed to query.
\ No newline at end of file
+Important drawback from this is that it does not create a linear relationship downwards. Even though one could argue that it does, but it requires knowledge about what SCC one is suposed to query.