Edited chapter_27_hot_lava.asciidoc with Atlas code editor

Author: troutman_margaret@yahoo.com

chapter_27_hot_lava.asciidoc

@@ -379,7 +379,7 @@ But how do we do that?
 The classic solutions to this problem from the object-oriented world
 come under different names, but they're all variations of the same trick:
 identifying the boundaries, creating an interface to define those boundaries,
-and then using that interface at test time to swap out fake versions of your real dependencies.((("architectures of applications", "Hexagonal/Clean/Onion architectures")))((("adapters, ports and")))((("object-oriented architecture", "ports and adapters")))((("Hexagonal Architecture pattern")))((("Clean Architecture pattern")))((("Onion Architecture pattern")))
+and then using that interface at test time to swap out fake versions of your real dependencies.((("architectures of applications", "Hexagonal/Clean/Onion architectures")))((("adapters, ports and")))((("object-oriented architecture, ports and adapters")))((("Hexagonal Architecture pattern")))((("Clean Architecture pattern")))((("Onion Architecture pattern")))
 
 Steve Freeman and Nat Pryce, in their book
 <<GOOSGBT, _Growing Object-Oriented Software, Guided by Tests_>>,