Commit: 6b059b76d9c87fe019a027180067288544a691cb - MESS (hg)

Commit MetaInfo

• Revision: 6b059b76d9c87fe019a027180067288544a691cb (tree)
• Time: 2020-03-23 00:55:05
• Author: Albert Mietus <albert@miet...>
• Commiter: Albert Mietus

Log Message

advantages.rst edited online with Bitbucket

Change Summary

• modified: SoftwareCompetence/DesignWorkShops/PubSub/concept/advantages.rst

Incremental Difference

diff -r 174651343bba -r 6b059b76d9c8 SoftwareCompetence/DesignWorkShops/PubSub/concept/advantages.rst
--- a/SoftwareCompetence/DesignWorkShops/PubSub/concept/advantages.rst	Sun Mar 22 15:50:53 2020 +0000
+++ b/SoftwareCompetence/DesignWorkShops/PubSub/concept/advantages.rst	Sun Mar 22 15:55:05 2020 +0000
@@ -26,7 +26,7 @@
 Then, both are not “stable” (as they might develop) and being depended on unstable modules is bad. You can’t test
 independently, you may need to revise when the other is updated, etc. Well you know the troubles ...
 
-To overcome this, the modules should be *uncoupled* or *lousily coupled*: Both modules are not allowed to call a
+To overcome this, the modules should be *uncoupled* or *loosely coupled*: Both modules are not allowed to call a
 function/method of the other one. (Which is easy:-). But still pass information; which might seen impossible at first.
 
 This is possible, as the modules do not dependent on each other; instead they both depend on the generic